Install Valheim dedicated server mods with BepInEx

Confirm hosting requirements

Ask whether the plan permits BepInEx, access to the server installation and the required startup command. Access limited to save files is insufficient. Record the operating system and exact Valheim version.

For each mod, list dependencies and whether it belongs on clients, the server or both. Exclude client-required mods from a console-player setup. A hosting plan advertising crossplay does not remove this limitation.

Install the loader on a test copy

Stop the server and archive the world, configuration and version list. Download BepInExPack Valheim from its maintainers' page. Extract it into a temporary directory first, then place the pack contents at the server installation root following their instructions.

On Linux, the pack supplies start_server_bepinex.sh. It must be executable and configured with your server's world parameters. If your panel enforces its own startup command, confirm the supported method with the provider instead of overwriting arbitrary files.

Introduce mods in small groups

Start with the loader alone and inspect its logs. Add plugins and dependencies to BepInEx/plugins. Configuration files are generally generated under BepInEx/config after loading.

Install a small coherent group, restart and connect with a client configured for the same requirements. Maintain a list of names, versions and dependencies so players can reproduce the expected setup.

Update with a recovery path

Before updating, archive the world, plugins and configuration together. If loading fails, compare logs and reproduce the issue on the test copy. Removing content mods from the main world can affect their items and structures.

Recovery requires a compatible combination of game, loader, mods and save. Automatically updating only the server can interrupt play until the remaining components catch up.

Frequently asked questions