GameServerManagers / LinuxGSM

The command-line tool for quick, simple deployment and management of Linux dedicated game servers.
https://linuxgsm.com
MIT License
4.32k stars 821 forks source link

Refactor <serverName> dt/ details #2671

Closed JimTR closed 3 years ago

JimTR commented 4 years ago

I am producing a web app using LGSM to contol games currently I am refactoring the ouput from the dt command most of the output works fine as I'm splitting the string around the : character to produce the array E.G Key value LinuxGSM version: v19.12.5 this works fine in most cases and most other outputs are easy enough to create a key for with the exception of this part mcserver outputs `

Game INBOUND 25565 tcp Query INBOUND 25565 udp Rcon INBOUND 25575 tcp`

however most other games output like `

Game/RCON INBOUND 27016 tcp/udp SourceTV INBOUND 27021 udp < Client OUTBOUND 27006 udp`

the easy fix is to add :'s after the title and remove the > and < any thoughts ?

issue-label-bot[bot] commented 4 years ago

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.69. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

dgibbs64 commented 4 years ago

Sorry for the slow response. I can see no issue with removing the < & > from that. Not quite sure what you mean by :'s though. Also im guessing you are using the ansi=off setting.

JimTR commented 4 years ago

the code currently reads `DESCRIPTION DIRECTION PORT PROTOCOL

Game/RCON INBOUND 27017 tcp/udp SourceTV INBOUND 27022 udp < Client OUTBOUND 27007 udp ` coud it read

DESCRIPTION DIRECTION PORT PROTOCOL Game/RCON: INBOUND 27017 tcp/udp SourceTV: INBOUND 27022 udp Client: OUTBOUND 27007 udp

notice the :'s added to the line

dgibbs64 commented 3 years ago

I have refactored port detection with the most recent update. this should help with this issue

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.