Cheat Engine

[Kwhali]

I'm fairly new to CE, been going through tutorials on forums/youtube past few days. My choice in game doesn't seem to be the best to start learning CE with as most values I try to search for don't seem to be represented the same way. Some do though like timers so I'm trying to work with those.

I learnt about AoB scanning recently and while finding a matching byte array wasn't as small as the examples online I came across, I have found a matching pattern that works all the time. I can set this value on the address manually and toggle activation to keep the value freezed which is great. I'd like to be able to have an AA script do it though, however it's always causing the game to crash..

I've noticed that even though I've got an address and set/frozen the value, once the game is unpaused the GUI display and the value listed in CE that I set are jittering, it's a float value, the address is correct as the items effect duration never ends, so this hasn't bothered me. But perhaps it indicates why the AA script is breaking? The AoB will find the address no matter what the current value is, so the jitter isn't an issue for that. Nothing any the memory region of the AoB is changing apart from the bytes representing the jittering value and the next 2 bytes to the right of the values.

Here is my AA with AoB:

[SteveAndrew]

Okay your problem is you are trying to "hook data"... lol

See when you're manually editing the value at address: 0x518708c0 aka "pauseECM" in your script.

pauseECM after finding the aob, is pointing to 0x518708c0 or whatever the address happens to be for that run of the game.

Instead of modifying it to a float value of 15.0 you are instead writing a JMP xxxxxxxx(5 bytes: 0xE9 XX XX XX XX) + nop (1 byte: 0x90)

and you're storing float value 15 at newmem which isn't doing anything for you... Because you have to hook code, data is not code and can't be hooked...

I would recommend adding the address: 0x518708c0 to your CT and doing a right click + "find what accesses" and then doing whatever it is in the game that changes the value, and see what comes up... You can hook that code to change the value...

However until then I have a solution for you since that aob seems to be working good for you, this can work your way.

However you said you have to freeze the value right? So just setting it once isn't going to do much right? Don't worry about the fidgeting the value looks like in CE while freezing it... That's only because you are constantly modifiying it, and the game is still able to modify it also... It's kind of like a tug of war, where the game is like no the value is supposed to be like this, then CE is like no but I'm changing the value to (float)15.0, etc... etc... and that goes on and on, back and forth. With CE and the game both fighting to "have it their way" with the value they each want it to be.

That is the benefit of finding the game's code which is changing the value, and then you can nullify it's ability to change it, and instead whenever it tries to change it, you insert your own value like 15.0 (float)

So here would be fixing your script, but it still only changes it once, so you'd have to keep enabling / disabling it for it to stay in effect:

[Kwhali]