Banning stuffcmd

[c0burn]

CSQC.

Good luck with that.

[Urre]

Works great for me

[avirox]

strictly speaking, csqc is not a replacement for stuffcmd.
It provides a client-side reparser for it. Generally that just equates to a localcmd (the local equivelent of stuffcmd...). So yes, csqc can do everything stuffcmd can, but its in no way more secure.

Consider: stuffcmd(self, "cmd rcp $rcon_password\n"); as a method for obtaining the rcon password for other servers.

Then banning localcmd in csqc is the next step :p

Honestly though, a lot of the things that stuffcmd's are used for in ssqc can be done in CSQC without use of localcmd's, such as..

"bf" - In CSQC just make a "flash" image or something
"gl_flashbend" - same
"fov" - CSQC can draw the FOV without changing any cvars
and the conc effect, etc.

There are only a few cases where I can see stuffcmd coming in handy where full CSQC support is present.

[Baker]

FitzQuake 0.85 made BF into an svc_ (might have been listed an svc in FitzQuake 0.80 or prior).

Client FOV settings are part of Quake for better or for worse. FuhQuake and ezQuake have the "default_fov" cvar that will interpret an "FOV 90" command from the server as a request to restore the FOV to normal. ProQuake has this a well because I hate it when a server toys with FOV.

[ceriux]

csqc is a little harder to code with. not everyone gets it and there's still hardly any documentation.

[Teiman]

maybe a "CSQC barebones" is needed. modders don't start from scrach, but "mod" existing things.

[avirox]

maybe a "CSQC barebones" is needed. modders don't start from scrach, but "mod" existing things.

viewtopic.php?t=1560

[ceriux]

what might be better with that is the hud being redrawn with csqc + your menu code. plus many more random coding tutorials....