Cheat Engine

[ikasarum]

So I have first found an address that is related to a stat that I want to change. (The Desired Address is 28A90A90)

Then I went on to Memory Viewer

And while pausing the game through Cheat Engine, I have tried to use Break and Trace with conditions set to RBX==0x28A90A90, that is the address of the desired stat.

Now I had gone back to the Memory Viewer to find the code that writes to RBX, which is RAX, which is being written by RDI.

So now I went back to the Cheat Table to manually add the address of RDI, that is 1084FEE0 and attempt to Break and Trace that to trace what writes to RDI. However, I become stuck when the code I manually added that writes to RDI does not match with the value for RBX. It keeps on changing/alternating, and so now I'm not sure what to do next.

[ParkourPenguin]

What exactly are you trying to do with break-and-trace?

If you want to know where rdi comes from, scroll up in the disassembler. You'll probably end up at a parameter to the function, at which point you should look at the caller. Repeat as necessary.

[ikasarum]

[ParkourPenguin]

RDI is just the source of data being copied from one memory location to another. There's no guarantee it must be the same the next time the code is run. Performing a break-and-trace there won't help. It's like trying to catch a criminal by putting a trap at the scene of the crime that was just committed- it's not particularly likely to work.
The only way what you're doing could work is if you could go backwards in time- it's impossible.

You have to know how to read assembly in order to learn where RDI comes from. Break-and-trace isn't going to be of much help. It'll help you easily move around the callstack, but that's pretty much it.

[ikasarum]

Oh okay, thanks, I suppose there's still a lot more learning to do.