Cheat Engine

Rawing

As I've had no luck finding a pointer path the manual way, I've tried to use the pointer scanner, and come across a rather weird phenomenon that I don't quite understand.

Every time I start the program and run a pointer scan, I get a bunch of very similar pointer paths like these:

As you can see, most of them end in [568, 7A8, 638], even the shorter ones.

However, when I run another scan, I get completely different offsets:

None of the pointers found in the previous scan are valid any more. I've even tried to increase the maximum depth to 9 and lift some of the scanner's restrictions, and left it running until it had amassed more than 100 gigs of data, but even then NONE of the pointers were still valid after restarting the game.

Quite frankly, I'm stumped. Can anyone explain why this is happening? What can I do to find a valid pointer path?

mgr.inz.Player · Posted: Mon Mar 02, 2015 2:10 pm Post subject:

Does this game use Lua or Mono, or .NET, or Java, or AS2, or AS3, or GML ?

Rawing · Posted: Mon Mar 02, 2015 2:25 pm Post subject:

I don't know, but I doubt it uses any of those. It's an MMORPG. (Don't worry, I know I can't use Cheat Engine to increase my gold and stuff. The stuff I'm interested in is purely client-side.)

Dark Byte · Posted: Mon Mar 02, 2015 2:48 pm Post subject:

your paths have offsets of 638 and 7a8
that's very close to the default 800 limit (2048)

Perhaps the min offset is too small (so instead of a higher level, try a bigger structure/offset size ) like 4096, or even 8192

Rawing · Posted: Mon Mar 02, 2015 4:45 pm Post subject:

That did the trick, thanks!

(Not that it really matters, but I guess all those pointer paths ending with the same offsets was just a coincidence then?)

Dark Byte · Posted: Mon Mar 02, 2015 4:53 pm Post subject:

Basically a coincidence
The pointerscanner searches the memory for a value between the address you're interested in, minus the max offset size.
There's bound to be a few addresses that contain such a value, but are unrelated
The pointerscanner will then take those unrelated addresses and repeat the process till max level, or a static has been found, and fill the pointerlist with those useless pointers all ending with the same wrong offset

This is the main reason you have to do a rescan, since the first scan will always be littered with those entries