feature: command to disable checking for cheat cmds when viewing the demo

[SmileyAG]

No description provided.

[YaLTeR]

So what does this do exactly?

[SmileyAG]

So what does this do exactly?

When playbacking demos that recorded in multiplayer, protected cvars would give the Can't set %s in multiplayer console message
To fix that, we have to fake our cls.state to pass through the Cvar_Command function and after we can restore it to original state

          if ((((*(byte *)&pcVar4->flags & 0x40) != 0) && (ca_disconnected < cls.state)) &&
             (1 < cl.maxclients)) {
            Con_Printf("Can\'t set %s in multiplayer\n",pcVar4->name);
            return 1;
          }

And, there is R_ForceCvars function which calling only if 1 < cl.maxclients and that forcing values to default for specific list of cvars:

r_lightmap
gl_clear
r_novis
r_fullbright
snd_show
chase_active
lambert
gl_monolights
gl_wireframe
r_dynamic
gl_alphamin
gl_max_size
gl_polyoffset
r_drawentities
lightgamma

To fix that, simply don't call that function, but it contains also the updating of changed gl_monolights in real-time, so you have to call GL_BuildLightmaps function for that reason

[YaLTeR]

cls.state is kind of an important variable. If you set it to 1, do commands like disconnect, changelevel, etc. still work?

[SmileyAG]

That's a fair point. It would be more rationally to replace it with set cl.maxclients to 1 instead.

I just didn’t want to make offsets for find that new variable through other functions before, but now I looked at the Cvar_Command code in more detail, and it actually calls a function for which the cls.state values will affect its code (Cvar_DirectSet)

In the case of cl.maxplayers I can't tell at first glance, but even if it may turn out to be the case later, it will be less harmful than changing cls.state