Posted on 14 December 2016 - 09:07 PM
Panda_Chips wrote
Intimidated wrote...
Not saying he hacked, just defending Slet's point
Ok so there is literally no way to prove you don't cheat. He got a combo! Yeah he's cheating banned
Posted on 14 December 2016 - 09:10 PM
Unshift wrote
http://i0.kym-cdn.com/photos/images/newsfeed/000/954/837/12a.gif
Last edited on 14 December 2016 - 09:28 PM by Jahmyr
Intimidated wrote
Intimidated wrote
Unshift wrote...
http://i0.kym-cdn.com/photos/images/newsfeed/000/954/837/12a.gif
Posted on 14 December 2016 - 09:59 PM
Intimidated wrote
Panda_Chips wrote...
Ok so there is literally no way to prove you don't cheat. He got a combo! Yeah he's cheating banned
The more I read your comments the closer I come to dying
Posted on 14 December 2016 - 11:32 PM
-1 like others said gcheat doesn't falseban hardly anyone. And half the time it does falseban the player was probably trying to set it off with its cpsPosted on 15 December 2016 - 03:11 AM
Bladian wrote
GCheat firstly has a 99.95% success rate, meaning that it's almost never wrong.
Now you may have noticed 2 things over the past year, meaning that it now only bans you for "Unfair Advantage"
The hacking community is becoming smarter and smarter, and by banning for "Kill Aura", you were giving clues on how you were being detected, and you could just edit the code, until you got it right.
When you show logs, you're basically showing what logs you triggered, meaning that you're telling the player how GCheat "knew you were cheating"
A developer can reverse engineer these logs, and figure out what settings to change in his hacked client, making it completely undetectable.
The chances of this is low, but it's there non the less.
All you need is a bored developer to take the task of fucking over GCheat and spending time reverse engineering these logs, and you've got a Private Badlion GCheat Bypass.
Basically instead of getting logs, they actually have to get banned multiple times, and have to trial and error with so many accounts, to the point where it becomes repetitive and close to impossible.
Most developers do it for the challenge, so there's always a tiny risk either way.
I'm pretty sure this is the correct reason buy @Archybot would have to give you a more specific answer.
This is pretty remarkably accurate, to the best of my knowledge. We have to remain vague about why someone was actually banned or else we risk helping client developers learn to bypass.
Posted on 15 December 2016 - 05:41 AM
We don't allow this for people who are trying to understand why the got banned who are doing it in a malicious intent to reverse engineer things like GCheat.