Why not just use gamemode_XXX_server.cfg? This way you can let
gamemode_XXX.cfg update as it should.
TigerOx
On 2012-09-06 11:54, Tackdriver wrote:
Hey just wanted to give folks a heads-up about this so you
(hopefully)
don't get caught by it on the next mandatory update:
I had occasion a day or two ago to re-run the SteamCmd updater with
validate, and it proceeded to replace the cfg/gamemode_XXX.cfg files
(like
cfg/gamemode_casual.cfg) that came from last week's update.
I had edited mine to "blank them out", containing only a single line
to
echo the name of the config file that was being executed, but all 4
of
them (gamemode_casual.cfg, gamemode_competitive.cfg,
gamemode_armsrace.cfg, and gamemode_demolition.cfg) got replaced as a
result of the update, and all the "strange" things that happened to
the
servers configs after last week's update happened again.
So I ended up adding some stuff to the small script I wrote to call
the
SteamCmd updater, to put the cfg/gamemode_XXX.cfg files *I* want the
servers running back into place after updating.
Probably a good idea for everyone else to look at this too.......
Cheers,
Tackdriver
_______________________________________________
Csgo_servers mailing list
[email protected]
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
_______________________________________________
Csgo_servers mailing list
[email protected]
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
