Yup setting the servers to pure 1 or 2 will sort the sound/model hacks. Setting for server 1 and 2 is pure 0, server 3 is set to1 though. The reason is quite a few people like the have custom weapons etc but if cheating gets out of hand we will up the pure settings of course . Aimbots only work for hitscan weapons though so don't blame hacks when you get owned by soldiers or demos

On sv_pure 1 can't you set the whitelist.txt to allow some custom content. Don't use any custom myself so not sure what other ppl might use, but wouldn't allowing custom sound/weapon models/sprays be ok and then banning custom player models since they are easily abused

In any case it would be nice for Valve to provide the means for any statistics plugin to obtain the player crit ratio, dps, dph. That would answer a *lot* of dubious questions. WHY WON'T THEY DO IT, WHY LORDDD WHYYYY? </fit>

I do use custom models and sounds, so I don't particularly want pure on in any form. It things like that which kill the customisation community.

Of course you get people who would abuse it. But be honest, games aren't usuallly fair at the best of times. Pure on won't stop team stacking or snipers who sit in one spot all match just for kills (I've seen plenty of both).

@Spiderbloke: Agreed, but the crucial difference between cheaters and mechanics abusers is that the first group outright hacks/breaks the game code to achieve what they want, whereas the second one relies only on mechanics handed out already by the game itself.

That's also one of the differences between a great, well thought-out game and a bad one. A well designed game won't be as susceptible to "grief tactics", whereas a bad one will be full of ways for ppl to abuse game mechanics. Both however are ruined by cheaters. And that's what should be first and foremost be prevented.