GameGrid
Valheim Mods and BepInEx Guide - visual guide

Valheim Mods and BepInEx Guide

How to install BepInEx and mods on your Valheim dedicated server. Server-side vs client-side mods, and crossplay compatibility warnings.

BepInEx Overview

BepInEx is the modding framework used by Valheim. It is a plugin loader that injects .NET assemblies into the game at runtime. Almost every Valheim mod needs it.

You do not have to install it. GameGrid installs BepInEx on every Valheim server start, on new and existing servers alike, along with the GameGrid Bridge plugin that the Game Tools page and the economy talk to. If the download fails the server still starts - it simply runs without platform integration until the next successful attempt.

BepInEx is installed into the server root: doorstop_config.ini and winhttp.dll sit beside valheim_server.exe, and those are what actually inject the loader. Plugins live in BepInEx/plugins and their settings in BepInEx/config. A running server with BepInEx active prints its version banner to stdout at startup, so the Console tab is where you confirm it took effect.

Game updates can break BepInEx and its plugins. After a Valheim update, check for updated mod versions before restarting a modded server.

Server-Side vs Client-Side Mods

Server-side mods: run only on the server. They modify server behavior (crafting recipes, spawn rates, world generation) without requiring players to install anything. Examples: Valheim Plus (server config), Server Devcommands.

Client-side mods: run on each player's own game client. They modify the client experience (UI, graphics, quality of life). Each player must install them individually. Examples: CraftyCarts, Better_UI.

Shared mods: some mods need to be on both the server and every client. They synchronize configuration or perform version checks. Examples: Epic Loot, ValheimVR.

If a shared mod is on the server but not on a client, the client will be disconnected or experience desync. Always tell your players which mods they need to install.

Installing BepInEx on Your Server

Normally there is nothing to do: the loader goes in by itself on every start.

If you want to check or reinstall it, open the Mods tab for your Valheim server. A mod-loader panel sits above the Installed and Browse Marketplace tabs; it names the loader from your server's own blueprint and offers Install and Uninstall.

That panel distinguishes "not installed" from "we could not ask the host". If it cannot reach the host it says so rather than telling you to reinstall a loader that is working.

Uninstalling has an option that also purges BepInEx/plugins and BepInEx/config - every mod you installed and every setting you tuned. It is off unless you ask for it. Uninstalling also removes the GameGrid Bridge, which takes the Game Tools page and the economy with it until the next start puts it back.

Whatever you change, restart the server: plugins are only loaded when the game process starts.

Installing Mods

From the GameGrid Mods tab:

1. Switch to Browse Marketplace and search for a mod. Valheim's marketplaces on GameGrid are Nexus Mods and Thunderstore. Steam Workshop is not offered for Valheim.

2. Click through to the file list for the mod and pick the file you want. Many mods publish several (core, resources, optional patches) and they install separately.

3. The host agent downloads it and places the files under BepInEx/plugins.

4. Restart the server for the mod to load.

5. Check the Console tab or BepInEx/LogOutput.log for errors. A missing dependency error (e.g. "Plugin X requires Y v1.2.3") means you need to install the dependency first. BepInEx loads plugins alphabetically and resolves declared hard dependencies itself, so load order only matters where a mod declares one.

6. If a mod has a configuration file it appears in BepInEx/config/ after the first run. Edit it from the File Manager and restart.

For anything neither Nexus Mods nor Thunderstore carries, upload the plugin into BepInEx/plugins yourself with the File Manager or over FTP, then restart.

Install mods one at a time, restarting after each, so you can tell which one broke something. Always back up your world before installing or updating mods.

Crossplay and Mods

Game-changing mods (Epic Loot, Valheim Plus gameplay changes, any mod that alters items, stats, or mechanics) can cause desync and crashes for Xbox and Game Pass players. Those clients cannot install BepInEx, so they cannot run the matching client-side components.

If your group includes them, run a vanilla (unmodded) server for maximum compatibility.

Server-side-only mods (mods that do not require client installation) are generally safe for crossplay, but test with an Xbox player before committing. The GameGrid Bridge and MaxPlayerCount are both in that category - they are server-side only and change nothing for a connected client.

Game Pass players cannot disable crossplay, so they are always on the PlayFab backend. They can only join crossplay-enabled servers and are affected by the same mod restrictions as console players.

Popular Mods

Server Devcommands: enables cheat commands (god, fly, spawn items) for admins on dedicated servers. Must be on the admin list to use. See the Admin Commands guide.

Better Networking: raises Valheim's outgoing data-rate cap, reducing desync for large groups. It has to be installed on every CLIENT as well as the server, so it locks out Xbox and Game Pass players - do not use it on a crossplay server.

Valheim Plus: a large gameplay overhaul mod. Configurable crafting, building, stamina, and food changes. Server-side config, but some features require the client mod.

Epic Loot: adds RPG-style loot drops with item rarities and enchantments. Requires installation on both server and all clients.

Plant Easily: simplifies farming. Server-side only.

Configuration manager: adds an in-game configuration UI for all BepInEx mods. Client-side only.

Equipment and Quick Slots: adds separate slots for backpack, quiver, and quick-swap gear. Requires client installation.

Troubleshooting Mod Issues

Server crashes on startup after installing a mod: the mod likely has a missing dependency or is incompatible with the current Valheim version. Remove the mod from BepInEx/plugins/ via the File Manager and restart.

BepInEx not loading: check BepInEx/LogOutput.log, which is downloadable alongside the main log. If no log is generated, BepInEx itself failed to load - check that the BepInEx folder, doorstop_config.ini and winhttp.dll are all at the same level as valheim_server.exe. Restarting the server reinstalls the loader if it is missing.

Game Tools stopped working after a mod change: the GameGrid Bridge lives in BepInEx/plugins too, so a purge uninstall or a hand-cleared plugins folder removes it. It is reinstalled on the next server start.

Players disconnected after mod install: a shared mod is on the server but not on the client. Either install the mod on all clients, or remove it from the server.

Mod config not applying: edit the file in BepInEx/config/ and restart. Config files are only generated after the mod has loaded at least once.