Cheat Engine

[BirchTree]

I'm pretty much a noob at this, but I'm trying to call a function on a game using the Auto Assembler.

In the memory viewer, I can see that the function is called like this:

[Famine]

Your goal is to call a function within the game's code by replicating the assembly instructions. However, there are a few issues with your script that could be preventing it from working correctly.

Here are some things to check and correct:

Memory Addresses: Verify that the addresses you are using in your script (Game.exe+42A210, 01A578F0, 000102CC, etc.) are still valid. Game updates or changes in memory allocation can lead to these addresses becoming outdated.

Register Values: Ensure that the values you push onto the stack (push 0000000F, push 00008000, etc.) match the values the game expects at those points in the function. If you've copied the assembly code correctly, this should be fine.

Calling Convention: Confirm that the function Game.exe+42A210 uses the same calling convention as your script. The calling convention determines how function parameters are passed and how the stack is cleaned up after the call. If it's not a standard calling convention, you may need to adapt your script.

Code Flow: Check if there are any conditional branches or other code that could prevent the function from being called. The original assembly code might be part of a larger context that you're not replicating in your script.

Memory Permissions: Make sure that the memory areas you're trying to modify or execute code in have the necessary read, write, and execute permissions. Some parts of the game's memory may be protected, and you might need to use additional techniques to modify them.

Debugger State: Ensure that the game is running and the debugger in Cheat Engine is attached to the game process. It's important to have the debugger running for breakpoints to work.

Thread Handling: Your script creates a new thread to execute the code. Make sure this is the intended behavior in the game. Some games may not support or allow external threads to interact with their code.

Error Handling: Check for any error messages or issues in the Cheat Engine log. It might provide insights into what's going wrong.

Debugging: You can try single-stepping through your script in Cheat Engine's debugger to see if the code execution proceeds as expected and identify any issues.

Game Updates: Keep in mind that game updates or anti-cheat measures can break your cheats. You may need to update your script to match the latest version of the game. If you've checked all these points and the script still doesn't work, you may need to delve deeper into reverse engineering and debugging to understand the game's code better.

[ParkourPenguin]

Are you using the VEH debugger? The thread probably finishes executing the code before the VEH debugger notices the thread exists. The windows debugger doesn't have this problem.

Do you know what calling convention the function uses? e.g. stdcall, cdecl...
`add ecx,04` is weird to have just before the call. ecx is typically a volatile register- there's no point to modify it before a call unless it's a parameter. Could be thiscall or fastcall.

I'd look at the function itself and see what it uses. Maybe check for globals too. You can't get the full story by just looking at a call to the function.

[BirchTree]

[ParkourPenguin]

[BirchTree]

[ParkourPenguin]

Might need to wait longer
https://forum.cheatengine.org/viewtopic.php?p=5694129#5694129