Cheat Engine

stomperz · Posted: Sat Dec 03, 2005 9:28 am Post subject: Save memory region(s)

DB when using Save memory region(s)
I don't chk the "Don't include Cheat Engine header in file"
But when I load it asks me for a start address and I cannot edit the address.
Get an "list index out of bounds (0)" error.

If I chk the box and save the file, i'm able to give the loader the address.

This happens whether I save single or multiple regions.

edit: This used to work, but I haven't used it in awhile.

cparty · Posted: Sat Dec 03, 2005 9:53 am Post subject:

in CE5.2 loading files without the header worked fine for me, but I wasn't able to load those with header. When looking at the dumps it looks like there is no address range saved along with it. Anybody else noticed?

Dark Byte · Posted: Sat Dec 03, 2005 11:08 am Post subject:

I'll add it to the list

Dark Byte · Posted: Tue Dec 06, 2005 9:49 am Post subject:

if you redownload ce you will be able to use it (And it DID save the address regions, startaddress+size, just didn't load it right)

cparty · Posted: Tue Dec 06, 2005 9:57 am Post subject:

thanks DB

Zhoul · Posted: Tue Dec 06, 2005 5:54 pm Post subject:

I'd like to request a feature for future versions of CE, related to this.

Often times, I'll want to copy hex output in a certain memory area and have to revert to that horrid 1/2 ass util "Memhack".

2 sub-features.

Bytes per row:
Number of bytes until a space is placed in between:

In this example, lets say I asked for a range of 60 bytes, 20 per row, spaces every 4 bytes.

0000 0000 0000 0000 0000
0000 0000 0000 0000 0000
0000 0000 0000 0000 0000

Of course, readable in .txt format.

This, more for data reviewing and sharing (as it was hard to look at a situation as describeb above, quickly and easily, as CE will shrink and grow based on 'logical' sizes, i.e. 8/16/32, which is a feature i love... but in this case, 16 byte chunks of data was separated by 4 bytes of separation data, making it hard to 'skim' through. Using the 8-byte per row feature actually helped, but would have lined up much better in a 20-byte per row scenario.

I wouldn't even care if it supported loading features, but I can already think of ways that could be useful as well. (Similar to AutoAssemble scripts, but without all the snazzy features).

The 'save disassembled output' is already a *huge* help in the tutorials I create... I'd just like to also be able to include memory regions that are effected, without having to post screenshots, which , on this site, all collect at the bottom of the post, making it harder to make a 'flowing' tutorial.

The sharing idea comes from the recent project with NFS-MW, as we could have saved eachother a lot of time, description and typing.

- Zhoul