Cheat Engine

[moccor]

So I am curious if this is even possible to do at even a slightly reasonable time but I doubt it. Basically in some videogames, they don't allow quicksaving on higher difficulties.

I feel like that would require tons of scans to even narrow it down to a reasonable amount of addresses.

However what I am thinking is, I guess a easier method would be to find the area of memory where the settings are kept for the menu (if possible) and search what changes in that area when comparing a normal difficulty to a hard. Its possible somewhere in that area tells the game to enable/disable quicksaving.

But also, if there is a keybind for autosaving, can that be used to my advantage in this scenario? Maybe its some kind of data hidden in the save file that would simply require comparing two brand new saves with a hex editor.

Has anyone done something like this before or attempted it and decided it just isn't worth it or is not possible?

[OldCheatEngineUser]

you can use any of memory profiling tools (ultimal code filter etc), or you do memory scans.

you can use memory profiling tools when you:
- save your game
- change difficulty

you can use unknown initial scan as well, but use it this way:
- keep changing difficulty
- scan for changed/unchanged
repeat, once found:
- see what writes/reads that address
- go debugging and jump over calls
if the call you jumped over did anything to quick save button:
- change difficulty to easy/normal
- break and trace that subroutine
repeat two times, 1st on easy 2nd on hard

you can figure the rest, or any missing stuff.
good luck.

[moccor]