3 ms·
From the game's perspective this was a cheat. The anti-cheats job is to make sure nobody tresspasses with the game logic. They modified where methods returned
by filterfiber 3y ago
From the game's perspective this was a cheat. The anti-cheats job is to make sure nobody tresspasses with the game logic.
They modified where methods returned to so they could run their own code before returning to the game.
VAC cannot determine if this was a bhop-wallhack or an anti-lag feature.
It just sees that someone modified the game.
This is like walking up to someone's building and spray painting a mural without permission. No matter how innocent or well intentioned it is - internal modification is a red line.
- rat9988 3y agoBeing caught by an anti cheat doesn't make you a cheat. This a false positive.
- filterfiber 3y agoSo yes it is a false positive, but it's not the type VAC is concerned about. What AMD did was like crossing the DMZ. It doesn't matter who you are or what your intentions are. It's not possible for normal applications to do this unless they're specifically trying to. You cannot cross the DMZ without special permission, and even then it's more likely valve adds it directly to the engine instead. There's more "accidental" type of detections which would be false positives too - but this is a clear line in the sand AMD crossed. --- There is no anti-cheat that will let you do this. You contact valve and work with them to add support in engine. What AMD did was insane.