Cheat Engine

[shakib187]

For faster and more reliable results for finding base addys?. I sometimes reduce the size from 2048 to 1024 for faster results doesn't always work tho

[Dark Byte]

try improve pointerscan with gathered heap data
or "first element of struct must point to module"

and ticking "max different offsets per node" and setting a low value will also greatly reduce the number of useless results and increase scantime (that option will result in pointerpaths with low offset values, which is usually what you need)

[Gniarf]

You can use:
-Path must end with...+enter a few offsets found by debugging (finding at least the last offset is usually easy).
-Stop traversing when a static...
-No looping pointer.
-If you're sure you want the base address to belong to a specific module (like game.exe) you can enter whatever game.exe+1000 and game.exe+size_of _your_game correspond to in the base address must be in range. Use memory viewer->view->memory regions to find where your game ends. (@Dark Byte: if it makes less hdd writes, it does make the scan faster)


I also disallow stack address since I always choose pointers with a base in module+XXX in the end when it comes to manually picking a pointer.