starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-26 06:35:54 +03:00

[GH-ISSUE #1242] Settings to disable sleeps and prompts #964

New issue

Closed

opened 2026-02-27 02:54:33 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @UltimateByte on GitHub (Jan 13, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1242

skipsleeps="on" parameter would disable sleeps in LGSM. Less readable, but faster.
Code wise: Replace any sleep into LGSM by fn_sleep x with x being the desired duration. Then fn_sleep would check for the config variable before applying any kind of a sleep.

skipprompts="on" parameter would disable any kind of prompt in LGSM.
Code wise: Prepare some prompt functions with different layouts. Then call it with fn_prompt_whatever "Message goes here" "Text Option A" "Text Option B" "Action option A" "Action option B" "Invalid option message" "Default Option". Of course, this function would check for the config variable as well. Not really sure how to implement this one though, but would be really cool.

Would be lovely IMO, and make LGSM so much faster for experienced users!

Thoughts?

Originally created by @UltimateByte on GitHub (Jan 13, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1242 `skipsleeps="on"` parameter would disable sleeps in LGSM. Less readable, but faster. Code wise: Replace any sleep into LGSM by `fn_sleep x` with x being the desired duration. Then fn_sleep would check for the config variable before applying any kind of a sleep. `skipprompts="on"` parameter would disable any kind of prompt in LGSM. Code wise: Prepare some prompt functions with different layouts. Then call it with `fn_prompt_whatever "Message goes here" "Text Option A" "Text Option B" "Action option A" "Action option B" "Invalid option message" "Default Option"`. Of course, this function would check for the config variable as well. Not really sure how to implement this one though, but would be really cool. Would be lovely IMO, and make LGSM so much faster for experienced users! Thoughts?

kerem

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

closed this issue
added the
type: feature
label

kerem commented

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

Author

Owner

@braunsonm commented on GitHub (Jan 13, 2017):

Would be kind of annoying to add this setting to every server file no? Additionally if we go this route every time we want to add a configurable feature to LGSM you'd have to edit EVERY server file in LGSM.

Should maybe be something when running the install, like ./mtaserver install --skip-sleeps

@braunsonm commented on GitHub (Jan 13, 2017): Would be kind of annoying to add this setting to every server file no? Additionally if we go this route every time we want to add a configurable feature to LGSM you'd have to edit EVERY server file in LGSM. Should maybe be something when running the install, like `./mtaserver install --skip-sleeps`

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Jan 13, 2017):

Thanks for sharing your thoughts.

Would be kind of annoying to add this setting to every server file no?

Well, after this https://github.com/GameServerManagers/LinuxGSM/releases/tag/161030 I'm not affraid about it. :p
The feature would apply to newer "gameserver" scripts and not break existing installations.

Should maybe be something when running the install, like ./mtaserver install --skip-sleeps

For some reason, @dgibbs64 said it's impossible to combine two arguments. A global setting would be more enjoyable anyways, I think.

@UltimateByte commented on GitHub (Jan 13, 2017): Thanks for sharing your thoughts. > Would be kind of annoying to add this setting to every server file no? Well, after this https://github.com/GameServerManagers/LinuxGSM/releases/tag/161030 I'm not affraid about it. :p The feature would apply to newer "gameserver" scripts and not break existing installations. > Should maybe be something when running the install, like ./mtaserver install --skip-sleeps For some reason, @dgibbs64 said it's impossible to combine two arguments. A global setting would be more enjoyable anyways, I think.

kerem commented

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

Author

Owner

@braunsonm commented on GitHub (Jan 13, 2017):

I don't think the implementation for that backup even makes sense on its own. If you plan to make LGSM sustainable and organized while still adding configurable scripts, having a separate file that is fetched that is specifically for configuring LGSM would be more ideal imo.

Keep server files for server configuration, have a separate file for LGSM configuration, notifications, backups, skipping sleep etc. That way you have 1 file to update on GitHub, and 1 file for the client to fetch in order to configure.

@braunsonm commented on GitHub (Jan 13, 2017): I don't think the implementation for that backup even makes sense on its own. If you plan to make LGSM sustainable and organized while still adding configurable scripts, having a separate file that is fetched that is specifically for configuring LGSM would be more ideal imo. Keep server files for server configuration, have a separate file for LGSM configuration, notifications, backups, skipping sleep etc. That way you have 1 file to update on GitHub, and 1 file for the client to fetch in order to configure.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Jan 13, 2017):

That is a project already. I can't wait to see this coming.
https://github.com/GameServerManagers/LinuxGSM/issues/344

Until then, we have to do it this way.

@UltimateByte commented on GitHub (Jan 13, 2017): That is a project already. I can't wait to see this coming. https://github.com/GameServerManagers/LinuxGSM/issues/344 Until then, we have to do it this way.

kerem commented

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

Author

Owner

@JimTR commented on GitHub (Jan 14, 2017):

referencing something dated Apr 2015 ... I still think add this stuff to a database rather than a file so it can be read via any platform that can access it

@JimTR commented on GitHub (Jan 14, 2017): referencing something dated Apr 2015 ... I still think add this stuff to a database rather than a file so it can be read via any platform that can access it

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Dec 25, 2020):

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.

@github-actions[bot] commented on GitHub (Dec 25, 2020): 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.