Valheim 1.0 Cheat Flag: How Devcommands Lock Achievements

Valheim 1.0’s achievement system carries a built-in cheat flag — an eligibility mark for the achievement list, not an anti-cheat that bans or blocks play — and it flags more than just the person who typed a command. Iron Gate’s own 1.0 FAQ lays out several distinct rules for how a world or character can end up marked as cheated, alongside one named exception, and at least one of them — picking up the wrong item from a friend’s inventory — catches players who never touched the console at all. This runs through exactly what triggers the flag, what it locks, what does and doesn’t clear it, how to get achievements back with the console command hotfix 1.0.12 added, and precautions for a co-op run through the Valheim boss order.

The cheat flag is Iron Gate’s eligibility mark for the achievement list that shipped with Valheim 1.0 — it decides whether a character and world can still earn achievements, rather than a ban system. Do not confuse this achievement rule with separate server-admin policies or the effects of individual commands. It is built to stop cheat commands from being used to unlock achievements without earning them properly. The rules below come from the FAQ and apply on every platform; what differs by platform is the 1.0.12 opt-back-in command, which shipped on Steam first. There is a system in place to prevent achievements from being unlocked if you have cheats enabled, and most commands (such as “spawn”) will place a flag on your current character and world save, informing you that it is permanently locked from getting any achievements. The flag isn’t one setting — it’s several separate triggers, some tied to commands, some tied to items, and one tied to a world modifier.

This sits alongside the rest of the 1.0 launch, which added the Deep North biome and its patch notes, new boss content, and the full achievement list — all built and published by Iron Gate Studio and Coffee Stain Publishing.

The part that trips people up is that the flag isn’t limited to whoever ran the command. Characters that have used cheats before 1.0 will also be marked in this way, and there will also be a confirmation required to enter a cheated state after 1.0, to prevent you from accidentally marking out your character and world as cheated. Read that warning before confirming a command; the FAQ does not describe a pre-1.0 achievement lock, since achievement statistics begin tracking with 1.0.

The genuinely underrated part is item contamination. Items that have been spawned in will also be marked in this way, and if a non-cheated player character picks up a cheated item, they will enter a temporary cheat state. In practice, that means a friend who spawned in a stack of resources on their own character can hand you an item that quietly flags your character too, even though you never touched a console yourself. Check a shared chest before a boss fight; marked items are visible.

Here’s the split that matters most for anyone chasing boss achievements. Temporarily cheated characters are locked out from unlocking achievements while in this state, and can become eligible for achievements again if they throw out all cheated items from their inventory. Cheated items are visibly marked, so in theory you can check your own inventory before a boss fight and see exactly what’s flagging you.

The permanent flag from devcommands is a different story. The original FAQ describes it as locking a character and world “permanently” and does not lay out a way to reverse it. That changed after launch: hotfix 1.0.12, released on 11 September 2026, added a console command that opts a character back into achievements after devcommands or mods. Iron Gate’s own framing: “We will leave it to your own judgement whether or not to activate this function – Oden will surely know if you use it dishonourably.” The same hotfix added a popup that tells you when achievements are available again after a temporary block. It is an opt-in for achievement eligibility; the notes do not say the underlying mark is deleted.

Hammer-mode gets treated by a lot of players as a harmless building convenience, but Iron Gate lists it among the world modifiers that block achievements, as a temporary cheat. Some world modifiers such as hammer-mode will also block certain achievements. Hammer-mode counts as a temporary cheat. The FAQ doesn’t publish which specific achievements hammer-mode blocks, so treat “certain achievements” as exactly that — an unspecified subset, not the full list, until Iron Gate says otherwise.

The practical setup, and this is editorial judgment rather than anything Iron Gate has published as a formal recommendation: keep one world per group and treat devcommands as off-limits on it entirely, including “just to check something.” The FAQ puts the permanent mark on the character and world save together, so do not assume that moving your main character to a test world isolates the risk. The FAQ does not spell out every case for a clean visitor joining a flagged world without picking up marked items. Experiments with spawn commands or hammer-mode belong on a separate character on a separate throwaway world — a spare world alone does not protect your main character — and it is worth backing up the character and world files before you try anything, because the mark is not described as reversible.

The flag concerns achievement eligibility; it is not itself a save wipe. Commands can still change a save, which is a separate reason to keep backups. On Steam, the 1.0.12 command above restores achievement eligibility for the character; if your platform does not have that command, check its current patch notes before deciding to restart. Discarding marked items addresses the temporary item state, while the original FAQ does not document a reset procedure for the persistent command flag. Keep your existing saves rather than deleting progress. If you use a farming service — ours included — ask how the items are obtained; ask specifically whether spawned items or devcommands are involved. The FAQ addresses spawned items; it does not justify a guarantee about every item supplied by a service.

“Throwing out cheated items clears every kind of flag”

It only clears the temporary state from picking up a cheated item. The FAQ separates that case from the permanent flag placed on a character and world by devcommands — throwing out items doesn’t touch that one.

“Only the person who ran the command gets locked out”

If a non-cheated player character picks up a cheated item, they will enter a temporary cheat state — so a teammate who never opened the console can still end up flagged just by looting a shared chest.

“Hammer-mode is just a building tool, not a cheat”

Iron Gate’s own FAQ lists hammer-mode among the world modifiers that block certain achievements and classes it as a temporary cheat — lighter than a devcommand flag, but not nothing.

Sources and Confidence

Everything mechanical above comes from Iron Gate’s 1.0 FAQ and the 1.0.10/1.0.12 hotfix notes; the one press row is marked as such.