Allow CVARINFO cvars to be latched

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Allow CVARINFO cvars to be latched

Re: Allow CVARINFO cvars to be latched

by Major Cooke » Sat Nov 11, 2017 8:16 am

That's precisely what I am hoping for.

Re: Allow CVARINFO cvars to be latched

by Rachael » Fri Nov 10, 2017 11:15 am

Keep in mind even if you do this, CVAR latches are only saved on the console side.

If you modify the CVARs internally they will not latch.

Re: Allow CVARINFO cvars to be latched

by Major Cooke » Fri Nov 10, 2017 10:34 am

Agreed, a useful one. It should be a keyword: "latch".

Re: Allow CVARINFO cvars to be latched

by ZippeyKeys12 » Thu Nov 09, 2017 7:55 pm

Very interesting, would actually like this too. Currently I'm storing the CVar as well, but it would be nice to have the latch warning, provided that it's feasible to do.

Allow CVARINFO cvars to be latched

by argv » Thu Nov 09, 2017 2:44 pm

I see that the “skill” CVar is latched. Changes to it do not take effect until a new game is started, and it says so in the console.

Please allow CVARINFO-defined CVars to be latched like this, as well.

The intended use case is to have additional difficulty settings that, like “skill”, only take effect on a new game. Currently, the only way I know of to do that is to capture the CVars' values upon game startup, and store them in a global somewhere, but that doesn't make the latch warning appear on the console.

Top