Cheat Engine

[NvrBst]

Sometimes, the value I'm looking for has a bunch of locations and figuring out which one (after a restart of the program) was the one I was searching for can be a little tedious, and usally requires some debuging. If under the

"Rescan Memory - Remove Pointers not pointing to the right address"

you could add a "Rescan Memory - Remove Pointers not pointing to the right value" (Much like the "next scan" button does, but with just the "exact value" option), that would be fantastic for a future release


Also some small bugs, If you do an "Injected Scan", then close the 2 windows that pop up. Then it wont let you do an "Injected Scan" again. Simular thing happens if you try to attach a debugger ("Find out what access's this address"), have the address get accessed, then stop the debugger and exit the window, it then wont let you do the "Injected Scan" (Can do "Default Scan" though at anytime).

And this last one probably isn't a bug, but if you get to the "Injected Scan" window, and then try to "Pause Process" it'll freeze the "injected scan" window too. (have to pause process then click the "injected scan").

[Dark Byte]

about the value scan, I'll see if it's possible, but why not just scan for the value yourself using the standard scan routines and then scan for the address you finally find ? (that'll get more wrong pointer paths, since there is a chance that even a wrong pointer path points to a address with the correct value.

about the debugger problem, do you get a error or will it just not open ?

and the pause freezing the injected scanner isn't really a bug, since the injected scanner becomes part of the target process it'll be affected by anything ce does to it as well

[NvrBst]

the Debugger->Injected Scan, or Injected Scan->Injected Scan, there is no error, just nothing happens when you press the 2nd "Injected Scan" (no pop-up's).

And what I mean for the Value Scan... Well for example say I'm searching for a value which tells me if a window is up (0 if no window, 1 if window). So I search for the value and then keep tuning it (using "Next Scan"), then I get to something like this

0x0E660834
0x12BBDAAA
0x12C40DFC
0x12CB1FD4
0x12D27ED8
(6 more values in the scan I just did).

All 11 seem stable (turns to 1 when the window I want is up), 0 otherwise.

So I take the 0x12BBDAAA, Add it to the "Pointer List", pause process, right click > Pointer scan for this address. Do a level 6 scan with 0x4096 size. Go to bed. I wake up and have about 1M pointers.

I save the list, shut down the game, and restart it. I then have to search for the address again, so I do and find the 11 values. But I'm not really 100% sure that the first (new) 0x12xxxxx value that I find is the same address that was used for the Pointer Scan I just did (IE maybe everything in the 1M pointers I have actuall all point to the 5th 0x12xxxxx address now).

In this respect, it'd be a lot easier for a person to sift through the 1M pointers by poping up the window, and go "Rescan Memory - Remove Pointers not pointing to the right value" and give it a 1. Take down the window and do another "Rescan Memory - Remove Pointers not pointing to the right value" and give it a 0. That way I can definally be removing pointers that don't work untill i'm down to (hopefully) ~10 pointers. Then I can just add them all to the Pointer list and manually find the one I want, and also make sure they always giving the right information