Re: Next release, early 2010
I know we're in the aftermath, so there is no point on saying this but...
Why don't you just disable the cvar 'cheats' so it can't be activated unles the dll is compiled with it (Maybe comment it on the source, or do an #if)?
I mean, that would let you make sure there are no exploits related to it (and makes your job easier
). Besides... no one should use it, and for testing porpouse, you can simply make that #if statement true.