Cheat Engine

[TastyToast]

The game I'm trying to hack is Pixel Puzzle Ultimate Jigsaw.


Attachment 1: In this game there are two "currencies" I'm trying to hack, "hints" and "gold pieces".
Whenever I've tried to fiind those values, I find 8 adresses which are all being written by the same two functions.


Attachment 2: The first thing I wanted to do here was to follow EBX, but for some reason it's showing EBX=00000000.
Then I tried to see what this function was accessing, and there were 40+ addresses so I couldn't get any info from that.


Attachment 3: Here I checked the FPU registers and there was one which had the same value as the address I was hacking but I just don't know how to proceed. Is there a way to know the addresses for these FPU registers?


I think I'm pretty much stuck or I'm missing something important, so if anyone has an idea I'd love to know about it/learn from it.

Also if anyone wants to give it a shot, it's a free to play, when you finish (or skip) the tutorial you can go to the kiosk and get 10 gold pieces which can be converted into 100 hint pieces if you start a puzzle.

Edit: I should point out that locking all these values (or changing them) doesn't seem to have any effect at all.

[ParkourPenguin]

Disconnect from the internet and try to play the game. If you can't or some features are limited, the values probably aren't stored on your computer, and you should give up.

If changing the values doesn't have any effect, changing the code accessing the values almost certainly won't work either.

ebx in the first instruction is a value being stored at an address. It has no correlation to the derivation of the address being written to. Click "show disassembler" and scroll up to find out where edi is coming from.

The x87 FPU stack automatically converts values loaded onto it into an 80-bit floating point format. Change the display type to "extended" to see what the values on the stack actually are. (make sure you're looking at the fpu stack and not sse xmm registers)
Since the registers were recorded after the instruction executed, the value on the top of the stack wasn't the value stored at edi. (fstp popped it off after storing it)

[TastyToast]