this post was submitted on 14 Nov 2025
634 points (99.2% liked)
Linux
10136 readers
712 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ultimately you either have basically google stadia (with all its technical problems) or you are trusting the client to render the game.
Even if the client only has exactly the absolute minimum amount of information needed to draw all the things that are visible, that still allows a cheat to see the player coordinates and the coordinates of visible entities, which usually makes eg. an aimbot trivial to make.
Rendering is not what you are doing server side.
Servers would just be checking to make sure a player can actually do something and if they can't don't let the client do it. Then any changes made client side would only affect the player making the changes.
It boggles my mind Riot would rather use a hacky method like kernel level anti-cheat instead of just having the servers mirror the game logic and confirm everything. Its all about saving money at our expense.
No shit sherlock. Rendering requires information about the game, and that information is enough to allow cheating. Aimbots don't need to perform "invalid actions" in order to wreck a game. They just need to be faster and more accurate than most human players. Trying to heuristically detect aimbots is also commonly used alongside other anticheat methods, it just doesn't work (unless you have people manually reviewing individual reported cheaters, but companies try to avoid that because it's expensive and risks false positives).
Right. Nice to find someone here who actually understands some of the problems that make kernel level anticheat important. In modern FPS, server authoiritative everything is just not feasible. No gamer is going to accept the latency that would cause. Or when you look and suddenly you momentarily desynced and now your camera jerks back because the sever decided you tried to look around too quickly? People are so willfully ignorant about this topic.
maybe we could get away from needing it as badly if valve would provide a strong attestation that the kernel running is unmodified with a secure tpm solution, but they haven't, so here we are.