Digital Paint Discussion Board
Fairness Enforcement => Cheater Reports and Bans => Topic started by: payl on May 26, 2011, 05:45:21 AM
-
Server: Speed USA
Time: Right now
Name: newbie1720
http://banterous.co.uk/demo/769
obviously download using http://dplogin.com/forums/index.php?topic=22447.0
@jitspoe: Did you removed 'kicked for time disparency'? Many speedhackers can't handle that simple anticheat... Maybe add something similar?
-
@jitspoe: Did you removed 'kicked for time disparency'? Many speedhackers can't handle that simple anticheat... Maybe add something similar?
I'm not jitspoe, but i know it. You can enable it with the setting sv_enforcetime. It is 0, so disabled by default. The [OTB] servers run with "sv_enforcetime 240".
-
I'm not jitspoe, but i know it. You can enable it with the setting sv_enforcetime. It is 0, so disabled by default. The [OTB] servers run with "sv_enforcetime 240".
240 seconds? Isn't this too much?
If most players just use CheatEngine to have speedhack, why don't someone (Jitspoe) just add something which will be called every second and check if time moved by more than 900ms? If it's less than 900ms, then 'something' just decreased delay value... So auto client shutdown/disconnect. Because, as far as i know, CheatEngine just decrease delay value by: original time*ratio=new time. So it's easy to detect, isn't it?
-
240 seconds? Isn't this too much?
If most players just use CheatEngine to have speedhack, why don't someone (Jitspoe) just add something which will be called every second and check if time moved by more than 900ms? If it's less than 900ms, then 'something' just decreased delay value... So auto client shutdown/disconnect. Because, as far as i know, CheatEngine just decrease delay value by: original time*ratio=new time. So it's easy to detect, isn't it?
again, there is a cheat detection for speedhacks. They sometimes give false positives though, so that's why Jitspoe waits for the confirmation that someone has been cheating (read: demo).
-
again, there is a cheat detection for speedhacks. They sometimes give false positives though, so that's why Jitspoe waits for the confirmation that someone has been cheating (read: demo).
Watch banlist, if we make cheating harder, less bans. And more time to development. I think good anticheat, try to catch less irritating cheaters and just tell them 'wrong way'. If someone tries to omit user side anticheat, then server anticheat goes on, and global ban incoming. Client side anticheat doesn't care about lags/internet problems. We can clearly say, that if on someone PC 1second is less than 900ms, then something is wrong, so just disconnect from server. Good anticheat tries to kick simple cheats rather than forcing Jitspoe to check demo, find IP, get global data and add ban. So he could develop more.
-
Names used:
newbie3888
newbie1720
newbie
IP: 201.27.15.76 = 201-27-15-76.dsl.telesp.net.br
payl: It does seem like an automated speed cheat detection should be simple to implement, but I continue to get false positives regardless of what method I use (even detecting on the client).