Iron Gate shipped Patch 1.0.20 for Valheim on 15 October 2026, a little over five weeks after 1.0 ended Early Access on 9 September. The post opens with an apology dressed as a joke: “We’ve heard a lot of you pointing out that you haven’t been getting as many trophies as you should from your kills, and this patch should finally fix that.” The line that matters more, if you played the first week of 1.0 and then stopped, is the fourth bullet: a reset of the cheated flag on every item and build piece a launch bug had wrongly marked.
What this covers: all eight lines of the 1.0.20 notes, what each one changes in play, and the four-week history that produced the cheated-flag reset — including the Mac App Store exception that broke crossplay for this patch specifically. Why it matters: two of the eight fixes decide whether an item in your chest counts as legitimate and whether a rare drop is distributed fairly. Both are changes you only notice if you know what the old behaviour was. Who should care: returning 1.0 players still holding gear stamped as cheated, trophy farmers, and anyone running a dedicated server on the same machine they play on.
The advice here assumes patch 1.0.21, published 28 October 2026 — the newest patch on Valheim’s official news feed. Nothing in 1.0.21 reverses the drop-logic changes from 1.0.20; where it touches trophies at all, it adds a requirement rather than removing one.
All eight lines of the notes, and who each one is for
The 1.0.20 notes are eight bullets with no headings, published identically on Steam and on valheim.com. Here is the full list, with the consequence each line carries.
| Line in the notes | What it changes | Who notices |
|---|---|---|
| Trophy drop chance increased by monster star level | The harder variant of a creature pays out a trophy more often | Anyone farming trophies for decor, for the Ballista, or for The Trophy Collector |
| Pseudo-random drop logic no longer reset between sessions | The rare-drop counter survives a logout | Anyone hunting a low-probability drop across several evenings |
| Fixed a possible exploit to Forge of Potential | A second pass on the endgame upgrade station | Players working the idol upgrade path |
| Cheated flag reset on all items and build pieces from previous versions | Gear wrongly stamped at launch is flagged clean again | Everyone who played 1.0 early and found items marked cheated |
| Cheat Sword and Cheat Sledge now counted as cheated in specific cases | Closes a hole in the same flag | Achievement hunters on shared worlds |
| Dedicated server no longer runs uncapped frame rate when client v-sync is on, same computer | Stops a self-hosted server burning CPU it cannot use | Server operators |
| Sheathed weapon attachment points adjusted | Cosmetic | Everyone, for about ten seconds |
| Xbox One and Xbox Series S/X settings now save between sessions | Configuration persists | Xbox players who rebuilt their settings every login |
Two bullets are gameplay, four are bug fixes, one is cosmetic and one is platform-specific. In the order they matter to a returning player, that is the rest of this piece.
Trophy drops now scale with star level
The note reads, in full: “Trophy drop chance is now increased by star level of monsters.” It publishes no multiplier, no base chance and no list of which creatures were worst affected — so treat any specific percentage quoted for this patch as somebody’s reconstruction rather than Iron Gate’s number.
What the sentence does establish is the direction of the old behaviour. A chance that is now increased by star level was previously not increased by it, so the harder variant of a monster paid out at close to the base rate. Iron Gate’s framing — “you haven’t been getting as many trophies as you should from your kills” — treats the old rate as an error rather than a balance opinion.
Trophies are not decoration-only in 1.0, which is why the rate got a patch. The post closes on the promise of “bear rugs”, and the Ballista had already been widened in 1.0.14 to “accept all new trophies (All Deep North enemies + Bjorn + Vile)” — so the drop rate feeds a defensive structure as well as a wall. Then 1.0.21 adds “Troll Trophy as requirement to The Trophy Collector achievement”, converting a bad drop rate into a completion barrier for anyone who never got one. Supply was the bottleneck, and Iron Gate has now worked both ends of it: supply in 1.0.20, demand in 1.0.21.
The pseudo-random reset was a fairness bug, not a rate bug
The second bullet is the more interesting one technically: “Pseudo-random drop logic will no longer be reset between player sessions to give a more fair distribution for rare drops.”
A pseudo-random distribution makes low-probability drops feel less streaky. The game tracks how long it has been since the last success and raises the chance on each attempt, so a rare drop arrives inside a predictable window instead of clustering on one unlucky evening and then vanishing for a week. The counter is the mechanism. If it lived only in memory, every logout wiped it — and the player who plays an hour a night was permanently stuck at the bottom of the ramp, never reaching the improved attempt one long session would have handed them. “Fair distribution” is therefore not press language; it is a description of what persisting the counter does, which is to stop session length from being the variable that decides whether a rare drop is reachable.
The note does not say how many attempts the ramp needs, or whether the counter is tracked per item, per creature or globally, and no primary source states it. The direction of travel does hold: a nightly player now accumulates progress at the same rate as a marathon player, which was not true before 15 October.
The cheated flag took four weeks, and crossplay is why
This is the section worth reading twice if you bounced off 1.0 in September.
Under the 1.0 achievement rules, a character or world that has used devcommands is flagged, spawned items are marked as cheated, and a clean character who picks one up enters a temporary cheat state that blocks achievement progress until every cheated item is dropped. The 1.0 FAQ sets that out in full, and adds that “characters that have used cheats before 1.0 will also be marked in this way.”
The bug was that the flag landed on things it should never have touched — items obtained legitimately. The repair took two fixes, a promise and a reset:
- 1.0.14, 17 September. Two lines in the same patch. First: “Fix for player characters sometimes mistakenly being marked as temporary cheaters, leading to items dropped by monsters they kill being incorrectly marked as having a cheated origin.” Then: “Cheated stackable items no longer stack with regular items, preventing uncheated stacks from being ‘corrupted’ into a cheated state.”
- 1.0.15, 18 September. No flag fix — a promise, and a partial rollback of the stacking rule: “For those of you who have run into the issue of incorrectly having items marked as cheated: We have a planned fix for this, but as it’s a fix that has to be released simultaneously on all platforms as to not break crossplay, it will come in an upcoming patch.” Its own notes restored stacking for one case: “Items affected by dev commands will no longer be marked for characters which have enabled the dev bypass command and naming has been updated and items can now stack together again.”
- 1.0.20, 15 October. “Reset the cheated flag on all items and build pieces from previous versions, to undo the damage done by a bug in the initial 1.0 release that marked some validly obtained items as cheated.”
That “upcoming patch” was 27 days out, and the reason for the wait is the interesting part. A fix that changes how items are flagged has to land on every platform at once, or a crossplay session has clients disagreeing about whether the sword in a shared chest is legitimate. Iron Gate repeats that constraint in nearly every post in this stretch — 1.0.16, 1.0.17 and 1.0.21 all carry a version of “due to some internal restrictions, the patch will require a few days to get uploaded to all platforms.”
Per the 1.0 FAQ, Valheim now sells on Steam for Windows, Linux and Mac, the Mac App Store, the Humble store, the Microsoft Store, Xbox One, Xbox Series X|S, PlayStation 5 and Switch 2. Eight storefronts with separate certification queues is how a one-line flag reset becomes a four-week project.
The same patch also closed the other half of the flag: “Fixed bug that caused Cheat Sword and Cheat Sledge to not be considered cheated in specific cases.” A reset that clears false positives is only safe if the true positives still register, which is why the two bullets sit next to each other.
The one patch where crossplay actually broke
Every other post in this run pairs its platform warning with reassurance that “crossplay will still remain functional, so you can keep playing with your friends regardless of what platform you’re on.” 1.0.17 says it, and so does 1.0.21.
1.0.20 does not. Its note reads: “There is a small delay with Mac App Store for this patch, which means that crossplay will not work between Mac App Store players and players on other platforms until it has caught up. As soon as the patch is out on that platform, crossplay should work for everyone again.”
So the status for this patch is the inverse of the usual one: the drop changes and the flag reset reached Steam, Xbox and the rest on 15 October, while Mac App Store players were cut off from crossplay until their build caught up. If you are the Mac App Store player in a mixed group, the question is not whether 1.0.20 is out — it is whether your client has caught up, and only your launcher can answer that.
A dedicated server has no reason to run uncapped
“Fixed dedicated server running at uncapped frame rate if v-sync was enabled in client on the same computer, wasting massive amounts of CPU time.”
The qualifier “on the same computer” is the whole bug. A dedicated server has no window to synchronise to and nobody watching its output, so a frame cap means nothing to it — yet when client and server shared one machine and v-sync was on, it did not idle: it ran uncapped, spinning a render loop for a game nobody was looking at and taking the CPU the client needed. Self-hosted servers on the family desktop are exactly the configuration this targets.
The Forge of Potential needed two passes
1.0.20 says only “Fixed a possible exploit to Forge of Potential”. The context is a September fix: the 1.0.12 notes, Steam-only at the time, carry the line “Using the Forge of Potential no longer unlocks recipes that should not be unlocked”. Two patches, five weeks apart, on the same feature — which reads as an incomplete first fix rather than a regression.
Iron Gate has not described the exploit, the station’s full recipe list or which recipes were affected, so guessing would be inventing detail. What the notes do show is an endgame crafting layer being hardened across the same stretch: 1.0.21 still works on the Frost Foundry, fixing the crafter credit recorded when it “is network-owned by another player”. Following the Deep North progression route, the practical reading is that the upgrade station was never a shortcut around the mould-and-cast chain.
Where the build stands on 1.0.21
1.0.21 landed on 28 October 2026 with 15 bug fixes and 18 tweaks, by my count of the published list. It does not revisit the trophy rate except to attach one trophy to an achievement, and it fixes the bug that had tied “Mighty Halls, Comfort is King, The Homesteader, The Architect, and The Survivor” to the current difficulty level.
Seven patch posts in seven weeks, in order:
| Date | Patch | What it actually touched |
|---|---|---|
| 11 September 2026 | Hotfix 1.0.10 / 1.0.12 | Deep North heavy armour repairable, punching and snow, Forge of Potential recipe unlock, item-stand durability, achievement opt-in command |
| 17 September 2026 | 1.0.14 | Keybinds and accessibility, tessellation GPUGPU. Graphics Processing Unit — the chip that renders the game's visuals; the main driver of framerate and image quality. cost, characters wrongly marked as temporary cheaters, achievements unlocking repeatedly |
| 18 September 2026 | 1.0.15 | Terrain duplication and performance loss, armour mould drop chance, cheated-flag fix promised for all platforms |
| 25 September 2026 | 1.0.16 | Terrain reverting after unload, raid spawn counts, three achievement fixes |
| 6 October 2026 | 1.0.17 | World-save chunk bug that could erase objects, invalid item types on PlayStation 5 |
| 15 October 2026 | 1.0.20 | Trophy scaling, pseudo-random persistence, cheated-flag reset, Forge of Potential exploit, server CPU, Xbox settings |
| 28 October 2026 | 1.0.21 | Achievement difficulty ties, Kall Fimbulbringer tuning, Troll Trophy added to an achievement, Nord Greatsword multi-hit |
Two things stand out. The shape of it: of seven posts, only two — 1.0.14 and 1.0.21 — are broad, and the rest are narrow and targeted. And the drift in subject matter. September was terrain, saves and crashes; October was achievements and drops. The launch damage was structural; what is being fixed now is the layer players touch every session. Iron Gate has said the work continues — the September dev post promised “more content updates coming” without naming them.
If you are starting now
Patch status does not change the answer to “should I start a fresh 1.0 world”. The 1.0 FAQ still recommends starting over rather than taking an old save north, and the achievement tracker only counts statistics from the moment you installed 1.0 — so a returning character arrives with a clean slate either way. For what the release contained, the 1.0 launch breakdown is the starting point.
What the patch history changes is one piece of conventional wisdom. Trophies were a decoration problem; since 1.0.20 they are a rate you can plan around, and since 1.0.21 one of them is an achievement requirement. Hunt starred spawns deliberately, and do not log out mid-hunt assuming your accumulated luck resets — as of 1.0.20, the counter goes with you.
Next read
- Valheim 1.0: Deep North, 40+ Weapons, September 2026 — the launch-day read on the biome, plus the engine upgrade behind it.
- Valheim 1.0 Deep North Guide: New Biome Progression — the mould, cast and Malicious Blood chain in order.
- Survival-Craft: The Five Axes That Split the Genre — where Valheim’s patch rhythm sits against the rest of the field.
- 7 Days to Die V3.3.0: Backpacks and Horde Base Design — how a peer survival title tunes its own drop rates after launch.