51–60 of 332 posts
Earlier quoted context omitted.
If I write a cheat for your game that operates on the kernel level, how would you detect it from the game that runs in user space?
Yes, it's an impossible fight. Give up early and just detect the supernatural aim server-side or have a working report system.
Not to say this isn't a worrying practice, but it's unfortunately industry standard. Almost every mainstream fps game has intrusive software, to the point where you're expected to be thankful that it's not a rootkit (which is not unheard of).
Then there's CS:GO, whose developers refuse to use intrusive practices to counter cheating. And the game is ruined by rampant cheating. (Neither for nor against. Just saying.)
A few months ago, their secondary system, "Trust Factor", was broken for an unknown period of time, which the communication to the community was a single tweet. During that period (probably a few weeks?), there was blatant cheaters in half the games I played.
I've moved to playing FACEIT (a third-party matchmaking service) recently, partly due to anti-cheat. I don't remember the last time I saw a cheater in FACEIT, while CSGO's matchmaking has cheaters in around 10% of my games (average skill player, ~2k hours over 7 years, high Trust Factor).
Microsoft should implement an Xbox mode for Windows that has these protection features for all games. It will probably require some virtualization and performance degradation but it's better than each game rolling out their own half assed drivers.
Can anyone tell me why Fortnite doesn't seem to have as bad of a problem as CoD? My son plays both, but CoD really sucks. It is so obvious when someone is cheating.
I think Fortnite uses a projectile bullet model while Call of Duty is all hitscan, but I could be mistaken. It’s been years since I played a CoD game.
This is an arms race that game developers won't win, it's just whack-a-mole. They should invest instead in server-side models for detecting cheating, then it can't be circumvented and you don't need to bother learning all the different ways they can produce inhuman inputs.
Which is already the case and can't work for all use cases. how the server knows that you see behind walls exactly? And ML / heuristic stuff is very limited as well.
Detecting cheating, client or server side is very complicated and not even close to be a solved problem.
Earlier quoted context omitted.
If I write a cheat for your game that operates on the kernel level, how would you detect it from the game that runs in user space?
Easy: code your game correctly and check for impossibilities server-side. But that costs money in development and infra.
Not to say this isn't a worrying practice, but it's unfortunately industry standard. Almost every mainstream fps game has intrusive software, to the point where you're expected to be thankful that it's not a rootkit (which is not unheard of).
Then there's CS:GO, whose developers refuse to use intrusive practices to counter cheating. And the game is ruined by rampant cheating. (Neither for nor against. Just saying.)
Then there's EFT (BattlEye) ruined by rampant cheating.
Then there's (was?) Combat Arms (multiple anti cheats over the years) ruined in-part by rampant cheating.
I wouldn't mind _that_ much if anti-cheats actually helped, but they don't.
Can anyone tell me why Fortnite doesn't seem to have as bad of a problem as CoD? My son plays both, but CoD really sucks. It is so obvious when someone is cheating.
I think Fortnite uses a projectile bullet model while Call of Duty is all hitscan, but I could be mistaken. It’s been years since I played a CoD game.
Earlier quoted context omitted.
If I write a cheat for your game that operates on the kernel level, how would you detect it from the game that runs in user space?
Next will be cheats that run in hardware themselves ... I wonder if it's possible to flash a video card to force wire framing ...