5 ms·
Readme seems out of date, seems to be detected by ESEA and FaceIt, unless the hardware ID mitigation fixes that. Shouldn't the hardware ID be randomised to sta
by sk0g 7y ago
Readme seems out of date, seems to be detected by ESEA and FaceIt, unless the hardware ID mitigation fixes that.
Shouldn't the hardware ID be randomised to start off with? Not that I plan on using this either way, though.
- bri3d 7y agoThe detection is based on hardware ID interrogation, yes. Here's an ESEA blog post about it although of course they don't go too far into their methods, besides claiming they go "beyond just hardware ID" : https://blog.esea.net/esea-hardware-cheats/ https://blog.esea.net/esea-hardware-cheats/ . My suspicion is that they interrogate "suspicious" devices in various ways (for example, seeing if the IO mechanism provided by the driver for each device installed in the system can be used in the expected way), but this is of course easily defeatable.
- sk0g 7y agoHave you tried to honeypot the ESEA client? See what digging around they do, log absolutely everything you can, and see what you can learn from it. Ugh, now I want to write my own game cheats for the sake of curiosity!
- ryanlol 7y ago> but this is of course easily defeatable. How so? Is it really common for non-cheaters to have exotic PCIe devices connected? You could certainly build the cheating functionality into a common PCIe device, but I’m not sure I’d call that easy. There may not be enough money to be made from cheating on ESEA to justify such efforts.