Cheat Engine

[++METHOS]

Pointer scanner tutorial.

Alternatively, you can use an instruction to find the address each time. Once you find the address, search for instructions that access the address. When you do this, you may have an instruction that accesses that address and only that address. You can add the instruction(s) to your code list and save the cheat table so that you do not have to find them again.

[mgr.inz.Player]

++METHOS +

@kik4444, what METHOS said.

If you found good address, after several crash, etc (but you finally found it), you can use those techniques to speed up searching you do next time:

- check if player coords are always close to something easier to find. For example player health. If yes, you can speed up searching. Find health address. For example health is at 29C41004, coord at 29C4FBC0. So you can set search range to 29C40000 - 29C60000. Next time if you want to find coord address, you search for health address first, for example address is now 12E23304, set search range to 12E20000 - 12E40000

- look around coord address, maybe structure (which have player coord) have some unique values? Or have the same values which are around health address.

You have health address, few bytes before health there is objectID. And few bytes before player health there is the same objectID.

- customType (for example you know that X coord at address XXXXXXX has its EXACT copy at address XXXXXXXX+30). Anyway, this is for advanced users.

[kik4444]

I think the best way might be to find and dissect the base address for the player structure. You never know what you're gonna find. Once I found an address while dissecting Battlefield 4, and if you froze that address, the entire game and everything froze, and unfreezing it caused the game to go back to normal as if nothing happened.
Only problem is - some games can't be ran in windowed mode, so you can't look at the game and the dissection at the same time.

[++METHOS]

SunBeam published this solution yesterday for running ACIV in windowed mode.