RunicSentinel

Runic Sentinel 1.6.2

Manage your Valheim server from the F3 dashboard. Choose approved mods, manage administrators and bans, run commands, view player reports, and adjust building and terrain limits.

Admission rules and administrator permissions are managed by the server.

Installation and setup

1. Install RunicSentinel 1.6.2 on the host (dedicated or listen server) and administrator clients. Ordinary players need only RunicSentinelClient 1.0.5.
2. Install the dependencies listed by your mod manager, including Runic Safety for full Sentinel. Do not install RunicSentinelServer alongside full RunicSentinel.
3. Start with Remote Admission → Policy = Optional in the host configuration.
4. Add your account ID to the host's adminlist.txt, join the game and press F3.
5. Select Set Up Sentinel, choose your mod policy, and select Apply & Sign Policy.
6. When your players' mod profiles are ready, set admission to Required and restart the host.

Keep your existing configuration and the host's private key in BepInEx/config/RunicSentinel/server-private. When replacing RunicSentinelServer, preserve its configuration and policy files. Before first launch, copy chazman.RunicSentinelServer.cfg to chazman.RunicSentinel.cfg if the latter does not already exist. Remove the Server package. RunicSentinelServer 1.3.0 does not provide the new building and terrain controls. Existing signed mod profiles may need updating for the new plugin versions.

Required and optional mod setup

Admission mode and mod categories are separate settings. Optional admission monitors policy results. Required admission enforces the signed policy when a client connects.

1. Install full RunicSentinel on the host and administrator clients. Ordinary players install RunicSentinelClient.
2. Keep Remote Admission → Policy = Optional in the host configuration during setup. Join as a server administrator and open F3 → Mod Policy. On first setup, select Set Up Sentinel.
3. Select Required for plugins every player must have, Allowed for permitted optional plugins, Greylisted for permitted plugins whose presence is recorded, and Blocked for prohibited plugins. The selected category displays [X] in gold.
4. To reject every unlisted plugin, set the unknown-mod policy to Forbidden. Explicitly allow all permitted client plugins and dependencies, including RunicSentinelClient for ordinary players and full RunicSentinel for administrators. Leave these two alternatives Allowed unless everyone uses the same package.
5. Select Apply & Sign Policy to save the categories as the host's active signed rules.
6. Set Remote Admission → Policy = Required in the host configuration, restart the host, and reconnect.

Base required rules on the players' client plugins. The displayed list includes server and administrator plugins; server-only plugins do not belong in the required client list. Rules identify BepInEx plugin IDs, rather than Thunderstore package names.

Changing a category retains existing version and file restrictions. Open advanced rules to review them: each line is plugin.id|version|sha256; * accepts any version or file hash in that field. For example, example.plugin|*|* requires only that plugin's presence when placed in Required.

If a connection is rejected, read Last admission denial in F3 or run runic_sentinel report. RequiredMissing means a required plugin is absent; ForbiddenPresent means a blocked plugin is installed; UnknownForbidden means an installed plugin has no explicit rule; PluginMismatch means its version or file hash differs. A greylisted plugin remains subject to any version and file restrictions on its rule.

Taller buildings and deeper terrain

Open F3 → World → Building and terrain:

1. Check Enable custom building and terrain limits.
2. Set the vertical support multiplier, maximum terrain raise and maximum digging depth.
3. Select Save building limits for next restart, then restart the host and rejoin.

The panel shows running limits and restart status. The World tab replaces Server Cap and retains its player-cap controls below. Changes require host administrator authorization; stale edits are rejected.

The support multiplier ranges from 1–10. A value of 2 halves vertical support loss; it does not guarantee twice the building height because materials, connections and horizontal spans still matter. Terrain limits range from 1–64 metres, measured above or below the original ground, including already excavated terrain. Defaults are disabled, with support 1, raise 8 and dig 8. Water level and the inability to dig tunnels are unchanged.

Ordinary players only need SentinelClient. The host sends its limits before world admission; player configuration cannot override them. Custom-limit hosts require compatible acknowledgements even with Optional admission. Connections to an unmodified host retain vanilla limits.

Keep the same building and terrain limits when continuing an existing world. Manual configuration is also available under [Building and Terrain] in BepInEx/config/chazman.RunicSentinel.cfg.

F3 dashboard

• Mod Policy: search mods by name, choose Required, Allowed, Greylisted or Blocked, then select Apply & Sign Policy. Advanced rules let you specify versions and file restrictions.
• People: filter all people, online accounts, administrators or banned accounts. Manage administrator rights and bans, kick connected players, review recent activity and create player reports.
• Commands: enter a command and press Enter or Run. Browse the command guide, read command output, and toggle God, Ghost, Fly, Freefly, debug mode or no-cost building with live On/Off indicators. Sentinel authorizes each request; no separate Server Devcommands mod is required.