Not making the gamemodes.txt reload automatically makes the system hideously impractical. Why would you even use the new gamemodes.txt when basic things like permanently changing a cvar (without a server restart) is impossible with it? Right now you're enforcing gamemodes.txt on us by installing completely arbitrary restrictions on standard .cfg usage (first and foremost making basic cvars restricted) but at the same time are advertising .cfg usage. I can see the value of the gamemodes.txt style of configuration but this is just an unnecessary limitation. If I want to have this new way of configuring to be my go-to solution something basic like on-demand reloading is a must.
On Mon, Aug 20, 2012 at 9:39 PM, Absurd Minds <[email protected]> wrote: > Sorry I just read your reply to the other email thread. Nevermind my > question > > On Aug 20, 2012 3:34 PM, "Absurd Minds" <[email protected]> wrote: >> >> Agreed. How can I possibly change these cvars when they aren't ever >> executed from a config and can't be changed through console? >> >> On Aug 20, 2012 1:28 PM, "Nick Emson" <[email protected]> wrote: >>> >>> Is there no intention to change this? This will only fuel the anger >>> against >>> the changes if the new system proves to be un-flexible. >>> >>> Particularly misleading is the direction you are taking when the original >>> wiki documentation amended by "ngamache" on 10th May said: >>> >>> "server.cfg >>> This file has been significantly depreciated with CS:GO. It is no >>> longer used as the primary way of configuring the convars of the server. >>> Certain convars, like mp_timelimit, are not even available through the >>> console, as they are now loaded using a different file (see gamemodes.txt >>> below)." >>> >>> So which is it? Use a cfg file as the primary cvar configuration or not? >>> There is no consistency to where this is going if gamemode files cannot >>> be >>> reloaded. >>> >>> Whilst you typically would not expect to change cvars during server >>> operation on paper, the amount of times you do is actually quite >>> surprising. >>> If for example in the midst of playing with friends they propose a >>> change, I >>> do not expect to have to reload the server and have them all reconnect >>> (and >>> lose any public people). Equally I do not expect to make duplicate bodge >>> edits to secondary cfg files. >>> >>> Regards, >>> Nick >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Ido >>> Magal >>> Sent: 20 August 2012 18:00 >>> To: [email protected] >>> Subject: Re: [Csgo_servers] Reloading gamemodes_server.txt without server >>> restart >>> >>> Gamemodes.txt does not reload. >>> >>> If you need to switch between sets of cvars while the server is running >>> then >>> I recommend putting them in a cfg instead. >>> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Russell >>> Smith >>> Sent: Sunday, August 19, 2012 11:02 PM >>> To: [email protected] >>> Subject: [Csgo_servers] Reloading gamemodes_server.txt without server >>> restart >>> >>> In other source games if you make edits to server.cfg the changes are >>> parsed >>> and set when the server changes maps. This doesn't appear to be the case >>> with gamemodes_server.txt in CS:GO. Is there anyway to manually reload >>> cvars from this file without rebooting the server? >>> >>> >>> >>> _______________________________________________ >>> 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 _______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
