Cheat Engine

Tomato10 · How do I cheat? Reputation: 0 Joined: 09 Nov 2012 Posts: 1

When I try to hack the score or time (in singleplayer), I can narrow down my list to around 262 or 54 addresses (respectively). I usually find the exact same green address every time, and I've found the pointer for it too. However, when I change the values for all these addresses, my changes don't stick. I've even tried marking the active box for ALL of the values, and and changing the freeze interval to 5 ms, but my changes don't stick. What I mean by this is that the game doesn't acknowledge that the time is 45:00 (even though it says so on the menu) and won't start injury time (basically random amount of extra time added at the end of each half). So essentially, 45:00 is the farthest I can hack it. Also, when I unfreeze the values for time, it just goes back to what the time would have been if I hadn't hacked it. (So for example, I hack the game at time 2:00 to make it 45:00, and I freeze it at 45:00 for 2 minutes while I play. Then I unfreeze it, and now the time is 4:00--assuming the game time progresses at the same rate as irl time).

Also a funny thing:

the base address (for the pointers) for both of these values is the same, only the offset is different (450 rather than 458).

Also, when I was first trying to find the pointers, and used the "find what writes to this" option, the number (count) on the left hand column would start counting up super fast. when i did the tutorial, the number would only go up every time I clicked the "change" button.

Sorry for this wall of text; hopefully you guys can help me out. Smile

Rawing · Posted: Thu Jan 02, 2014 5:22 am Post subject:

I'd guess you found the variable used for display purposes, not the REAL time variable. Try scanning for other data types or the time in milliseconds. If you're unlucky, there won't even be a time variable, just a variable with the time when the game started.

About the number of times the time variable is written to, well, it's obvious that the time changes all the time, right? Of course it's accessed very often. That's actually a good sign - if a variable isn't accessed very often, it most probably is NOT the time.