starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #2936] confirmation bypass option for gameserver console command #2096

New issue

Open

opened 2026-02-27 03:00:50 +03:00 by kerem · 9 comments

kerem commented

2026-02-27 03:00:50 +03:00

Owner

Originally created by @kriegtiger on GitHub (Jun 24, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2936

User Story

When setting up my LGSM arkserver instance, I used the console multiple times, and it was mildly bothersome to run the './arkserver console' command, then have to wait and input confirmation, before I could actually see the console.

Basic info

Distro: Debian 9
Game: ARK
Command: ./arkserver console
LinuxGSM version: v20.3.3

Further Information

It would be nice if it were possible to issue a '-y' or something along with the console command (ie: ./arkserver -y console ) in order to skip past that additional prompt, or maybe a shell variable that is effectively a 'usage understood' EULA style nod that says 'I know how to exit/use the console, skip ahead please'.

Originally created by @kriegtiger on GitHub (Jun 24, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2936 ## User Story When setting up my LGSM arkserver instance, I used the console multiple times, and it was mildly bothersome to run the './arkserver console' command, then have to wait and input confirmation, before I could actually see the console. ## Basic info * **Distro:** Debian 9 * **Game:** ARK * **Command:** ./arkserver console * **LinuxGSM version:** v20.3.3 ## Further Information It would be nice if it were possible to issue a '-y' or something along with the console command (ie: ./arkserver -y console ) in order to skip past that additional prompt, or maybe a shell variable that is effectively a 'usage understood' EULA style nod that says 'I know how to exit/use the console, skip ahead please'. ## Further Reading Numerous Linux commands/utilities have '-y' functionality to automatically say 'yes' to whatever prompt may be presented

kerem added the

type: feature

command: console

labels

2026-02-27 03:00:50 +03:00

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Jun 24, 2020):

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

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

@issue-label-bot[bot] commented on GitHub (Jun 24, 2020): Issue-Label Bot is automatically applying the label `type: feature request` to this issue, with a confidence of 0.95. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jul 29, 2020):

So the reason a Y is added is to allow users to ability to understand how to correctly exit the console.

I think there are a couple of options here. Either add a count down timer of say 5 seconds. Or try to speed the messaging to get to the Y point. Im not to sure on implementing a -y option currently

@dgibbs64 commented on GitHub (Jul 29, 2020): So the reason a Y is added is to allow users to ability to understand how to correctly exit the console. I think there are a couple of options here. Either add a count down timer of say 5 seconds. Or try to speed the messaging to get to the Y point. Im not to sure on implementing a -y option currently

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@kriegtiger commented on GitHub (Jul 29, 2020):

So the reason a Y is added is to allow users to ability to understand how to correctly exit the console.

I think there are a couple of options here. Either add a count down timer of say 5 seconds. Or try to speed the messaging to get to the Y point. Im not to sure on implementing a -y option currently

Yep, I get that. It's a perfectly reasonable reminder to have for a while to remind people how it works, it's just an irritant once you're familiar with the process - hence the request for having a way to bypass it later if the user wishes.

What about having something like '<CTRL-B>, D to exit' in the green bar at the bottom that is (at least for ARK?) mostly empty? Or maybe add a second green bar at the top with usage reminders. Information is still conveyed and will always be present in the user's vision in this case instead of just a blip at the beginning.

@kriegtiger commented on GitHub (Jul 29, 2020): > So the reason a Y is added is to allow users to ability to understand how to correctly exit the console. > > I think there are a couple of options here. Either add a count down timer of say 5 seconds. Or try to speed the messaging to get to the Y point. Im not to sure on implementing a -y option currently Yep, I get that. It's a perfectly reasonable reminder to have for a while to remind people how it works, it's just an irritant once you're familiar with the process - hence the request for having a way to bypass it later if the user wishes. What about having something like `'<CTRL-B>, D to exit'` in the green bar at the bottom that is (at least for ARK?) mostly empty? Or maybe add a second green bar at the top with usage reminders. Information is still conveyed and will *always* be present in the user's vision in this case instead of just a blip at the beginning.

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@soccermitchy commented on GitHub (Aug 31, 2021):

Just saw this issue was still open - what about something like a skipconsolewarning variable, defaulting to not skip it? I'd be willing to submit a pull request for it. It's something that'd only be known by those who already know about it, anyway - ie. you'd have to dig into the config to see it, indicating you already know how to use LinuxGSM, and we can have how to exit be part of the config value description.

@soccermitchy commented on GitHub (Aug 31, 2021): Just saw this issue was still open - what about something like a `skipconsolewarning` variable, defaulting to not skip it? I'd be willing to submit a pull request for it. It's something that'd only be known by those who already know about it, anyway - ie. you'd have to dig into the config to see it, indicating you already know how to use LinuxGSM, and we can have how to exit be part of the config value description.

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@kriegtiger commented on GitHub (Aug 31, 2021):

Just saw this issue was still open - what about something like a skipconsolewarning variable, defaulting to not skip it? I'd be willing to submit a pull request for it. It's something that'd only be known by those who already know about it, anyway - ie. you'd have to dig into the config to see it, indicating you already know how to use LinuxGSM, and we can have how to exit be part of the config value description.

That sounds good to me. Would it be possible to have that bit in the green bar at the bottom as a reminder of how to properly exit the console? That would alleviate an earlier responder's issue of 'we need the confirmation prompt to make sure people know how to quit the console'. Not sure if that area is reserved for other functions/data depending on the game being served.

@kriegtiger commented on GitHub (Aug 31, 2021): > > > Just saw this issue was still open - what about something like a `skipconsolewarning` variable, defaulting to not skip it? I'd be willing to submit a pull request for it. It's something that'd only be known by those who already know about it, anyway - ie. you'd have to dig into the config to see it, indicating you already know how to use LinuxGSM, and we can have how to exit be part of the config value description. That sounds good to me. Would it be possible to have that bit in the green bar at the bottom as a reminder of how to properly exit the console? That would alleviate an earlier responder's issue of 'we need the confirmation prompt to make sure people know how to quit the console'. Not sure if that area is reserved for other functions/data depending on the game being served. ![image](https://user-images.githubusercontent.com/6956044/131548736-3a351051-4819-4b20-a57d-336fd2bbee06.png)

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@soccermitchy commented on GitHub (Aug 31, 2021):

In theory it'd be possible, but I'm not sure if that'd be something the LinuxGSM team would be willing to do on the official versions of LGSM. The bottom bar is from tmux, and a lot of people use custom tmux configurations which may be setting their own custom text, and we'd be trampling on over the configuration if we set it. That said, it's literally one command to do it:
tmux set -t $sessionname status-right " [<Ctrl-b> d to exit] "#{=21:pane_title}" %H:%M %d-%b-%y"
Or from within the session itself:
:set status-right " [<Ctrl-b> d to exit] "#{=21:pane_title}" %H:%M %d-%b-%y"
That would give you something like this:

@soccermitchy commented on GitHub (Aug 31, 2021): In theory it'd be possible, but I'm not sure if that'd be something the LinuxGSM team would be willing to do on the official versions of LGSM. The bottom bar is from `tmux`, and a lot of people use custom tmux configurations which may be setting their own custom text, and we'd be trampling on over the configuration if we set it. That said, it's literally one command to do it: `tmux set -t $sessionname status-right " [<Ctrl-b> d to exit] "#{=21:pane_title}" %H:%M %d-%b-%y"` Or from within the session itself: <Ctrl-b> `:set status-right " [<Ctrl-b> d to exit] "#{=21:pane_title}" %H:%M %d-%b-%y"` That would give you something like this: ![image](https://user-images.githubusercontent.com/443155/131549153-72d23313-d271-4e27-ba79-6289a82cc11f.png)

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@soccermitchy commented on GitHub (Aug 31, 2021):

Re: tmux configuration, you can put this in your ~/.tmux.conf for a similar thing:

set -g status-right " [<Ctrl-b> d to exit] "#{=21:pane_title}" %H:%M %d-%b-%y"

@soccermitchy commented on GitHub (Aug 31, 2021): Re: tmux configuration, you can put this in your `~/.tmux.conf` for a similar thing: ```tmux set -g status-right " [<Ctrl-b> d to exit] "#{=21:pane_title}" %H:%M %d-%b-%y" ```

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@rtxa commented on GitHub (Apr 8, 2022):

@dgibbs64 Sorry for tagging you. Any updates on this issue? I find a good solution to add some option like skip-console-warning to avoid the annoyance to keep pressing Y everytime you want to access the console, start the server, etc. when you are already familiarized with LinuxGSM.

@rtxa commented on GitHub (Apr 8, 2022): @dgibbs64 Sorry for tagging you. Any updates on this issue? I find a good solution to add some option like `skip-console-warning` to avoid the annoyance to keep pressing Y everytime you want to access the console, start the server, etc. when you are already familiarized with LinuxGSM.

kerem commented

2026-02-27 03:00:51 +03:00

Author

Owner

@Jacksaur commented on GitHub (Jan 21, 2025):

Since there's still no way to disable the warning, I've done my best to copy the tmux command out of the script and run it directly under an alias instead.
For me tmux -L tf2server-3292477d attach-session -t tf2server works for a TF2 server. Socket name was found by checking ls /tmp/tmux-1000 while the server was running. And the session name by running tmux -L $SOCKET_NAME list-sessions after.

Working well enough so far, not sure how often the socket name changes but it's persisted between multiple server and system reboots, and shouldn't be too hard to update the alias if it does change.

@Jacksaur commented on GitHub (Jan 21, 2025): Since there's still no way to disable the warning, I've done my best to copy the tmux command out of the script and run it directly under an alias instead. For me `tmux -L tf2server-3292477d attach-session -t tf2server` works for a TF2 server. Socket name was found by checking `ls /tmp/tmux-1000` while the server was running. And the session name by running `tmux -L $SOCKET_NAME list-sessions` after. Working well enough so far, not sure how often the socket name changes but it's persisted between multiple server and system reboots, and shouldn't be too hard to update the alias if it does change.

kerem referenced this issue

2026-02-27 03:54:40 +03:00

[PR #2086] [CLOSED] Add extraparams parameter to all gameservers #3484

kerem referenced this issue

2026-02-27 03:54:42 +03:00

[PR #2096] [MERGED] feat (game server): StickyBots Server #3489