ServerManager

ServerManager

Mod control, server-side characters, player logs and Discord tools for Valheim.

Works with dedicated servers and multiplayer worlds opened from the game. The local host’s character is managed too.

optional mods list is available on lobby.

2-way discord chat and rcon command on server through discord channel

Features

• Allow only approved mods, checked by exact DLL hashes (SHA-256).
• Save characters on the server and restore them when players return.
• Keep native .fch backups and restore characters with admin commands.
• Monitor cheat tools, cheat commands, player stats and forbidden items.
• Record player activity, inventories, chat and server events.
• Send Discord notifications, relay chat and run admin commands from Discord.
• Schedule server commands, including supported Upgrade World maintenance.
• Customize the main menu with a logo, quick connect and an optional-mod list.

No preloader patcher, separate bot program or extra RCON listener is needed.

Install and start

Use Valheim 1.0.20 on the server and all clients. Existing pre-1.0.20 Deep North character files and backups remain readable; do not rename or delete them for this update. New full saves use the current game format.

1. Install ServerManager.dll in BepInEx/plugins on the server and all clients.
2. Disable crossplay. Remove ServerCharacters and old standalone

OrbOfDiscord DLLs. Avoid other mods that manage the same character saves.

1. Start the dedicated server, or open a world with Start Server.

ServerManager creates its files under the Valheim save folder.

1. Copy your approved mod DLLs into required and optional.
2. Edit ServerManager.yml. Set up discord.yml only if you want Discord.
3. Check the server log for errors, then join with a new character or an approved

existing save.

By default, an existing local character with world progress cannot join unless the server already has its save. The player is asked to create a new character; their local save is not overwritten by this rejection.

New server characters keep the skin color, hair, beard, hair color and body model selected during character creation. Starting items and progression follow the server rules. Once a server save exists, its appearance is restored instead; later in-game appearance changes are included in full character saves.

Where files are stored

Server data is separate from mod-manager profiles.

On Windows:

%USERPROFILE%\AppData\LocalLow\IronGate\Valheim\ServerManager

If you use Valheim’s -savedir option, the folder is <savedir>/ServerManager. Dedicated servers and local hosts use the same rule.

ServerManager/
├── ServerManager.yml       Server rules and starting items
├── discord.yml             Webhooks, bot commands and chat
├── cron.yml                Scheduled commands
├── cron_last.yml           Saved scheduling progress — do not edit
├── Itemdata.yml            Item custom-data presets
├── required/               Required mod reference DLLs
├── optional/               Optional mod reference DLLs
├── characters/
│   ├── <Steam64>/          Character files and backups
│   └── HowToRestore.txt    Import and recovery instructions
├── logs/
│   ├── events-audit.log    Server, security and admin activity
│   ├── events-chat.log     Chat history
│   └── <Steam64>/          Individual player logs
└── cache/logos/            Downloaded client logos, when used

The editable YAML files reload automatically, except maxPlayers, which applies on the next server session. Invalid edits keep the last valid settings. Use spaces, not tabs, and keep key names exactly as shown. Existing files are not rewritten when defaults change.

Characters share this storage across worlds. For independent servers on one computer, use separate -savedir folders. Leave generated lock files alone; a lock file remaining after shutdown is normal.

Ordinary remote clients do not create the server settings or character store. Keep server settings, Discord credentials and character files out of modpacks.

Required and optional mods

Copy trusted DLLs into these folders on the server:

| Folder | What players need | | --- | --- | | required | Every listed mod, with an approved DLL hash. | | optional | The mod is optional, but its DLL hash must match if installed. | | Neither | Unlisted BepInEx plugins are rejected for non-admin players. |

These are reference copies. Putting a DLL here does not install the mod. Mods that must run on the server still belong in its BepInEx/plugins folder.

• ServerManager adds its own running DLL to the required policy automatically.
• Folder changes reload in the background. Update these copies when changing

your modpack; the updated policy applies to new connections.

• Multiple approved versions can share one folder. Do not put the same plugin

in both folders.

• Invalid updates keep the previous policy. While the first policy is still

loading, players may need to retry joining.

• Verified admins may use extra plugins or mismatched optional mods.

Required mods still apply to admins.

Only BepInEx plugins are checked. Standalone libraries such as Newtonsoft.Json.dll and YamlDotNet.dll are skipped even when copied into required or optional; skipped files are reported when the policy loads or reloads. Their presence, version and hash do not affect admission. A companion DLL that registers a BepInEx plugin (such as Newtonsoft.Json Detector) still follows the normal plugin rules. Libraries merged into a plugin remain part of that plugin's file hash. Native DLLs are not supported as references.