I'm attaching a game's process to view/edit my ammo. I've reversed a few games and understand x86 assembly; however, I'm new to the whole anti-debuggers and memory scanning bit. I have searched for resources on how to combat this issue, but still have found nothing. Whenever I attach to the game it still works, but as soon as I change a single instruction it's as if the application "scans" it and detects my change, thus causing a crash. Also, sometimes if I happen to "bypass" the detection, the anti-cheat always finds a way to kick me out.
I've read about a few functions that some programs may use, but none of them have really seemed to help.
- What do these games/applications use to detect this?
- Is there a way to avoid this detection?