Cheat Engine

[MeblIkea]

Hello, I tried to use Cheat Engine on a Godot game on ItchIo on Firefox, and I cannot find the values.
I done everything good (attaching Cheat Engine on good Firefox process, then I tried with Google Chrome) but still nothing.

Anyone know what I done wrong, or what should I do for gettin value of Godot games please?
Thanks!

[Kvist]

I assume that's gonna be tough. For Godot to work on the web, it is compiled to WebAssembly.
A component of the browser's JS engine (SpiderMonkey for FF, V8 for Chrome) then runs the WebAssembly bytecode, which will eventually be compiled into machine code.

A big obstacle in all of this will be the JS engine, as these do loads of de-/optimization, garbage collection, and code relocation.
This leads to memory changing all of the time and makes scanning for values quite challenging.
I for my part, can't even find integer values I set myself inside the JS console of Chrome, but then again,
I never tried to hack any games in the browser, so I don't really know if there's a special trick to them.

The only lead I can give you is to have a look at the sources. Both the JS source and the WebAssembly can be accessed from the browsers' developer consoles, and both FF and Chrome will decompile the bytecode into text format.
This will allow you to look into the whole game code, break and step through it with the browser's debugger and even change memory in both JS and WebAssembly while on a breakpoint, but you won't be able to get any hard and fast addresses for CE this way either.

On the other hand, I don't know half as much about this stuff as it may seem and there are some crazy cracks out there, so if anybody else knows how to do this kind of stuff with CE, I'd love to know.

[MeblIkea]

[quote="Kvist"]I assume that's gonna be tough. For Godot to work on the web, it is compiled to WebAssembly.
A component of the browser's JS engine (SpiderMonkey for FF, V8 for Chrome) then runs the WebAssembly bytecode, which will eventually be compiled into machine code.

A big obstacle in all of this will be the JS engine, as these do loads of de-/optimization, garbage collection, and code relocation.
This leads to memory changing all of the time and makes scanning for values quite challenging.
I for my part, can't even find integer values I set myself inside the JS console of Chrome, but then again,
I never tried to hack any games in the browser, so I don't really know if there's a special trick to them.

The only lead I can give you is to have a look at the sources. Both the JS source and the WebAssembly can be accessed from the browsers' developer consoles, and both FF and Chrome will decompile the bytecode into text format.
This will allow you to look into the whole game code, break and step through it with the browser's debugger and even change memory in both JS and WebAssembly while on a breakpoint, but you won't be able to get any hard and fast addresses for CE this way either.

On the other hand, I don't know half as much about this stuff as it may seem and there are some crazy cracks out there, so if anybody else knows how to do this kind of stuff with CE, I'd love to know.[/quote]
Hi, thanks for your answer.
I'll try to continue my stuff tomorrow, and try to get some values.
If I find a way to get some good results, I'll try to send every steps here.

[panraven]

A minor info, like the old flash, wasm's bytecode instruction encode integer constant,
"All integer constants are encoded using a space-efficient, variable-length LEB128 encoding"