What problem does it solve? Debugging a BepInEx mod running inside the Resonite client is hard because .NET debugger attach is not set up and Renderite IPC behavior is undocumented. This Skill provides a print-debugging workflow for the resonite-io mod: tailing BepInEx logs, decompiling Resonite first-party DLLs, and launching or stopping Resonite inside the devcontainer. ## Core Features & Use Cases - Log Tailing: Follow mod output via just log, which tails gale/BepInEx/LogOutput.log across Resonite restarts and log rotations. - DLL Decompilation: Run just decompile to expand Resonite and Renderite Unity DLLs into a readable project under decompiled/ using ilspycmd, essential for understanding undocumented Renderite IPC. - Container Launch Control: Start the mod-loaded client with just resonite-launch and stop it with just resonite-stop, with staged SIGTERM/SIGKILL of both engine and renderer processes. - Use Case: When a TypeLoadException appears after adding a Protobuf dependency, use this Skill to check the BepInEx log, identify the Google.Protobuf 3.11.4 conflict bundled with Resonite, and consult the linked memory notes for the fix. ## Quick Start Ask the AI to start Resonite with the mod loaded and tail the BepInEx log to diagnose why the mod is not behaving as expected.
