starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 22:25:59 +03:00

[GH-ISSUE #2199] Start Parameters in instance config #1681

New issue

Closed

opened 2026-02-27 02:58:29 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 02:58:29 +03:00

Owner

Originally created by @mgjuhler on GitHub (Feb 19, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2199

I think I might have found a bug.

I run several servers during the same installation and it works just fine.
I run with a config per instance and I am trying to set the start parameters different on each instance.
(some servers run with tickrate 128 and without bots) it is not a problem as long as I insert start parameters into the common.cfg file, but when I do so in instance config it does not work. All other settings that are in instance config are added just fine, the only thing that does not work is the start parameters.

https://pastebin.com/YxS1HAY3

Game: Counter-Strike Source

Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04

Originally created by @mgjuhler on GitHub (Feb 19, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2199 I think I might have found a bug. I run several servers during the same installation and it works just fine. I run with a config per instance and I am trying to set the start parameters different on each instance. (some servers run with tickrate 128 and without bots) it is not a problem as long as I insert start parameters into the common.cfg file, but when I do so in instance config it does not work. All other settings that are in instance config are added just fine, the only thing that does not work is the start parameters. https://pastebin.com/YxS1HAY3 Game: Counter-Strike Source Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04

kerem

2026-02-27 02:58:29 +03:00

closed this issue
added the
type: bug

priority
labels

kerem commented

2026-02-27 02:58:30 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Apr 26, 2019):

Just to clarify.

If you change start parameters in common.cfg it works but for instance.cfg it does not?

@dgibbs64 commented on GitHub (Apr 26, 2019): Just to clarify. If you change start parameters in common.cfg it works but for instance.cfg it does not?

kerem commented

2026-02-27 02:58:30 +03:00

Author

Owner

@mgjuhler commented on GitHub (May 2, 2019):

Just to clarify.

If you change start parameters in common.cfg it works but for instance.cfg it does not?

Correct, if i set the start parameters in common.cfg it all works, if i try to set the start parameters in the instance cfg and not in the common.cfg i does not work

@mgjuhler commented on GitHub (May 2, 2019): > Just to clarify. > > If you change start parameters in common.cfg it works but for instance.cfg it does not? Correct, if i set the start parameters in common.cfg it all works, if i try to set the start parameters in the instance cfg and not in the common.cfg i does not work

kerem commented

2026-02-27 02:58:30 +03:00

Author

Owner

@h3o66 commented on GitHub (Feb 23, 2021):

Not sure if this is still the case ?
The command system was reworked with the latest release.

@h3o66 commented on GitHub (Feb 23, 2021): Not sure if this is still the case ? The command system was reworked with the latest release.

kerem commented

2026-02-27 02:58:30 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Feb 27, 2021):

I will close this as it may be fixed in a recent release. However if still an issue please re-raise. Thank you

@dgibbs64 commented on GitHub (Feb 27, 2021): I will close this as it may be fixed in a recent release. However if still an issue please re-raise. Thank you

kerem commented

2026-02-27 02:58:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 28, 2022):

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 (Feb 28, 2022): 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.

kerem referenced this issue

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

[PR #1682] [MERGED] Fix #1681 - Oxide Seven Days file renamed #3393