Here is the deal, the client was forcing sv_cheats to 1... This doesn't happen unless there is a "hack" trying to force it. You can't just type sv_cheats 1 in console and get banned for it nor can you accidently bind a config file to it... Somehow, the client is trying to force sv_cheats to 1.... This doesn't happen by accident.
I don't know you well breaker, but if your really innocent, lobbying on here isn't going to help your cause. I would go do some research (again, if your really innocent) and figure out how in the hell you client could do it. This has never failed before so I'd say without hesitation that the burden of proof is on you to give.
I don't know nor care if you hack or not, but if you think your innocent then go research... I'm afraid that due to the complete and utter accuracy of this type of ban in the past, there isn't a lot of hope for you through arguing.
---------------------------------------------------------------------------------------------------------------------
This "system" is not a anti-hacker tool. It doesn't catch all hacks.. it checks cvars... Consequently, a lot of hacks alter client side cvars, so it catches many hackers... but it's a cvar checker more than a hacker catcher...
Bookmarks