How lavagang/melonloader works
Project Type & Purpose
• This is a native-plus-managed “mod loader” framework for Unity games (MelonLoader).
• It injects itself into Unity player processes (both Mono and IL2CPP), generates/interprets assemblies, applies patches via Harmony, and loads user plugins/mods.
A. Proxy DLL & Native Bootstrap
• version.dll (or renamed proxy) + plthook/Dobby libs
• Entrypoint: intercepts game’s DLL load, initializes environment
B. Runtime Handlers
• MonoHandler (for Mono games)
• Il2CppHandler + Il2CppAssemblyGenerator (for IL2CPP games)
C. Managed Core (C#)
• MelonLoader.Core – central API, plugin/mod discovery & loading
• SupportModules & CompatibilityLayers – shims for IPA, Demeo, MuseDash, etc.
• Harmony & patching logic
• Configuration (Loader.cfg) & Logging
D. Plugin/Mod Ecosystem
• “Plugins” folder → user assemblies implementing IPlugin / MelonMod interfaces
• “Mods” folder → IL2CPP mods or other content
E. External Services
• Cpp2IL Remote API (optional)
• Local assembly dump & deobfuscation packages under Dependencies/Il2CppAssemblyGenerator
1. Game EXE loads Proxy DLL → Native Bootstrap
2. Bootstrap (Native) chooses Mono vs IL2CPP handler
3. Handler loads core managed assemblies (MelonLoader.NativeHost → MelonLoader.Core)
4. Core reads config, sets up Logging → writes logs to GameDir/MelonLoader/Logs
5. If IL2CPP: assembly generator runs (offline or remote) → dumps Unity types → loads into AppDomain
6. Core initializes SupportModules & CompatibilityLayers
7. Core scans Plugins/Mods folder → resolves assemblies, applies Harmony patches
8. Patches hook Unity engine methods → user mods execute at runtime
Architectural Patterns & Design Principles
• Native-to-Managed bootstrap (C++/C# interop via Dobby & plthook)
• Strategy pattern for runtime handlers (Mono vs IL2CPP)
• Plugin architecture (IPlugin, MelonMod interfaces)
• Dependency Injection / Reflection for module discovery
• Separation of concerns: native hooking vs managed logic vs plugin loading