Cheat Engine

[pox911]

I tried searching but didnt get an answer that way .

Is there a way to reduce the size of a pointerscan file? I can understand the first initial scan taking up a decent bit of a space but after i got the results down to 1k or so the file shouldnt need to be so big .


Also my sugestion would be for an easy way to update everything but the last level of a pointer. My reasoning is that after an update some pointers break or you find out your aob was wrong and you have to update the info again. Someimes you have a large amount of codes that used that base pointer and only the last level is different. It makes it tedious to update .

[Dark Byte]

the size is that big for quick lookup and display. The addresslist isn't really stored in ce's memory when shown, but read directly from disk each time you scroll. To make this fast cheatengine needs to know exactly where a pointerentry starts and stops. If compression was used CE would first need to decompress everything untill it would have found the entry it's looking for

But what you could do is make use of windows's folder compression.

as for the update, it's more often that the base address has changed (since the code might have changed size , causing the .data to shift) but the offsets stayed the same.
For that the recalculate addresses function will let you change the base pointer of multiple addresses at the same time with a specific offset

An option to update only the last level is too specific to be implemented as a default option though, but it can be added with lua. (Go through the addresslist, get the offsets, change the last one and set it as the new offsetlist)
(But perhaps editing it in a texteditor might be easier)