Cheat Engine

jgoemat

For instance I see this code:

STN · Posted: Sat Jul 12, 2014 7:23 pm Post subject:

Not really getting what you mean.

If you mean is there any other way to get the code besides debugging then i am afraid there is not. You can try to find it being referenced (hard-coded) in ollydbg (not sure how in CE) but that is assuming the address is hard-coded/static and accessed directly instead of through registers/allocated.

Your code in the code tags is confusing...this
Address is 7FF63B558A60 (-1028A60 is start of exe)
1028A60 looks like to be an offset not the start of exe.

No idea what the rest of information is.

661089799107 · Posted: Sun Jul 13, 2014 11:21 am Post subject:

If you are crashing then try the other debugger methods and breakpoint types in settings.

If the address of player speed is static then you may be able to find it with: Search->Find assembly code in the memory viewer.

Search for something like: *static_address*

Make sure you change the address range.

jgoemat · Posted: Sun Jul 13, 2014 6:03 pm Post subject:

Thanks for the replies. Assembly scan worked! I just have to search for the entire address (i.e. 7FF63B558A60) and not the module-relative one shows in the disassembly window. Can't believe I didn't see that.

What I mean is that the value I want is at 7FF63B558A60 in global address space. The exe starts at 7FF63A530000. The offset is what it shows in the instruction, i.e. "WolfNewOrder_x64.exe+1028A60". That instruction though uses IP relative addressing, so the actual bytes are "78976F00" or the 32-bit value 006F9778 which is relative to the instruction pointer after the instruction which is offset 0092F2E8. Add those two together and you get the 1028A60 offset from the exe start. If the next instruction was the exact same instruction, that 32 bit offset would be different because it is relative to the instruction pointer.

The problem is that I couldn't find the code that accesses the instruction because the bytes are different each time. With 32-bit games that access statics as global 32-bit addresses it is simple to find instructions that access them, just scan the EXE space for that 32-bit address. With 64-b it relative addressing the bytes are different for each address. "Find assembly code" seems to be just the thing I was looking for.