Cheat Engine

[mordax]

I made this, because i have encountered a lot of stupid bugs and errors in CE. i report these so CE can be made better, not to tell how stupid Dark Byte is. almost every software has issues, nothing strange there.

1. when using "array of bytes" search type, filter option only allows to filter for exact value. For example i know the exact value in bytes (i know it can be converted, but not the point here). So bytes are "AA 00 00 01", but then i know it changes, but don't know to what. so i want to filter changed, but it won't allow.

2. when using 1 byte scan, 255 is not considered as 1 byte, which is wrong. Im sure DB knows what byte is, but to others. 1 byte can hold FF which is 255 in DEC. however if i want to search for 255 using 1 byte, it won't allow. it changes it to 55 as soon as i do first scan.

3. when doing pointer scanning. it allows only float, 4 bytes and double, but what about 1, 2, 3 bytes ? and array of bytes ?

4. when doing a pointer scan, choosing 4 bytes, you can't enter 4 byte value to be searched. FF FF FF FF = 4294967295 << this value cannot be entered using 4 bytes. it allows only 8 digits, not 10. why is it 4 bytes, if i can't enter 4 byte value. it is obvious bug.

5. I think i mentioned this in some other topic, when creating header in cheat list, it loses it's hotkey upon saving the table and then loading.

6. 3 bytes search option is missing, which is necessary in some games. in one of the NFS games, money could only be found using 3 bytes search, i can't explain it, but that's how it was. most likely using 1 byte search unknown would have worked too, but 3 bytes could exist. or better yet, custom byte, that you can search for 3, 5 ..etc

7. search type ALL would be handy to have, like ArtMoney has it. it will search all possible fields, float, double, byte/s and even strings.

8. CE could have autosave feature for session. so if i dont save my stuff and something happens, it should autosave every x seconds/minutes. i have lost lot of work because it crashes sometimes. would be very handy to have autosave.

I dont know if its because of some settings, but to me Tsearch works a lot faster using 1 byte search unknown. CE sometimes even crashes.
for example i do first search using 1 byte unknown (or well just unknown) and then filter for changed / not changed on 1 byte. CE takes about 10 times longer. any ideas ? otherwise CE works faster than Tsearch, it's just that 1 byte search. and on top of that, CE sometimes won't find the addresses that Tsearch finds using 1 byte search. i have gone thru options, there are no memory range settings applied to CE. i'm not a rookie/noob so i know what im doing. i just dont know what might cause it.

i hope my reports and suggestions help.

[Dark Byte]

I'll check it out. (although it's too late to make it to ce 6.2)
As for 6, that is what custom types are for (set the bytelength to 3)

And seeing that you tend to scan for 1 and 2 bytes a lot, and can't find values, I suppose you're scanning inside an emulator? In that case, make sure mem_mapped is checked in settings
And change the buffersize to 4 in scansettings for the 1 byte scans