A thing I noticed with the new (v30) binaries.
Do you remember about cl_yawspeed and cl_pitchspeed (turning around using keyboard)?http://openarena.ws/board/index.php?topic=4466.0
They were hard-coded
to their default value (140) in official 0.8.5 and 0.8.8 binaries (as some sort of anti-abuse protection). You were able to change them to any value you liked, but the game continued to work as if they were set to 140. It has been pointed out that was a strange behavior, that may confuse users.
In the new test binaries, you are not allowed to change their values anymore. They do not appear as "cheat-protected" (even in devmap mode, you cannot change them), but as "read only". You cannot
change them when playing, or when playing demo, or from main menu, or from devmap mode....
The problem is... if you change them form 0.8.8 binaries (e.g. set them to 500), then launch v30 binaries, it keeps the "500" value, uses it
, and prevents you from changing it again.
Well, changing their values from old binaries is not the only way to "workaround" the lock
... you can change them also simply text-editing your q3config.cfg file, or starting openarena with "openarena.exe +set cl_yawspeed 500".
In other words, the new lock is not good enough yet.
I can imagine that the old kind of lock (unelegant) was done to be not "workaroundable" in any way (unless using unofficial binaries). However, I suppose it should be possible to prevent abuse also using the "elegant" lock in some way (maybe resetting to the default value on program start/match start? Or making the variable as cheat-protected? I don't know...)...
I don't know if you thought about a way to let server admins to decide if their players would be allowed to customize such variables or not (it was one of Corvette's thoughts) or allowing some ranges of freedom... e.g. using "dmflags" or "videoflags" (ehm.. its not "video"... maybe the old name "fairflags" would have been better for that)
Another thing: strangely enough, if you type /cl_pitchspeed
ENTER, it says its current
value only, and it doesn't say ", default value is 140"
! I don't know the reason of this (maybe because, being a read-only variable, it thinks it may never
be changed? Wrong!
), but hope it may be fixed and the default value being mentioned.