TIP: The solution only works with VS 2019.

For the record; there are a many libraries which are better than mine available for free on GitHub. I'm just creating this codebase for myself to get a better understanding of architectures.

This library changes a native (unmanaged) game application into a managed application by injecting your managed library and loading all the needed CLR dlls.

See the Samples folder where you can see how I do things, I'm using notepad++ 32-bit for all my samples currently. The library you are injecting needs an explicit architecture version, such as, if you're injecting into a 32 bit process then the DLL will have to be build with the x86 architecture.

You always want to extend your injection method from the GameSharp.External.Injection.InjectionBase class. You can add your own injection methods by overriding the Inject and Execute method.

Currently there are a lot of detection vectors which are still present and most likely you'll have to figure out how their anti-cheat is working to get the most out of this project. However, I do try to keep some of the anti-cheat in mind, for example:

• The code searches for a code cave inside the memory region of the to be called function before applying a hook or calling the original function. This is to bypass return address checks.
• When a debugger attaches we set the IsBeingDebugged flag in the PEB to 0.

• DLL injection of a managed DLL in an unmanaged application through the famous RemoteThread injection method.
• Randomizing the PE header.
• Attaching a managed debugger to the unmanaged remote process.
• Hiding the presence of the debugger from the PEB!IsBeingDebugged flag.
• Execution of the entry point of the injected DLL in the remote process.
• Execution of the MessageBoxW function with my own arguments in a safe way.
• Hooking the MessageBoxW function in a safe way.
• Calling NtQueryInformationProcess in 3 different ways, safe function call, pinvoke, through a payload.