Cheat Engine

bismult · Cheater Reputation: 0 Joined: 09 Mar 2022 Posts: 27

I'm running into issues with setting multiple parameters for executeCodeEx and executeMethod. I need to set RDX and RDI to 0x4, but it's not working. Yes, I 100% have the correct address.

Eggs_ · How do I cheat? Reputation: 0 Joined: 19 Jun 2025 Posts: 7

i just tried it in windows, it works. I assume you are trying to execute it in Linux, maybe you should also set RSI the documentation doesn't state that the default parameter value is 0 if you don't set it.

Have you put a breakpoint at the function address to check if it gets triggered at all and just doesn't give the desired results.

alternatively you could always inject into a gameloop and use autoassembler code ..

bismult · Cheater Reputation: 0 Joined: 09 Mar 2022 Posts: 27

Eggs_ · How do I cheat? Reputation: 0 Joined: 19 Jun 2025 Posts: 7

ParkourPenguin · Posted: Fri Jun 20, 2025 12:10 pm Post subject:

executeCodeEx - the 4th and 5th parameters set rcx and rdx respectively. Naming a local variable EDX or EDI doesn't mean anything.

executeMethod - Only the 4th parameter to executeMethod is special and allows you to specify the register that the pointer to the instance is stored in. All further parameters are the same as executeCodeEx- i.e. the register can't be specified.

See documentation in celua.txt for more details. You should specify something for the timeout to prevent deadlock if something goes wrong. e.g. 10000 = 10 seconds; most calls should finish before then.

That calling convention is almost certainly wrong. Find a call to the function you want to call, and show us the code around there. Set a breakpoint, do something to trigger it, step over code until the function returns, and scroll up a bit to see the call. If that doesn't look quite right, there may have been a tail call involved somewhere. Try dissecting the code of the exe/dll (if the function is in an exe/dll) or the same memory region (if it was dynamically allocated). There should be a menu item under the "Tools" menu of the memory viewer. Go to the start of the function and you'll see a list of all the calls to that function.