Valheim Console Commands & the 1.0 Cheat Flag (What It Costs Your Server)

 

    Valheim's console has always been harmless fun. From 9 September it has consequences. Version 1.0 adds achievements, and with them a rule that reaches beyond the person typing: cheat usage permanently flags characters and worlds, and spawned items are visibly marked and temporarily restrict any non-cheated player who picks one up. On a ten-player server that makes console access a group decision. Here is how to open it, what triggers the flag, and what to agree before launch day.

 

Opening the Console

 

Platform	How
Keyboard	F5
Controller	LB + LT + Start
Steam	Add -console to launch options: "Right mouse click on Valheim → General. Then, under Launch options, add the -console argument"
Microsoft Store	Append -console to a shortcut's Target field after Valheim.exe
Mac App Store	Run /Applications/Valheim.app/Contents/MacOS/Valheim -console in Terminal
Xbox	"On Xbox, the console is enabled by default."

 

    There is now an easier route than any of those launch arguments. The Call to Arms update (0.221.4, September 2025) "added the option in the settings menu to enable the developer console" — and noted that "the command line argument -console overrides the setting."

 

    So the launch-argument methods above still work and still win, but for most players a settings toggle is now enough. The distinction matters if you have -console set and cannot work out why the settings toggle appears to do nothing: the argument is taking precedence.

 

    Note the Xbox row carefully too. Xbox players have the console available without doing anything, while PC players must deliberately enable it. On a crossplay server that is an asymmetry worth knowing about — the platform least likely to be tinkering has the lowest barrier to it.

 

    Most commands are gated behind one more step. Iron Gate: "Most console commands become eligible only after typing and executing devcommands." So opening the console is not itself dangerous; devcommands is the line you cross.

 

    A Microsoft Store alternative, if you prefer not to make a shortcut:

 

start shell:appsFolder\CoffeeStainStudios.Valheim_496a1srhmar9w!Game -console

 

What the Flag Actually Does

 

 

    From the official 1.0 FAQ, three rules:

 

Rule	Effect
Cheat usage is flagged permanently	On characters and worlds — it does not wear off
Most dev commands lock achievement eligibility	With narrow exceptions, such as freefly
Spawned items are visibly marked	And temporarily restrict non-cheated players who pick them up

 

    The third rule is the one that makes this a server issue rather than a personal one. A spawned item is not just the cheater's problem — it is a marked object sitting in your shared world, and anyone who picks it up takes a temporary restriction with it.

 

    So a single spawn command in a communal chest can quietly affect several people's achievement progress, none of whom typed anything.

 

    freefly is explicitly called out as an exception, which is useful: the camera command builders use for screenshots does not cost you achievements. If your group's console use is entirely photography, you are fine.

 

    And the world is flagged too, not just the character. Rolling a fresh character does not clean a flagged world.

 

Achievements Track From Install

 

 

    Nothing backfills. The achievement system tracks statistics starting from the 1.0 download, so anything your group achieved during Early Access is not credited. Iron Gate's own example is defeating Eikthyr — if you killed him in 2021, you kill him again.

 

    That matters for the world decision. One argument people give for keeping an old world is preserving progress — but achievement progress is starting from zero either way, on any world. It removes a reason to stay put, and pairs with the fact that the Deep North only generates in unexplored terrain.

 

    It also means the flag is worth avoiding from day one. There is no window where cheating is "free" because you have not started achievements yet — you start them the moment you install.

 

What to Agree Before 9 September

 

 

    This is a social decision, not a technical one, and on a dedicated server there is no toggle that solves it for you. Four things worth settling:

 

    1. Does your group care about achievements at all? If nobody does, none of this matters and you can use the console freely. Establish that explicitly rather than assuming.

 

    2. If they do — no devcommands on the shared world. Not "be careful with it". The flag is permanent and applies to the world, so one use ends the conversation for everybody.

 

    3. Nobody spawns items into shared storage. This is the rule most worth stating aloud, because the person spawning may not realise the marked item restricts whoever picks it up.

 

    4. Use a second world for experiments. Standing up a separate server for testing builds, trying a modded stack or messing with commands costs far less than flagging the world your group has invested in. It is also the cleanest way to keep a modded PC-only world alongside a vanilla crossplay one.

 

    One practical note for mixed groups: since Xbox has the console on by default, it is worth mentioning the rules to console players specifically. A PC player had to opt in with a launch argument and probably knows what they are doing; an Xbox player may open it by accident.

 

    And remember there is no test branch. Iron Gate confirmed "No. We want everyone to get to experience 1.0 at the same time!" — so nobody, including you, gets to try any of this before it counts.

 

Practical tips

• F5 on keyboard, LB + LT + Start on controller. Steam needs the -console launch argument.
• Xbox has the console enabled by default — mention the rules to console players.
• devcommands is the line, not opening the console itself.
• Cheat flags are permanent and apply to the world, not just the character.
• Spawned items are marked and restrict whoever picks them up — including innocent players.
• freefly is an explicit exception — screenshot flying does not cost achievements.
• Achievements track from install. Nothing you did in Early Access counts.

 

Running your own Valheim 1.0 server

 

    The safest way to keep a shared world clean is to have somewhere else to experiment — a second server for testing builds, mods and commands, so the world your group actually plays never gets flagged. A gamever Valheim server spins up in minutes, keeps both worlds online around the clock for 1–10 players each with full crossplay, and takes one-click backups before the 9 September update — which matters more than usual given 1.0 ships with no public test branch.

 

Conclusion

 

    Valheim's console opens with F5 on keyboard or LB + LT + Start on controller, needs the -console launch argument on Steam, and is enabled by default on Xbox — but the meaningful line is devcommands, which is what unlocks most commands. From 1.0 on 9 September that line has a cost: cheat usage permanently flags both characters and worlds, blocking achievements, with freefly named as an exception. The rule that makes it a group problem rather than a personal one is that spawned items are visibly marked and temporarily restrict any non-cheated player who picks them up — so one person's command reaches everyone sharing the world. Since achievements track only from the moment you install 1.0, there is no free window either. Agree the policy before launch day, and keep a second world for anything experimental.

 

    Want somewhere to experiment that is not your main world? Rent a Valheim server at gamever.io — instant setup, one-click backups and updates, full crossplay and 24/7 uptime. Start with a free trial and use promo code WELCOME.