Dedicated-server setup

Install Valheim WebMap.

Use these steps to understand the server-package layout. The inspected runtime line uses BepInEx 5 and .NET Framework 4.8 (net48); BepInEx 6 is not supported. The exact supported Valheim build and operating-system boundary will be listed with the public download.

Unofficial community mod

Valheim WebMap is an unofficial community mod. It is not affiliated with, endorsed by, sponsored by, or supported by Iron Gate AB or Coffee Stain Publishing AB. Valheim and related marks belong to their respective owners. Use of mods is at the user's own risk, and compatibility with future game versions is not guaranteed.

No public binary is available yet

The free binary download is not available yet.

Prerequisites

  • A Valheim dedicated server.
  • An existing BepInEx 5 installation that already starts correctly. Do not substitute BepInEx 6.
  • The release is built for the .NET Framework 4.8 (net48) runtime line.
  • A release-specific compatibility list matching the package you install.

Valheim Dedicated Server and BepInEx are prerequisites; they are not included in the WebMap package. Players connecting through the game client do not install WebMap or BepInEx.

A published package does not require Docker, a .NET SDK, Node.js, npm, or a source checkout.

Install the server package

  1. Stop the dedicated server.
  2. Extract the released deployment archive at the Valheim Dedicated Server game root. Verify that it creates this directory:
BepInEx/plugins/WebMap

The deployment overlay contains the plugin, its browser assets, the project MIT license, the separately bundled dependency license, and third-party notices. It contains no live configuration, passwords, map data, world files, backups, private infrastructure address, or private source-repository URL.

  1. Start the server once. WebMap creates its default configuration in the BepInEx configuration directory:
BepInEx/config
  1. Stop the server again before changing configuration.
  2. Edit the generated configuration, then restart the server.
  3. Open the browser companion only through the network boundary documented for that release.

Stop before editing

Configuration changes made while the server is running can be lost when it shuts down.

Updating

  1. Stop the server.
  2. Back up the existing plugin directory, live configuration, and map_data.
  3. Replace the package files using the release notes for that version.
  4. Start the server and verify the browser companion.
  5. If the old interface remains, verify the loaded server version and use one hard refresh as a diagnostic step.

Network exposure

The direct local WebMap address uses plain HTTP and is intended for the server computer or a trusted LAN. Do not expose the raw port directly to the Internet. Internet-facing editing requires a separately reviewed HTTPS and access-control boundary; authentication for edit and administrator actions is not proof that normal viewing is protected.