I agree. Most points of entry are usually via injection, and you need to maneuver around the anti-cheat defense. Once the game code isn’t in parity with the server, it’s also likely to be rejected; this leak is likely older anyway, so probably a non-issue since it’s not feature complete at this point.
It may help identify new points of entry for injection, but that’ll likely get patched once exploited.
Got_Bent@lemmy.world 10 months ago
Wow. I used to use a sector editor on floppy disks to cheat on games way back in the eighties by looking for player stats and abilities and whatnot. I had no idea that modern day cheating would be so similar to the rudimentary stuff I was doing nearly forty years ago.
d3Xt3r@lemmy.nz 10 months ago
The core ideas remained the same, only difference is that they’ve got more roadblocks now which makes it considerably tricker (security measures in the OS + anti-cheat + encryption/DRM + server-side checks etc).
But modern day cheating goes beyond memory editing, for instance there are things like aimbots which can work at the GPU/driver level, or input automation/macros which work completely ouside of the game so normal anticheat measures may not prevent it.
ilinamorato@lemmy.world 10 months ago
Yeah, computers have a lot more bells and whistles now, but the basics of how the system and the OS work haven’t really changed that much, until you get out of native apps and into Electron and stuff. It’s honestly remarkable how similar they are. Microsoft has a bunch of documentation about weird and quirky behavior they keep available for backwards compatibility, and most modern software developers take them up on that offer.