Cheat Engine

h3x1c

Hey everyone,

Alright, so, I've got the following bit of code related to ammo in this game I'm hacking:

ParkourPenguin · Posted: Sat Jan 02, 2016 11:26 pm Post subject:

You could backtrace it using the "break and trace instructions" option in the right click menu in the disassembler. Pause the process beforehand and make that a conditional breakpoint using the breakpointlist if you need to.
Topic on backtracing here.

You might also be able to look around the instructions that read from the address of your ammo. You might find that cmp around (likely after) one of them if you're lucky.

h3x1c · Posted: Sat Jan 02, 2016 11:39 pm Post subject:

ParkourPenguin · Posted: Sat Jan 02, 2016 11:57 pm Post subject:

That routine being called by call DP.exe+19F170 is probably pretty large. Try selecting "step over instead of single step" when doing the break and trace. That will step over the call (and any other calls). It'll still execute them, but it won't track them.

Then, in the window that pops up, right click in it and select "expand all". Double click on the instruction after the ret 0004, and it'll take you to that instruction in the disassembler. Above the instruction it takes you to should be the call that called the subroutine you posted above, and slightly above that should be whatever instruction pushed the argument [esp+04] onto the stack for that call.

You could also go one step further and (using the break and trace window) look at what called the routine that called this subroutine, then break and trace that routine just before the call to the routine that called your subroutine. It'll give you more information like the value of the registers at the instructions leading up to the call to your subroutine.

PS: backtracing sucks. There might be a better way of doing this that I can't think of right now, but this is a surefire way of doing it.