Tools and resources useful for developing and debugging BepInEx plugins.

You need to have at least BepInEx 5,x installed for most of the tools to work.

Turns exceptions into a more readable format. Resolves enumerators, lambdas and other complex structures.
Based on Ben.Demystifier.

How to use: This is a preloader patcher. Put the compiled DLL into BepInEx/patchers. Requires BepInEx 5 (or BepInEx 4 with MonoMod.RuntimeDetour).

This preloader patcher allows to capture and mirror Unity internal debug logs (i.e. the contents of output_log.txt).
Preloader patch provides a public event one can listen to which will receive all Unity logs, including internal debug logs that are only output to output_log.txt.

Unlike output log, which can be disabled in the game, this mirror will always capture said debug logs. If Unity already outputs output_log.txt, this plugin will simply create a copy of it in a more accessible place that %APPDATA%.

How to use: This is a preloader patcher. Put the compiled DLL into BepInEx/patchers.
By default, logs are output to unity_log.txt. This is configurable via MirrorInternalLogs.cfg configuration file that gets generated on the first run.

A simple profiler that can be used in any Unity player build as long as it can run BepInEx 5.x. It can generate a .csv file with profiling results from an arbitrary length of time.

How to use: To install simply extract the release archive into the game root directory (folder structure is important. MonoProfiler32/64.dll files need to be right next to the game .exe and other dlls need to be inside BepInEx subfolders). MonoProfiler32.dll and MonoProfiler64.dll can both be copied to the game directory and only the correct one will be loaded.

Check the config file or use ConfigurationManager to change the hotkey used to dump the collected profiler data (KeyCode.BackQuote by default). Dumps only include information that was captured since the last time a dump was triggered.

You can use LibreOffice Calc or Excel to view the dumped .csv results. Using Calc as example, open the .csv and import it with default options, then select columns A B and C, and click Data/AutoFilter. You can now click the arrows in 1st row to filter and sort the results.

Warning: The profiler always runs and will noticeably slow down the game. To turn the profiler off you have to close the game and rename MonoProfiler dll to something else like _MonoProfiler32.dll. You need the correct version of MonoProfiler.dll for your game (either 32 or 64 bit).

Loads and reloads BepInEx plugins from the BepInEx\scripts folder. User can reload all of these plugins by pressing the keyboard shortcut defined in the config. Shortcut is F6 by default.
Very useful for quickly developing plugins as you don't have to keep reopening the game to see your changes.

Remember to clean up after the old plugin version in case you need to. Things like harmony patches or loose GameObjects/MonoBehaviours remain after the plugin gets destroyed. Loose gameobjects and monobehaviours in this case are objects that are not attached to the parent scriptengine gameobject.

How to use: This is a plugin. Put the compiled DLL into BepInEx/plugins.

Log and report the time spent in the Start, Awake, Main, .ctor and .cctor methods of each plugin.
Also reports the total time spent in all plugins during these methods and the total time spent in chainloader so any performance improvements done through multithreading can be analyzed better.

How to use: This is a preloader patcher. Put the compiled DLL into BepInEx/patchers. Requires BepInEx 5 (or BepInEx 4 with MonoMod.RuntimeDetour).

You can debug already built Unity players even if you don't have its source project. https://github.com/risk-of-thunder/R2Wiki/wiki/Debugging-Your-Mods-With-dnSpy

In-game inspector, editor and interactive console for applications made with Unity3D game engine. It's designed for debugging and modding Unity games.
https://github.com/ManlyMarco/RuntimeUnityEditor#readme