Valheim Command Manager

At a glance

Valheim is the most constrained of the games we host, and the reason is worth understanding before you plan anything: Valheim's dedicated server has no RCON, no telnet, and no admin API. Nothing exists to send a command to.

What fills that gap is the GameGrid Bridge, a BepInEx plugin we install on your server. It exposes a small HTTP interface that the panel talks to. Everything here goes through it - which is why the catalog is seven entries rather than fifty.

It is not a trimmed-down console. It is the complete set of things the bridge can do. If the bridge is not installed or not running, every Valheim schedule fails - and Bridge Health Check exists to tell you which.

Your first schedule

1. Open your server, click Event Manager, then the Command Manager tab.

2. Click + New Schedule.

3. Name it Bridge Health, pick Bridge Health Check, choose Every N minutes and set 15.

4. Click Create, then Run Now, then Log.

5. A green Success row means the bridge is alive and everything else on this page will work.

Starting with the health check rather than a save is deliberate - it proves the channel before you rely on it for something that matters.

The seven things you can schedule

Custom Command is narrower on Valheim than anywhere else. It accepts broadcast, save, spawn, players, info, health and help, and nothing beyond that. There is no back door to a command the bridge does not implement.

What is not available, and why

None of these is missing by choice. The bridge cannot reach into the game client, so nothing that lives there is schedulable.

Giving an item to everyone online

Spawn Item is the one Valheim action that takes a player, and it carries an Send to every online player checkbox. Tick it and you name nobody: when the schedule fires, the platform asks the bridge who is online and sends one spawn per player.

Session IDs, and why the checkbox is the better tool

The identifier used is the player's session ID - the ZNetPeer.m_uid the bridge reports - not their character name.

A Valheim session ID changes every time the player reconnects. It identifies a connection, not a person.

Valheim has no "everyone" selector of its own, so this is genuinely one command per player, one log row each.

Valheim saves are slow, and that is fine

A Valheim world save can hold the game for up to 90 seconds on a large, long-lived world. That is the game, not the platform.

Scheduled saves are given that time. This was not always true - saves used to be cut off at 15 seconds, which meant the scheduler recorded an error on a save that had in fact completed perfectly well.

If you have old Valheim save schedules that look like they have been failing, check their recent history. They may have been working the whole time.

Two practical consequences:

Schedules worth building

Save, then say so

One trigger, and players stop asking whether saves are happening.

A restart warning that stays accurate

Restart at {nextRun} - {players} online, get somewhere safe

Broadcast Message, ten minutes ahead of your nightly restart. The placeholders are filled in as the message goes out.

Reading the history

Click Log for the last 50 runs, each with what was sent, what the bridge answered, and a status.

Each status and what to check: Command Manager Troubleshooting.

Everything else a schedule can do

Multi-step sequences, waits, run conditions, overlap policy, catch-up windows, start spread and missed-run alerts work the same on every game.