Cheat Engine

[Dr.Disrespect]

I know how to read and write the memory of a game using C# or C++/CLI. However, for the more advanced stuff, I don't know how to do it with C# or C++/CLI.
For example, in the "Memory Viewer" in CE, I can select "Auto Assembly" under the "Tools" menu, then select "Create Table framework code", and select "Code Injection". This way, I can modify a piece of code of the game to achieve the result I want.

My question is, how to do that in C# or C++/CLI? How to direct the game process to use my code when a certain event is triggered, and goes back to the game process after the execution of my code?

Thanks a lot.

[ParkourPenguin]

https://www.youtube.com/watch?v=2CY_NBSwcWg

[Dr.Disrespect]

[ParkourPenguin]

1. C++ / C# Tutorial
   
2. Windows API Documentation
   
3. x86 Documentation

I honestly wouldn't recommend any specific tutorials on anything. The one I posted previously is if you're completely lost, new to programming, and/or don't have the time to learn anything. As long as you have a decent comprehension of the language you're using (C++/C#), knowledge of x86 architecture, and the ability to look at documentation (Windows API Index, Intel Software Developer Manuals), it shouldn't be hard to figure out how to make a hook: find the injection point, allocate memory, and write memory. The specifics beyond those 3 points depend on what you're doing. For example, if the injection point is located in a module, if you're doing this from within the process (i.e. dll injection) or externally, etc.

[Dr.Disrespect]

[ParkourPenguin]

What I'm trying to hint at is that not every situation is the same, and there isn't always going to be something that perfectly explains a specific situation. The authors of documentation expect readers to apply that information to their specific situation.

In your case, start by working on the three points I mentioned:

[Dr.Disrespect]

[atom0s]

If you are looking into DLL injection, look into the following API:

To obtain the target process information:
- CreateToolhelp32Snapshot
- Process32First / Process32Next
- Module32First / Module32Next

To manipulate the remote process:
- OpenProcess
- OpenThread
- CloseHandle

To manipulate tokens (needed in some cases to enable debug privileges):
- OpenProcessToken
- LookupPrivilegeValue
- AdjustTokenPrivileges

For injecting a DLL into a target process, there are a number of ways to do it. The typical method is via the WriteProcessMemory/CreateRemoteThread method. That would involve using:
- CreateProcess
- VirtualAllocEx
- WriteProcessMemory
- CreateRemoteThread
- WaitForSingleObject
- GetExitCodeThread

There are a lot of other methods to take though depending on the target and if there is detections to worry about. Manual mapping is the more common method of doing injections to avoid being detected. As well as other methods such as using a driver from the kernel level and such. There are a ton of injectors open source around the web that can assist you with learning those other techniques.

If you are looking to inject code caves and such, you will mainly need:
- OpenProcess
- VirtualAllocEx
- WriteProcessMemory

Just be sure to read up on x86 jumps and calls to understand how they are calculated to ensure that your caves jump to and from things properly and make calls correctly.

[Dr.Disrespect]