BepisLoader
A mod loader which allows using BepInEx with Resonite
About this mod Author’s original text
BepisLoader
A mod loader which allows using BepInEx with Resonite.
BepisLoader is a.NET (Core) only mod loader, currently targeting.NET 10. It is built on a fork of BepInEx with all Unity aspects (Unity Mono, IL2CPP, UnityDoorstop, etc.) removed. It cannot load Unity plugins and does not support Unity games.
Installation
For the recommended mod-manager setup, see the official installation guide.
Manual
- Download the latest release ZIP file (e.g., ResoniteModding-BepisLoader-1.6.0.zip).
- Extract the contents of the BepInExPack folder from the ZIP into your Resonite installation directory:
- Windows Default: C:\Program Files (x86)\Steam\steamapps\common\Resonite\
- Linux Default: ~/.steam/steam/steamapps/common/Resonite/
- Linux Users Only: The included LinuxBootstrap.sh file needs to be used instead of the default one:
- The package includes a modified LinuxBootstrap.sh that launches BepisLoader.dll instead of Renderite.Host.dll
- Important: Resonite updates could replace this file, breaking the mod loader. If this happens, you'll need to manually replace LinuxBootstrap.sh with the one from the BepisLoader package.
- Some mod managers - including Gale - will copy the script from their managed profile folder to the Resonite install directory on every game launch. In which case, you do not need to replace it manually.
- Enable the modded entry point by replacing enable=false with enable=true in the file hookfxr.ini
- Alternatively, add --hookfxr-enable to your launch arguments.
- Start the game normally.
- If you want to verify that the mod loader is working, check the BepInEx\LogOutput.log file after launching the game.
Disabling temporarily
- Set enable=false in the file hookfxr.ini
- Alternatively, add --hookfxr-disable to your launch arguments.
- If you had added --hookfxr-enable to your launch arguments before, you must remove it.
Uninstallation
- Delete the following files from your Resonite installation directory:
- Windows Entry Points:
- hostfxr.dll (our Windows entry point)
- hostfxr.pdb
- Common Files:
- hookfxr.ini
- All BepisLoader* files
- Delete the BepInEx folder.
Package Contents
The BepisLoader package contains:
- Windows Entry Point: hostfxr.dll and hookfxr.ini for hooking into the.NET runtime
- Linux Entry Point: Modified LinuxBootstrap.sh that launches BepisLoader if hookfxr is enabled (in hookfxr.ini or with launch options)
- BepisLoader: Core loader files (BepisLoader.dll, etc.)
- BepInEx: The BepInEx framework and all required dependencies
Building
Requires the.NET 10 SDK.
On Windows:./build.ps1 --target Publish -v d --build-type BleedingEdge
On Linux:./build.sh --target Publish -v d --build-type BleedingEdge
Or call the build project directly with dotnet (works on any OS):
dotnet run --project build/Build.csproj -- --target Publish -v d --build-type BleedingEdge
Build output (dist zips and the package) lands in bin/dist.
Targets (--target)
| Target | What it does |
|---|---|
| Default | Compiles the solution (runs Clean → RestoreTools → Compile). This is what runs if --target is omitted. |
| Clean | Wipes the bin output directory. |
| RestoreTools | Restores dotnet tools. |
| Compile | Builds the solution. |
| DownloadDependencies | Downloads the external hookfxr dependency into the dep cache. |
| MakeDist | Assembles the distributable folders under bin/dist (BepInEx pack layout, BepInExPack). |
| BuildThunderstorePackage | Runs tcli build to produce the.zip under bin/dist-package. |
| FixThunderstoreLinuxPermissions | Fixes executable permissions inside the package (Linux/macOS). |
| PushNuGet | Pushes *.nupkg to --nuget-source. Skipped unless --nuget-api-key is set and --build-type is not Development. |
| Publish | Full pipeline: MakeDist + PushNuGet + FixThunderstoreLinuxPermissions, then packs the final BepInEx-*.zip files. |
Arguments
| Argument | Default | What it does |
Install & use Install: follow the bundled instructions
- Unzip the archive from playbuff and read the bundled readme / instructions first.
- Most mods rely on the game's mod loader — the usual route is a community mod manager (such as r2modman): pick this game, install, and it handles the loader and dependencies.
- For a manual install, put the mod files into the matching Mod / plugins folder inside the game directory.
- Launch the game to confirm it loaded; mods with listed dependencies need those installed as well.
Install locations vary a lot between mods — the bundled readme is the most reliable guide.
Install these first, or the mod will not work: