Admin Is Not Devcommands: What Actually Works on a Valheim Server
The most common misunderstanding on a rented Valheim server is that admin rights unlock cheats. They do not. Valheim runs two separate command systems — the ordinary player commands anyone can type, and devcommands, which is where god, fly, spawn and tod live. Being on adminlist.txt gives you neither of those; it gives you a third thing entirely.
On sourcing. Iron Gate do not publish system documentation. The figures below come from the community wikis and can change with any patch.
Three Categories, Not Two
| Category | Who can use it | Examples |
|---|---|---|
| Player commands | Anyone, from the chat window | save, ping, info |
| Admin commands | Anyone on adminlist.txt | Kick, ban, server management |
| Devcommands | A separate toggle | god, fly, spawn, tod |
Player commands do not require devcommands and are available to every connected player. Typing / and pressing tab shows what is available — which is worth telling your players, because save and ping are genuinely useful and cost nothing to grant.
Admin commands come from the list file and cover server management: removing a disruptive player, banning them, forcing a save.
Devcommands are the cheat layer, and they are gated separately from both.
Why Devcommands Do Not Simply Work
Devcommands are designed around single-player and self-hosted sessions. On a dedicated server they are not something an admin flag switches on, which is why "I am an admin but fly does nothing" is such a common report.
There is a second catch even where they do work: devcommands reset when the session ends. The wiki is explicit that enabling them is something you end up doing every session rather than once, because the setting does not persist.
So the honest expectation for a rented server is:
- Player commands — always available, to everyone.
- Admin commands — available to whoever you listed.
- Devcommands — a separate matter, session-scoped, and not what adminlist.txt is for.
What This Means for Your Group
Tell people what admin actually is before you grant it. Most requests for admin on a group server are really requests for spawn or fly, and granting adminlist access does not deliver either — which leaves the person feeling short-changed and you feeling misunderstood.
Two better framings:
- "Admin lets you kick and ban." That is the honest description, and it is the reason to have one or two admins rather than everybody.
- "Cheats are a world setting, not a person setting." If your group wants a relaxed world, the lever is the world modifiers and presets system, which adjusts combat, resources, raids and portals globally — not a per-player flag.
World modifiers are the sanctioned version of what people ask devcommands for. They are configured once, apply to everyone, and survive the session.
The 1.0 Cheat Flag
Valheim 1.0 added a flag that records whether cheats have been used in a world, and it is worth knowing before somebody experiments.
That is the real cost of devcommands on a shared world — not the balance, but the mark. A group that wants a relaxed experience is better served by world modifiers, which are a supported configuration rather than a flagged intervention.
Setting Up a Server Sensibly
- Grant admin to one or two people, for kicks and bans — not as a status symbol.
- Tell everyone that player commands already exist.
save,pingandinfoneed no permission at all. - Use world modifiers for difficulty, not devcommands. They are global, persistent and supported.
- Do not promise cheats with admin.
god,fly,spawnandtodare not what the list file grants. - Remember devcommands reset per session wherever they do work, so they are never a permanent arrangement.
- Check the 1.0 cheat flag before letting anyone experiment on a world you care about.
Running your own Valheim server
Sorting out who can do what is easier when the list files and world modifiers are in the same panel. A gamever Valheim server gives you both, for up to 10 players, with one-click backups and automatic updates.
Conclusion
Valheim runs three command categories, not two, and they are not a ladder. Player commands — save, ping, info — are available to everyone from the chat window and need no permission; typing / and pressing tab lists them. Admin commands, granted through adminlist.txt, cover server management: kick, ban, force a save. Devcommands — god, fly, spawn, tod — are a separate system built around single-player and self-hosted sessions, are not switched on by admin rights, and reset when the session ends even where they do apply. That makes "I am an admin but fly does nothing" the correct behaviour rather than a fault. For a group that wants an easier world, the supported lever is world modifiers and presets — global, persistent, and not subject to Valheim 1.0's cheat flag, which records that cheats were used at all.
Want permissions and modifiers in one panel? Rent a Valheim server at gamever.io — instant setup, up to 10 players, one-click backups and updates, and 24/7 uptime. Start with a free trial and use promo code WELCOME.