With BepInEx, you can expand Valheim servers with mods if server files, client mods, and versions match cleanly. The key is not just copying a DLL, but a controlled process: install the framework, start the server once, add mods deliberately, align clients, and narrow down errors through logs or step-by-step disabling.
What BepInEx Does in Valheim
BepInEx is a mod framework for Unity games. For Valheim, BepInExPack Valheim is often used and is provided on Thunderstore: documentation at thunderstore.io. This project page is the primary source for the specifically named Valheim BepInEx package.
BepInEx provides the folders in which Valheim mods are loaded and configured. Many mods consist of one or more DLL files that must be placed in BepInEx/plugins/. After the first server start, additional configuration files are usually created in BepInEx/config/. Only change these files after the server has been started at least once with the framework installed.
If you also want to plan server basics, configuration, and boss progression cleanly alongside mods, the internal guide Rent a Valheim Server: Mods, Configuration & Boss Order 2026 is a good addition. For other Unity or mod-framework setups, the comparison with Install V Rising Mods with BepInEx Server Mods is also helpful.
Requirements
Before you start, you need access to the Valheim server directory, the ability to restart the server, and a clear mod list. With paid multi-game hosting like game-serverhosting, it is especially important that you apply changes traceably: first backup, then framework, then individual mods, then testing. This keeps technical control, supportability, and transparent operational workflows intact.
Also define which mods run purely server-side and which each player must install locally. Many Valheim mods require matching components on server and client; the labeling on the respective mod page is decisive. Therefore, check the relevant Thunderstore description for every mod before including it in a shared modpack.
Install BepInEx on the Server
- Download BepInEx from Thunderstore.
- Extract the contents into the Valheim server directory.
- Restart the server. BepInEx automatically creates the config folders.
The target structure should then look like this:
/valheim/
├── BepInEx/
│ ├── config/ # Mod configurations
│ ├── plugins/ # Place mods here
│ └── patchers/
├── valheim_server.x86_64
└── start_server.sh
The level is important: the BepInEx/ folder belongs directly in the Valheim server directory, not inside an additional subfolder from the ZIP archive. If no config or plugins structure appears after the restart, this is often exactly where the mistake is.
Install Mods
- Download mods from Thunderstore.
- Extract the DLL file into the
BepInEx/plugins/folder. - Restart the server.
Do not blindly install new mods in large packages. A controlled approach is more sensible: add one mod, start the server, check the log, test the connection, and only then install the next mod. With several players, you should document the mod list with version numbers so everyone uses the same basis.
If a mod includes additional files or its own folders, follow the respective mod instructions. Not every mod consists of just a single DLL. Do not arbitrarily move configuration files between plugins and config; BepInEx and the mod itself expect specific paths.
Align Client Mods
Most Valheim mods must be installed both on the server and on the client. Use the Thunderstore Mod Manager for easy client installation.
Alternatively, you can use r2modman:
- Install r2modman.
- Select "Valheim" as the game.
- Browse and install mods with one click.
- Export your modpack as a code → share it with friends.
The practical advantage of a mod manager lies in alignment: all players can use the same profile instead of manually collecting DLLs. Still, you should remain careful after updates. An updated client mod can be incompatible with an older server mod. Therefore, record when you changed the modpack and which versions are active.
Recommended Mods
The following table shows common examples; check every mod for current status and dependencies before installation. It is not a performance promise and does not replace checking the respective mod page for compatibility, current status, and required dependencies.
| Mod | Description | Client required? |
|---|---|---|
| ValheimPlus | Extensive adjustments | Yes |
| Better UI | Improved user interface | Yes |
| Plant Everything | Plant anywhere | Yes |
| Epic Loot | Rare items with properties | Yes |
| Better Wards | Improved ward stones | Yes |
Check the Result
After installation, the server should start without crashing. First check whether BepInEx is loaded in the log and whether error messages appear about missing dependencies, wrong versions, or DLLs that were not found. Then test with a client that uses the same mod selection.
In the game, you should deliberately test one function of each installed mod: UI change visible, new configuration option effective, new item present, or expected behavior active. If everything works, save the working mod list and the most important config files. This lets you trace later changes or roll back if problems occur.
Troubleshooting
Mod Does Not Work
First check the BepInEx version, mod version, and mod compatibility. Also check whether the DLL is really in BepInEx/plugins/ and not accidentally in a double-extracted subfolder. Read the mod page on Thunderstore, because many mods require additional dependencies.
Server Crashes
Remove mods one by one to find the cause. Start with the most recently installed or most recently updated mod. Restart the server after every change and check the log. If the server starts without mods but crashes with a specific mod, the cause is usually a dependency, version, or configuration.
Desync or Connection Problems
Make sure all players have the same mods in matching versions. Especially with client-required mods, changing only the server is not enough. An exported r2modman or Thunderstore profile reduces differences and makes support cases easier to trace.
Config Is Not Created
Start the server once with BepInEx and the respective mod installed. Many mods only write their config after the first successful load. If no file appears afterwards, the mod may not have been loaded, may be in the wrong folder, or may be incompatible with the current environment.
Checks, Limits, and a Safe Rollback
The guide “Install Valheim Mods with BepInEx – Step by Step” applies to the server type described in the article and the version status visible at the time of review. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values unchecked to another game, loader, or server version.
Before changing the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.
| Checkpoint | Expected Result | Abort and Rollback |
|---|---|---|
| Server startup | The server reaches the operational state without a new error message. | If startup errors occur, revert the change and restore the latest backup. |
| Connection test | A test account can connect via the address shown in the panel. | If version or connection errors occur, compare version, port, and permissions again. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore backed-up files. |
A successful single test is not a guarantee of performance or availability. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can trace later deviations.
FAQ
Does BepInEx Have to Be Installed on Server and Client?
For many Valheim mods, yes. If a mod is client-required, the server and players need the same or a compatible version. Always check this on the respective mod page.
Can I Install Valheim Mods Only via Thunderstore?
No, you can also place DLLs manually in BepInEx/plugins/. However, Thunderstore Mod Manager and r2modman make version alignment and distribution to fellow players easier.
Why Does My Server No Longer Start After a Mod?
Common causes are wrong BepInEx versions, missing dependencies, incompatible mod versions, or files in the wrong folder. Remove mods step by step and check the log after each restart.
Where Are the Mod Configurations Located?
Many BepInEx mods create their configuration in BepInEx/config/. The files often appear only after the first successful server start with the mod installed.
Should I Install All Mods at the Same Time?
Better not. Install mods one after another or in small groups so you can clearly assign errors. This saves time if the server crashes or clients cannot connect.