[GH-ISSUE #2031] Add sv_lan and sv_cheats options to csgoserver default config file #1589

New issue

Closed

opened 2026-02-27 02:57:59 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 02:57:59 +03:00

Owner

Originally created by @borzaka on GitHub (Oct 7, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2031

The idea is came from the official Counter-Strike: Global Offensive Dedicated Servers page.
Under Advanced Configuration there is an example autoexec.cfg:

log on //This is set to turn on logging! Don't put this in your server.cfg
hostname "Counter-Strike: Global Offensive Dedicated Server"
rcon_password "yourrconpassword"
sv_password "" //Only set this if you intend to have a private server!
sv_cheats 0 //This should always be set, so you know it's not on
sv_lan 0 //This should always be set, so you know it's not on
exec banned_user.cfg
exec banned_ip.cfg

So, these two sounds like a great idea to add to csgoserver default config file:

sv_cheats 0 //This should always be set, so you know it's not on
sv_lan 0 //This should always be set, so you know it's not on

Benefits:

you know it's not on, or it's on
you could set this settings per instance: maybe you want an instance with sv_cheats 1 for practice, and another one for only lan games (sv_lan 1), etc.

Originally created by @borzaka on GitHub (Oct 7, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2031 The idea is came from the official [Counter-Strike: Global Offensive Dedicated Servers](https://developer.valvesoftware.com/wiki/Counter-Strike:_Global_Offensive_Dedicated_Servers) page. Under [Advanced Configuration](https://developer.valvesoftware.com/wiki/Counter-Strike:_Global_Offensive_Dedicated_Servers#Advanced_Configuration) there is an example autoexec.cfg: ``` log on //This is set to turn on logging! Don't put this in your server.cfg hostname "Counter-Strike: Global Offensive Dedicated Server" rcon_password "yourrconpassword" sv_password "" //Only set this if you intend to have a private server! sv_cheats 0 //This should always be set, so you know it's not on sv_lan 0 //This should always be set, so you know it's not on exec banned_user.cfg exec banned_ip.cfg ``` So, these two sounds like a great idea to add to csgoserver default config file: > sv_cheats 0 //This should always be set, so you know it's not on > sv_lan 0 //This should always be set, so you know it's not on Benefits: - you know it's not on, or it's on - you could set this settings per instance: maybe you want an instance with `sv_cheats 1` for practice, and another one for only lan games (`sv_lan 1`), etc.

kerem

2026-02-27 02:57:59 +03:00

closed this issue
added the
type: refactor

game: Counter-Strike: Global Offensive
labels

kerem commented

2026-02-27 02:57:59 +03:00

Author

Owner

@borzaka commented on GitHub (Aug 1, 2019):

This issue is resolved via:

I think the best practice is to set these values in the config files, not in the command line.

@borzaka commented on GitHub (Aug 1, 2019): This issue is resolved via: - [Game-Server-Configs #68](https://github.com/GameServerManagers/Game-Server-Configs/pull/68) - https://github.com/GameServerManagers/Game-Server-Configs/commit/f5f339b59987b96985b9eeaa01b11f6f929abe2b#diff-e6740dbdb68468b3d1f7c1341bf1152f I think the best practice is to set these values in the config files, not in the command line.

kerem commented

2026-02-27 02:57:59 +03:00

Author

Owner

@ohbus commented on GitHub (Aug 2, 2019):

Kudos!

@ohbus commented on GitHub (Aug 2, 2019): Kudos!

kerem commented

2026-02-27 02:57:59 +03:00

Author

Owner

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

kerem referenced this issue

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

[PR #1589] [MERGED] Update core_messages.sh to allow logging with milliseconds #3364