Valheim has found a very Valheim way to revisit its achievement rules: not with a stern warning screen, an elaborate appeal process, or a hidden toggle, but with an absurdly direct line of text that asks players to own what they did.
Following the game’s 1.0 release, Iron Gate Studio has added 50 achievements and introduced a route for players who have used developer commands to opt back into achievement tracking. The catch is that they must type a lengthy command that plainly acknowledges the choice. The required text is yesiuseddevcommandsbutiwantmyachievementsanyway, entered without quotation marks or punctuation.
It is an unusually playful solution to a familiar problem in games: how should achievements work after someone has enabled tools that can change the usual progression loop? Rather than pretending the question has an entirely technical answer, Valheim’s new option makes the player explicitly decide what those achievements mean to them.
What changed for achievement hunters
Before the September 11 update, using developer commands meant a player could no longer earn Valheim achievements. That approach made the boundary easy to understand. Developer commands were available, but activating them carried a clear consequence for anyone who also wanted the game’s official achievement record.
The new system does not erase that boundary so much as make it elective. Players who have previously been blocked from achievements because they used devcommands can now restore eligibility by entering the opt-in phrase. In practical terms, achievement tracking can resume even if a player has used the game’s developer-command functionality.
That distinction matters. This is not presented as an argument that developer commands do not affect progression. It is a decision to let players take responsibility for the overlap between altered play and achievement completion. The deliberately unwieldy phrase ensures the choice is unlikely to happen accidentally, while its wording makes the player’s intent impossible to misunderstand.
“The fixes include a function to let you opt into using achievements even though you have been blocked from doing so because of previous usage of devcommands,” the update notes explain. “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 reference to Oden fits Valheim’s Norse-flavoured world, but the bigger point is serious beneath the joke: the game is placing the ethical judgement with the player. Its system can record an unlocked achievement; it cannot determine whether that accolade carries the same personal value after progression-altering commands have been involved.
Developer commands, explained
Developer commands are built-in commands that can alter aspects of a game beyond its standard moment-to-moment interface. They may be useful for experimentation, testing, troubleshooting, building, or simply playing in a less restrictive way. In a survival game, however, tools that alter normal constraints can also change the circumstances under which milestones are reached.
Achievements are generally designed as a record of completing defined objectives. For some players, their appeal is the challenge itself: reaching a target within the systems, risks, and limitations the game normally establishes. For others, achievement lists are a checklist, a personal diary of time spent in a game, or an invitation to see more of its content. Those are not identical motivations, and Valheim’s opt-in is effectively recognizing that difference.
Under the earlier rule, the game made the decision categorically. Use developer commands, and achievements were no longer available. Under the current rule, the game still flags the prior use of those commands, but offers a conscious override. It is a small design change with a clear philosophical shift: the technical restriction remains meaningful enough to require an explicit action, yet the final call is no longer permanently locked away.
The command itself is the punchline. A short, neutral setting label could have restored achievements with little fanfare. Instead, the phrase reads like a full confession typed into the console. Its length is part of the deterrent and part of the joke. Anyone enabling it is not merely pressing a button marked “allow”; they are affirming, in one uninterrupted string, that they used developer commands and would still like achievements.
Why the wording works
There is a practical reason for making an opt-in command conspicuous. Players sometimes enable settings while troubleshooting or experimenting, then later forget which systems were affected. A command as explicit as this one creates a memorable moment. It is difficult to mistake it for an ordinary gameplay input or claim that its consequences were unclear.
It also avoids treating every use of developer tools as identical. The supplied update details do not distinguish between different reasons for using devcommands, and there is no need to invent such categories. The relevant fact is simpler: players may now choose to restore achievement tracking after having used them. Valheim does not demand a justification, inspect intent, or offer a public verdict. The game asks the player to make the call.
That makes the feature less about “catching” cheaters than about communicating values. The old implementation established a hard rule. The new one makes its exception intentionally conspicuous and leaves room for personal judgment. Even the warning is framed through the game’s fiction rather than as a scolding anti-cheat message.
For players who prefer achievements to represent entirely unmodified progression, the practical answer is unchanged: do not use the opt-in after using developer commands. For players who regard achievements as a personal collection of objectives rather than a certification of a particular ruleset, the new command provides a way to keep collecting them. Neither position requires the game to pretend that the two paths are the same.
Fifty new achievements arrive with 1.0
The timing is important because Valheim’s 1.0 update brings 50 new achievements to pursue. A larger achievement list gives players more reasons to revisit objectives and track long-term progress, so the rules around eligibility become more visible than they might be in a smaller update.
There is no need to read the opt-in as a broad declaration that all achievement styles are equivalent. The update’s wording specifically identifies prior devcommand use as the reason players may have been blocked, then offers a function to opt back in. The game is transparent about that history rather than quietly changing the outcome in the background.
That transparency is useful for anyone deciding how they want to approach the new awards. Players who want a conventional achievement run can keep developer commands out of that save or play period. Players who have already used those tools and still want the 1.0 achievements can use the explicit opt-in. The system gives both groups a clearly legible route, though only one carries the tongue-in-cheek confession.
Achievement policies are often discussed as though they are only about enforcement. Valheim’s change shows that they are also about framing. A permanent block says that the game’s record has one fixed standard. An opt-in says that the record can be restored, while emphasizing that the player should think about the meaning of doing so. The phrase, and Oden’s watchful disapproval, ensure that this is not a subtle distinction.
What players should take from the update
- Achievement tracking can be restored: players previously blocked due to developer-command use now have an opt-in route.
- The command is intentionally explicit: enter yesiuseddevcommandsbutiwantmyachievementsanyway with no quotation marks or full stop.
- The choice is personal: the update leaves it to the player’s judgment whether restoring achievements after using devcommands feels appropriate.
- There are more goals on the board: Valheim 1.0 adds 50 achievements.
For a game built around survival and self-directed adventure, letting players define the value of their own achievement record is a fittingly hands-off answer. Iron Gate has not hidden the compromise. It has made players type the compromise out in full.
That is why the feature lands as more than a joke, even though it is undeniably a good one. The command turns a potentially dry policy change into a moment of accountability. If a player wants the achievements, Valheim will allow it. Whether Oden approves is apparently another matter.
For more on how platform rules and game visibility can affect PC players, see our coverage of a Steam label change that affected a vampire RPG’s search visibility.
