Cheat Engine

[cooleko]

I know that cheatengine is open source, so I was hoping to get some tips in incorporating my lazy version of automated manual pointer scanning.

That is: Right clicking an address in the list and having a selection for "lazy pointer scan" which will steal the code from "find out what accesses this address" and automatically scan for the guessed memory address holding the offset, all the way down to a static address to generate a small list of the 'manually' derived pointer chains.

I know that it would be really basic, but it would save some effort in doing it manually, and may have a result in just a few seconds (or several minutes if you have to play the game while it scans to force pointer changes such as buying/selling or zone changes).

Once I have that generated, then I am thinking I could have a "find out what accesses this address" actively running for each address in the chain, to steal the code that actually changes the pointer in order to generate a better offset.

I have been putting off this project because I stopped using pointers in favor of AOBs, but I would still like to do it eventually.

Any tips on where to find that specific source code of the find what accesses this address and the right click dropdown list would be appreciated.

[hhhuut]

Have you already discovered the pointer scanner?

When you right click an address you can choose "Pointer-scan for this address", which I think is exactly what you're looking for ...

[cooleko]

I want to automate the manual method. Results not guaranteed, but fast.

If I wanted to wait for hours I could, but I'd rather get a few cheap easy results that may work before waiting around.

[hhhuut]

When do you wait "for hours" with the pointer scan???

[Dark Byte]

for some quick easy results I also recommend the pointerscan

in advanced options enable "max different offsets per node" and set a very high offset (the max node basically overrides the offset)

this way it won't go in too deep into paths with high offsets, and the results you get a generally really good and really fast as well

[cooleko]

I'll try that, my last experiences with pointerscan were before the shared scan and before the multiple pointermaps as well, so there are features I dont know how to use.

I frequently ran into scans 7-10 deep that take several hours to run (in the past when I was using offsets instead of AOBs)

The last bot I wrote, pointerscans 9 deep took two days to run on a 980x, two 480s (impressive for ~2010), and multi-tb HD; but I needed those offsets! Rescans also took 5+ hours on those pointers. Once I got the first offsets, refining them took minutes because I noticed patterns from easier to obtain offsets.

Is there a new guide on how to optimize pointerscan with these fancy new features?

[Dark Byte]

The limit by nodes is the best way to speed up the scan. (you can even do very deep level scans)

Besides that, using secondary scandata files will save you on harddisk space. Instead of writing trillions of useless results to disk, it only writes results to disk that match both states of the game.

And if you have multiple fast systems you can let them join in on the scan.

[panraven]

The OP mention "find out what accesses this address" which is break point related. I guess OP want to gather the break point information of target address to aid pointer scanning, may be by examining the disassembled lines?

Try search ce git repository for desired source?,eg.
https://github.com/cheat-engine/cheat-engine/search?utf8=%E2%9C%93&q=%22find+out+what+accesses+this+address%22

=> MIFINDWHATACCESSES

=> FoundCodeUnit.pas

...

bye~

[babsfall1024]

I ve been around for many years and you guys are doing an awesome job. registered on forum just to say, because of your handy work from a hardcore gamer I drifted to become a code junky lol ...and i am learning a lot thanks

tested CE with my galaxy 4 SM-T231, it's working like a charm and I manged to do some mem editing. I use the PC gui to hookup with ceserver and its the best way to go i think.

glitches/bugs:
- when i hit cancel button in a middle of a search, ceserver freezes
- when trying to find out what access/read to some memory it shows 1 result before freezing. killing ceserver(hence killing the target in the process) and reloading it will resume both pc gui and the android app
-will report more if i find any...


final note: this app have an unparalleled potential and I expect it to be the ultimate tool the moment debugging target is effective (disassembly&setting proper break points )

cheers