Valheim's update history is a series of continents — Hearth & Home, Mistlands, Ashlands, each big drop reshaping the game — and between them, patches that reliably produce the forum season this whole guide series knows by heart: red BepInEx errors, "every mod broken", and crews unable to board their own server. The mod scene here is the Thunderstore-and-BepInEx world, where plugins track the game binary; the multiplayer is co-op survival where server and clients must match versions; and the stakes live in long-running worlds that crews have built for years. So the downgrade demand has two tempos: the urgent one (yesterday's patch broke the modpack — get us back one version) and the deep one (this world and its mods live on a specific era, keep it there). Paid game, no anti-cheat anywhere in the story.

01Worlds first

Years of building live in one folder Worlds and characters live in AppData\LocalLow\IronGate\Valheim\ — worlds_local and characters_local. Version moves are exactly when world files get hurt: a newer build can migrate world data forward, and an older build pointed at a migrated world is the classic corruption story. The one thing I won't do anymore is roll a long-lived world back without a fresh copy of these folders set aside first. Copy both folders before any switch, keep a backup per era for long-lived worlds, and turn off cloud sync while you're off the current patch — the same cloud-vs-pinned-build fight as everywhere on this site, with higher sentimental stakes.

02default_old: one step back

Iron Gate's answer to patch-day breakage is a Steam beta branch named default_old: Properties → Betas → pick it, and Steam swaps you to the stable build from immediately before the current patch. That single slot covers the most common case in this game's life — mods lag the patch by a week or two, you wait it out on the previous build, then return with "None". Two properties to respect: the branch holds only the immediately preceding version (when the next patch ships, the slot's contents change under you — it's a relative pointer, not an archive), and each switch is a full re-download. For the urgent tempo, it's the whole answer; for the deep one, read on.

03Deeper history by manifest

Anything older than one step back is depot work. Valheim's Windows build lives in depot 892972; match your era's patch date from the game's version history against SteamDB's manifest list and pull it into its own folder:

> .\DepotDownloader.exe -app 892970 -depot 892972 -manifest <manifest-id> \
    -username you -remember-password -dir .\valheim-pinned

The game is small — about a gigabyte — so era archives are effectively free. Launch valheim.exe from the folder with Steam running; for pinning your main install instead, the standard pair applies (updates "only when I launch" + read-only appmanifest_892970.acf). Honesty section, as always: Valheim's older manifests are subject to the same request-code gating as everyone's — community projects have logged 401s on old Valheim manifests — so what answers today is the part to archive today.

04Mod eras, the familiar way

If you've read the Lethal Company guide, you know this dance — same loader (BepInEx), same store (Thunderstore), same manager (r2modman), same rules: Thunderstore keeps every old version of every mod, so build a profile with era-correct releases, verify it loads, and transplant the profile's BepInEx folder into your pinned install for a self-contained modded build. Match three things to one era — game build, BepInEx pack, mod versions — and trim disabled mods before transplanting. Valheim adds one habit worth keeping: crews share era modpacks as profile codes, which makes "everyone run exactly this" a paste instead of a checklist.

05The server marches with the vikings

The dedicated server is app 896660, free and anonymous like its peers, and the operational rule is the strict kind: server and clients on the same version, or nobody sails. That cuts both ways around a patch — an updated server strands unupdated clients and vice versa — which is why pinned communities pin both halves together: the server by manifest or its own default_old step, the clients by whichever route above, mods matched on top via the shared profile. The stop-download-start rollback rhythm from the Rust guide transfers unchanged, with one local note: the server's world files are the same precious worlds_local data — back them up on the same schedule as the binary.

06Status in 2026

Valheim sits mid-spectrum on every axis this series measures. The official shelf exists but is one slot deep and self-overwriting — better than nothing, no substitute for an archive. The catalog is young enough (2021 onward) that recent manifests answer reliably, old ones already show the occasional 401, and every new patch pushes yesterday further into the weather. And the mod half lives on Thunderstore, which — unlike the Workshop that bit RimWorld's players — does keep version history, taking one worry off the table. The standing play, viking edition: when your world's era works, archive the gigabyte — the build, the profile, the worlds folder — and let the patches come when you're ready for them. If it were my crew's world, that's the night I'd spend an extra ten minutes on, every time.