On Fri, Aug 31, 2012 at 3:48 PM, Tackdriver <[email protected]> wrote: > >> Put it in your gamemodes_server config. > > That doesn't work anymore after last night's update - see my earlier post > for a detailed write-up of this.
I hate to be "that guy" but would it be possible to get a copy of that write-up? I've looked all over and am uncertain exactly how to transition to the new format after this latest update. I'm not even sure at what point to chop out the settings and place them in the new modes files. And whether I need to create both the mode server files *and* the mode server override files. Everything I've read outside of this list is pure speculation (followed by arguments as to whether its right or wrong). Anyway, I just subscribed to this list today, so I haven't seen your write-up and I get a 403 trying to access the CS:GO list archive. Thanks and regards. >> On Friday, August 31, 2012, Nevermore Imperium wrote: >> >>> how do you change hidden cvars without manually executing sm_cvar? > > > put it in a .cfg file like server.cfg: > > sm_cvar sv_minupdaterate 33 > sm cvar sv_maxupdaterate 128 > > > >>> >>> Thanks >>> >>> 2012/8/31 Chuck Gibke <[email protected] <javascript:;>>: >>> > Thanks for the research. I plan to get my config files sorted out >>> today. >>> > .......O&S >>> > >>> > >>> > -----Original Message----- >>> > From: [email protected] >>> > [mailto:[email protected]] On Behalf Of >>> Tackdriver >>> > Sent: Friday, August 31, 2012 6:18 AM >>> > To: [email protected] >>> > Subject: Re: [Csgo_servers] Config Files >>> > >>> > Mostly correct that I see -- I've been working on figuring this out >>> too. >>> > >>> > Unfortunately, +servercfgfile (server.cfg usually) gets executed >>> *FIRST* >>> > ahead of the other .cfg files (gamemode_xxx.cfg, >>> gamemode_xxx_server.cfg). >>> > >>> > I just proved this out by sticking: >>> > >>> > echo Executing (this-filename).cfg >>> > >>> > at the top of each file and starting the server. >>> > >>> > Also, all 3 of them get run on every map change in the same order: >>> > >>> > 1. server's config file (+servercfgfile cmdline arg or cfg/server.cfg) >>> 2. >>> > cfg/gamemode_xxx.cfg 3. cfg/gamemode_xxx_server.cfg >>> > >>> > after these, if you have defined any other exec statements in the >>> server's >>> > customized gamemodes_server text file, any you defined get run. But >>> only >>> > AFTER the above 3. >>> > >>> > In fact, even if you are using a custom gamemodes server file (via the >>> > -gamemodes_serverfile server cmdline arg), it is STILL going to run 1 >>> and >>> > 2 if they exist, even if you don't have them listed in your custom >>> gamemodes >>> > server file! >>> > >>> > Now here's the real kicker: >>> > >>> > NONE of these allow setting hidden CVAR's. for example, >>> sv_minupdaterate. >>> > If you want to set those, you still have to do use sourcemod to do it >>> via >>> > sm_cvar (assuming you're using Sourcemod). >>> > >>> > So basically, now we have a BUNCH of EXTRA config files to mess with, >>> some >>> > of which are already pre-populated samples. So if you're wondering >>> why >>> your >>> > server isn't obeying your configs after this update..... >>> > >>> > >>> > I hope we can still set convars via the gamemodes server file, but, >>> then >>> > again I won't be all that upset if we can't. Thank God for sm_cvar. >>> > >>> > All of this was a lot simpler when ALL CONFIG was via straight config >>> files. >>> > >>> > Sure would like to see per-map .cfg files though, or if we're supposed >>> to do >>> > that via .kv's now, a working example map .kv file that sets >>> map-specific >>> > cvars. There are some maps that are "fun" to play, but not for the >>> > mp_timelimit amount of time you have the default server config set to. >>> > Stuff like that. >>> > >>> > --- >>> > >>> > So, it looks like the "convars" key in your server's custom gamemodes >>> text >>> > file is no longer used either. Just for the heck of it I tried >>> putting >>> the >>> > "hidden" cvars in there that it used to let you set there (before last >>> > night's update) and they were not set. None of them. >>> > >>> > So again, thank God for sm_cvar. >>> > >>> > I won't complain about this. It is a step in the right direction IMO >>> - >>> > making running these servers more like it used to be - strictly via >>> .cfg >>> > files. We're used to some cvars having to be set via sm_cvar. >>> > >>> > Just as long as those cvars remain settable via sourcemod. >>> > >>> > >>> > I never saw much/any value to defining server cvars in a key-values >>> text >>> > file that obviously doesn't get re-read on each map change, or that >>> the >>> only >>> > way to make the server re-read it is to restart the server. That >>> alone >>> is >>> > reason enough to not put cvars you care about there. Except the kind >>> that >>> > you know you'll never want to change. >>> > >>> > --- >>> > >>> >> Apologies for incomplete message earlier - accidentally clicked >>> CTRL+S >>> >> >>> >> Correct me if I am wrong about any of the following: >>> >> >>> >> - cfg/autoexec.cfg >>> >> - executed first >>> >> - gamemodes.txt >>> >> - never touch >>> >> - executed first, and once >>> >> - gamemodes_server.txt >>> >> - edit this with changes to convars available in gamemodes.txt, >>> >> model >>> >> >> >> >> >> -- >> >> >> Kind regards, >> Saul Rennison >> _______________________________________________ >> 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 -- Seumas _______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
