Re:Valve bans 40k accounts after laying a trap for cheaters ...
by warent on Thursday February 23, 2023 @02:29PM
(#34915205)
Could just be a simple property that existed on some game object, which was exposed in the interface but nothing in the game ever accessed the property. Then a getter would report the read to their backend. The cheat programs probably automatically read every property of these objects.
[ Parent
| on HN ]
Re:Valve bans 40k accounts after laying a trap for cheaters ...
by jeroenhd on Thursday February 23, 2023 @02:33PM
(#34915271)
I'm no reverse engineering expert but I doubt cheats would actually call getters when they have access to the raw memory underneath.
Maybe lazy cheats do use that mechanism, but it's hardly a foolproof system. If this is how detection was done, I imagine Valve has targeted this detection system for a specific cheat tool/framework.
Re:Valve bans 40k accounts after laying a trap for cheaters ...
by warent on Thursday February 23, 2023 @02:36PM
(#34915309)
Yes I'm seeing now how unsophisticated and probably incorrect my approach is, clearly running into the limits of my understanding of compiled programs / cheat engines :)
Re:Valve bans 40k accounts after laying a trap for cheaters ...
by voldacar on Thursday February 23, 2023 @02:40PM
(#34915362)
A getter? If I write a cheat, I'm just reading bytes from the address of the honeypot in ram
Re:Valve bans 40k accounts after laying a trap for cheaters ...
by jamesfinlayson on Thursday February 23, 2023 @09:50PM
(#34920139)
Possibly - a lot of Source engine (and so probably Source 2 as well) plugins work by reverse engineering Linux/Mac builds of the games and building class definitions for in-game objects and calling the methods to get health/armor/ammo counts etc.