Cheat Engine

SuperAndromeda · Newbie cheater Reputation: 0 Joined: 30 Jul 2022 Posts: 12

This never happened to me before, but out of the blue, all the pointers I was working with (and I checked their reliability many times before) stopped working at the same time. The curious thing is that they were all from the game's own process, and the other few related to Steam I have are still working fine.

How could this happen and how can I avoid it?

Alt · How do I cheat? Reputation: 2 Joined: 19 Jan 2017 Posts: 4

Maybe an update, or you're dealing with a game that's got a JIT compiler like Unity. Seeing as you had consistency prior, though, I'd imagine it was probably an update. If it was an update, nothing is guaranteed to work, but AOB scanning is generally more robust than pointer chains.

SuperAndromeda · Newbie cheater Reputation: 0 Joined: 30 Jul 2022 Posts: 12

Alt · How do I cheat? Reputation: 2 Joined: 19 Jan 2017 Posts: 4

AOB is somewhat update resistant, but not fully. Pointer chains are not update resistant at all. An AOB will break if the corresponding code changes, a pointer chain will almost always break regardless of code changes.
Getting a pointer from an AOB is trivial in CE. You find the instructions that read/write to your address, inject using auto assembler, use the aob template, declare a variable that will store your desired address, move the address from the register that stores it into your variable, then use lua to get that address from the variable and assign it to your table. Doing this outside of CE means doing everything CE does manually, which will likely be a hell of a headache the first few times you do it. Good news though is that, should your AOB break, it's usually easier to find the new AOB than it is to derive a new pointer chain.

SuperAndromeda · Newbie cheater Reputation: 0 Joined: 30 Jul 2022 Posts: 12

lucid · Posted: Wed Mar 20, 2024 10:34 am Post subject:

SuperAndromeda · Newbie cheater Reputation: 0 Joined: 30 Jul 2022 Posts: 12

lucid · Posted: Thu Mar 21, 2024 10:26 am Post subject:

Did some searching and I found that Rivals was written in GameMaker. GameMaker by default uses a virtual machine JIT compiler, and pretty much any multi-platform game using GameMaker is going to use that default. As such, you're in the same situation as with Unity games. The pointers are going to change on you, and the only way to prevent this is to use AOB scanning to identify your pointers, which will only work after the relevant function has been called and the instructions have been written to memory. This is a headache you're dealing with that I'm not familiar enough with to give you decent guidance.