Cheat Engine

[main9dog]

Frequently modifying values in games may lead to gaining experience in identifying nearby locations. Sometimes, when changing adjacent positions to test if they correspond to on-screen elements such as health, MP, maximum values, usage counts, etc., the values in the memory location table may appear the same. In such cases, guesswork becomes necessary.


Scenario 1:

At times, modifying several nearby positions to different values for testing purposes can be confusing. For instance, altering values like health, MP, maximum values, usage counts, etc. When multiple values look the same in the memory location table, it becomes challenging to recall which positions and values were recently altered.


Scenario 2:

For finding item locations, consecutively incrementing several positions by 1 to test hexadecimal correspondences can be troublesome. In such cases, entering random hexadecimal values in the memory location table becomes a workaround.


In the past, I used another software that offered the following features:

memory table.JPG

For example, in the memory table above, there are many 【01】, and I don't know which 【01】corresponds to the 【1】 in the game. In such situations, I need to intentionally change each 【01】 to a different number. However, Cheat Engine doesn't highlight or provide a way to undo these changes. After making modifications, I can't remember which positions were altered or what the original values were. I assume many people encounter this challenge, right?



《1》

It would highlight in yellow to remind me of recent modifications.

(In Cheat Engine, everything appears black, making it unclear which values were modified.)

《2》

It allowed using Ctrl + Z to consecutively undo changes and revert to the original values.

(Cheat Engine doesn't seem to have this feature, making it challenging to undo changes. Restarting the game becomes the only option, causing the memory locations to change again.)



Is Cheat Engine capable of achieving the above-mentioned functionalities (1 and 2)? Or are there features that I am unaware of?

Do others face similar challenges, or is there a workaround for these issues?

[ParkourPenguin]

Edit -> Settings -> Enable write logging by default

Memory Viewer -> View -> User write history

1) That doesn't make sense for writable memory. There's no good way to differentiate user writes from game writes- e.g. user writes value, game writes same value. This does happen in the disassembler if write logging is enabled (code is usually non-writable).

2) I don't think the hex view (bottom half of memory viewer) has that shortcut, but the "User write history" does.