Valheim: How to Use Dedicated Server Admin Commands Safely

On a vanilla Valheim dedicated server, the commands you can reliably use are moderation and save tools: kick, ban, unban, banned, and save. Open the in-game console with F5, but make sure your account is authorized in the server’s admin list first. Typing devcommands does not grant god mode, item spawning, teleportation, or raid control on a normal dedicated server.

The important split is simple: vanilla dedicated servers support live moderation; local worlds and mod-enabled dedicated servers can use the wider developer command set. Treating those as the same thing is how admins end up typing god, goto, or event during a multiplayer session and assuming the console has failed.

Table of Contents (10)

Enable the Console and Get Admin Access First

For the Steam version of Valheim, enable the console by opening Valheim → Properties in Steam and entering -console under Launch Options. Launch the game, join the dedicated server with the character you want to administer from, then press F5 to open the console.

Console access and server-admin permission are separate checks. The -console launch option lets the client display the console, while the server’s admin list determines whether that character can run dedicated-server moderation commands. Add the appropriate Steam user ID to the admin list through the server files or host control panel before joining.

A player can open F5 without being a server admin. In that situation, seeing the console does not mean kick or ban will work. Recheck the authorized account and reconnect after changing the server’s admin configuration.

Vanilla Dedicated Server Commands That Matter

These are the commands worth keeping handy when you are running a persistent multiplayer world. They handle griefing, disconnect problem players, review bans, and protect progress after an intervention.

Command	Use	Best time to use it
kick [name/IP/userID]	Immediately removes a player from the server.	Connection problems, disruptive behavior, or a quick removal while you investigate.
ban [name/IP/userID]	Blocks a player from reconnecting.	Griefing, repeated harassment, or deliberate damage to the shared world.
unban [IP/userID]	Removes a ban entry.	A mistaken ban or a player returning after a resolved issue.
banned	Displays the current ban list.	Before reversing a ban or checking whether an enforcement action was recorded.
save	Forces an immediate world save.	After a moderation action, a controlled event, or any important correction.

Command references commonly show player names, IP addresses, and user IDs as valid targets for kick and ban. A user ID is the safer identifier when names are similar, duplicated, or contain unusual characters. Check the exact identifier format accepted by the server build and hosting setup before using a ban command during a busy session.

Use Kick for Immediate Removal, Ban for Persistent Enforcement

kick disconnects someone now, but it does not stop them from joining again. Use it for a temporary removal or when a player needs to reconnect after a desync. ban is the persistent tool: it adds the player’s identifying information to the server ban list and prevents another connection attempt.

Run banned before using unban. That small check avoids clearing the wrong entry when multiple players have been removed over the life of a shared world.

Force a Save After a Live Intervention

Use save after resolving a major incident, moving ahead with a planned session change, or finishing any mod-enabled admin work that altered the persistent world. The command gives you a clean checkpoint instead of relying on the next automatic save cycle.

This is especially useful on worlds where several players are building, transporting metals, or exploring the Deep North at once. A forced save cannot undo griefing that already happened, but it preserves the corrected state you want the server to keep.

What Devcommands Does on a Dedicated Server

devcommands toggles the broader developer-command mode in a session. In a local world, that opens access to tools such as god mode, spawning, coordinate teleportation, and manually controlled events. On a vanilla dedicated server, it does not unlock those cheat commands for admins.

That limitation applies even when you have correctly enabled -console, pressed F5, and added yourself to the server admin list. Native dedicated-server permissions cover moderation and management rather than the full creative/debug suite.

Server or world type	F5 console	Moderation commands	God mode, spawning, teleportation, events
Vanilla dedicated server	Available with -console	Available to authorized server admins	Blocked as native dedicated-server functions
Local single-player or self-hosted local world	Available with -console	Relevant only if other players are present	Available after devcommands is enabled
Mod-enabled dedicated server	Available with -console	Available to authorized server admins	Available when the server-side mod is configured to allow them

God Mode, Teleportation, Spawns, and Events Require Server-Side Support

If you want to run a managed creative session, recover players from inaccessible terrain, stage raids, or test a Deep North build area, the common dedicated-server solution is a server-side mod such as Server Devcommands. It extends the developer-command set to the dedicated environment while still limiting use to accounts listed as server admins.

Keep that modded control separate from ordinary moderation. Commands that change player state, world conditions, inventory, terrain access, or enemy activity can permanently affect the shared save. Back up the world before enabling a creative-control mod or staging an event that could damage a settlement.

Command	Effect	Dedicated-server requirement
devcommands	Enables or disables the wider developer-command mode.	Useful in local worlds; does not by itself unlock dedicated-server cheats.
god	Enables invincibility for the active character.	Requires server-side cheat support on a dedicated server.
goto x y z	Teleports the active character to specified world coordinates.	Requires server-side cheat support on a dedicated server.
spawn [item code]	Creates an item or entity using its internal code.	Requires developer commands and dedicated-server mod support.
event [name]	Starts the specified raid or world event.	Requires server-side cheat support on a dedicated server.
randomevent	Starts a random world event.	Requires server-side cheat support on a dedicated server.
stopevent	Ends the active event.	Requires server-side cheat support on a dedicated server.

Teleportation Has Limits in Vanilla Multiplayer

goto x y z is a coordinate teleport command, not a universal player-management tool. On a vanilla dedicated server, it remains unavailable even to an authorized admin. A mod-enabled setup can make it useful for recovering from terrain problems or reaching a planned event site, but use fixed coordinates carefully: a wrong value can place a character far from their gear, portal network, or group.

There is no native dedicated-server map command to rely on for revealing terrain or managing every player’s map state. Keep a portal route, marked meeting point, and a backup plan for players who die during long expeditions instead of expecting console navigation to solve every recovery problem.

Events Need a Clean Arena and a Stop Plan

event [name] and randomevent are useful for organized raids, but they should be treated as world-altering session tools. Start them away from vulnerable bases unless base defense is the point of the event, make sure participants understand where to regroup, and keep stopevent ready before the encounter begins.

This matters more on a 1.0 world with late-game progression and Deep North activity. A controlled fight is manageable; an unexpected raid near a packed dock, animal enclosure, or trophy room can leave a persistent cleanup job for everyone.

Safe Admin Routine for a Live Server

• Confirm that the active account is in the server admin list before the session begins.
• Use kick when a player needs to leave immediately, then use ban only when the block needs to persist.
• Check banned before removing an entry with unban.
• Run save after an important correction or before any planned maintenance.
• Reserve god mode, goto, spawn, and event commands for local testing or a dedicated server that has deliberate server-side mod support.
• Back up the world before creative commands, event testing, or large-scale item spawning.

Vanilla Valheim has no RCON or remote console for this work. Administration happens through the in-game F5 console and the server’s authorization files. The dedicated server’s command window is for the server process itself; when shutting that process down, use CTRL + C rather than simply closing its window, since closing the window can leave the server running in the background.

Keep Moderation and Creative Control Separate

For a normal dedicated world, set up the F5 console, authorize trusted admins, use kick, ban, unban, banned, and save, then leave the developer tools off. Add a server-side devcommands mod only when the server’s purpose genuinely includes teleport recovery, event hosting, god mode, or controlled item spawning.