MonoJunkie is a tool to inject .NET assemblies into Mono processes (though designed for use with Unity games). Any Mono process can be targeted, regardless of version. This project was written in an afternoon (to replace mono-assembly-injector for my personal use, which has some issues), so there are bound to bugs. I do plan to keep improving it, though!
MonoJunkie uses Blackbone. We embed it directly due to some quirks with Blackbone's project files.
Finally (if it wasn't obvious), MonoJunkie is for Windows only. I may eventually port it to Linux, but there are better ways to do this on Linux than using this tool.
DO NOT use MonoJunkie with online games. Don't blame me if you get banned!
- Follow the caveats to ensure everything will work correctly in your assembly.
- Start the process. Wait until the correct injection time (again, see caveats).
- Inject your assembly via the command line. For instance, for our example assembly:
MonoJunkie.exe -dll "ExampleAssembly.dll" -namespace ExampleAssembly -class Example -method OnLoad -exe targetexe.exe -mdll mono.dll
-mdll is optional, and allows you to specify the filename for the Mono DLL loaded in the target process.
- MonoJunkie must be the same architecture as the target process. If the process is 64-bit, we must also be 64-bit. This is due to some issue with Blackbone crossing the WOW64 barrier.
- The Assembly you are injecting must match the architecture of the target process (or Any CPU).
- The Assembly you are injecting must be using the same version of .NET the target process is. Failure to do so may lead to problems. For example, all Unity games you should use .NET Framework 3.5, and compile against the assemblies shipped with the game (including System.dll, mscorlib.dll!) Due to legal reasons, my example assembly does not do this because I would have to ship a game's DLLs with it!
- The Method MonoJunkie is calling must be static and publicly visible. MonoJunkie does not instantiate the class the method is a member of. See the example.
- The correct time to inject depends on what you are injecting into. Injecting too early may cause issues and crashes. In unity games; for instance, you would usually want to wait until the Main menu has completely loaded before injecting.
- Generalize all calls in MonoInternals using a template, as it is messy boilerplate.
- Use mono_assembly_loaded to check if the assembly is already loaded to avoid potential crashes in the target process.
- Add unloading support using mono_assembly_close, mono_image_close. Once this and 2 are implemented, we can reload Assemblies.
- Automatic dependency loading.
- Add more command line options:
- Allow PIDs
- Allow targeting a specific thread to inject with.
MIT - See LICENSE