A missing mod can come from three different stages: the loader never starts, the plugin fails to load, or the plugin loads but its feature is inactive. Find the first failed stage before reinstalling another package. These checks use original loader and mod-author instructions reviewed October 15, 2026.
Start with evidence from this launch
Save and close the game before changing files. Keep an independent save backup and note your game build, loader build and plugin versions.
After the next launch, check the BepInEx console and the log in the installed game's BepInEx folder. Nivalis mod authors refer to BepInEx/LogOutput.log; the general loader guide also documents LogOutput.txt. Inspect the file actually created by your loader and its timestamp. An old log is not evidence of the launch you are diagnosing.
Swipe horizontally to see all columns.
| Evidence | Likely stage to investigate |
|---|---|
| No newly written BepInEx log or generated folders | Installation, launch route or loader initialization |
| Loader appears, but the plugin is missing | Plugin path, package contents and dependencies |
| Plugin appears with binding or unsupported-build errors | Game update, generated bindings or plugin compatibility |
| Plugin appears without a load error, but a feature is absent | Its own controls, configuration or inactive patch message |
No loader log: check the full package identity
The refreshed Nivalis authors specify BepInEx 6 Unity IL2CPP Windows x64, build 788. BepInEx 5, Unity Mono and a native Linux loader are different packages. Nivalis remains a Windows game when launched through Proton or Wine.
Open Steam > Manage > Browse local files. The loader archive belongs beside Nivalis Nights.exe, not in the save folder or an extra nested download directory. Keep its archive layout intact, then start the game once before adding plugins. IL2CPP initialization can take time while it generates the files it needs.
If you use a manager profile, launch through the route required by that manager. Installing a loader into one game folder and launching a second copy will not test the installed files.
Loader starts: check one complete plugin
Read the package author's folder path rather than putting every DLL at the same level. Two current examples are:
- Performance Fix:
BepInEx/plugins/NivalisPerformanceFix/NivalisPerformanceFix.dll. - Better Time:
BepInEx/plugins/NivalisSlowDays/NivalisSlowDays.dll.
A nested BepInEx/BepInEx/plugins directory is a different path. An individual DLL can also omit the metadata or companion files supplied by its full ZIP. Keep the complete package, remove duplicate older copies and test one plugin first.
If the log names a missing dependency, install the matching author-required package. The Thunderstore Hvizeu packages declare loader 755, while their documentation identifies 788 as tested. A dependency installer completing successfully does not prove that a different loader build passed gameplay checks.
It failed after a game update
A plugin compiled for an older build can fail even when the loader works. Read the exact unsupported game build, unsupported GameAssembly or binding error. Update the plugin to a release whose author supports your build; reinstalling the same old DLL cannot establish compatibility.
With LUZ, use Maintenance > After a game update > Diagnose game update. If generated BepInEx bindings are stale, close the game and use Refresh game bindings. The launcher backs up the old generated files and enables regeneration on the next normal game launch. This does not repair an incompatible plugin or bypass its checks.
For an unapplied setup, use the profile guide. A ZIP can be imported into LUZ while the installed game still has the previous profile. Required dependencies must be enabled in that selected profile before Apply.
Loaded plugin, missing feature
Check the current release's own controls. Better Time's clock setting is under Gameplay when used alone and Mods with Unofficial Patch; old fixed-speed DLL instructions do not describe that current interface.
Performance Fix requires a restart for its worker-thread setting. Its current README gives 27/27 as the 1.0.8 startup example, with a separate old-HUD exception. If an optimization disables itself, read the named patch and game version. Some old vendor-restock work is unnecessary after the official Update #4 fix.
Proton or Wine: check DLL loading separately
The official BepInEx Proton/Wine guide explains the winhttp override needed for the Windows loader. LUZ's Nivalis quick start gives the Steam launch option:
WINEDLLOVERRIDES="winhttp=n,b" %command%
Merge that with the launch options your existing setup needs. A Linux/macOS LUZ package does not establish that the game, loader and chosen plugins work through a compatibility layer. The author's native acceptance remains pending.
Return to a known setup and report the first error
If the game fails only after adding one plugin, close it and remove that package using its author-specific instructions. Performance Fix removal also requires Steam verification to restore its boot.config setting. Preserve the log before it is replaced.
A useful report contains the first relevant load error, exact versions, installed packages, game directory, launch route and the action that reproduces the failure. Keep the distinction between “loader starts” and “feature works” in your notes.
Source references
- Official BepInEx IL2CPP installation and Proton/Wine loading.
- Performance Fix original README.
- LUZ 0.4.9 quick start and README.
- Better Time author documentation.
Source instructions checked October 15, 2026; no modded gameplay acceptance was performed by this site.