Bannerlord: campaigns outlive patches

A Bannerlord campaign is a long-term relationship — dynasties, kingdoms, a save measured in months of evenings — and the game kept evolving long past release, each version shifting balance, breaking save compatibility forward-only, and knocking over the mod stack. The result is this series' familiar pair of publics at unusual intensity: campaign protectors, who need the version they started on to stay exactly put until the dynasty concludes; and modlist runners, whose fifty-mod setups bind to a game version through a framework layer that tolerates zero drift. Both learn the same two skills: how to hold a version, and how to get one back.

01The Betas museum

TaleWorlds runs one of the most generous shelves on Steam: Properties → Betas lists nearly every historical version — the early-access e1.x line and the release-era v1.x builds alike, from 1.0 up through current, point releases included (the forums' perennial "how do I get 1.2.11 back from 1.2.12" has a dropdown answer here). For the majority of needs — finish the campaign, run the modlist where it works — selecting the version is the whole downgrade, and switching back is "None". The shelf's depth puts Bannerlord in the RimWorld/7DTD tier of developer behavior, and it deserves the same acknowledgment.

02Saves load forward only

03The stack below the stack

Bannerlord modlists stand on a foundation most players install once and forget: Harmony, ButterLib, UIExtenderEx and MCM — the "big four" framework mods that nearly everything else depends on, each of them version-locked to the game build. When a downgraded setup crashes at the launcher, the broken layer is almost always this one, not the flashy mods above it — every launcher crash that bit me on a rolled-back install traced back to one of the big four being the wrong era. The era-discipline routine, Calradia edition: game version first, then the big four in their era-correct releases (Nexus old-files tabs keep every version), then the mods — and mind the source split: Nexus files stay put; Workshop subscriptions auto-update, which is the same silent-rot trap that bites RimWorld colonies. For a pinned era, prefer Nexus downloads or local copies of Workshop folders, and check each mod page's stated game version — the community's own modding docs treat version-switching as a routine workflow, which tells you how normal this dance is here.

04Side-by-side and unlisted builds

The museum swaps your single Steam install; for parallel lives — the pinned campaign era next to a current-version experiment, or a modder testing across builds — pull a branch into its own folder:

Branch names mirror the Betas dropdown. For the rare build the museum skips, the standard date-matching route through SteamDB's app 261550 depots applies. Mind the scale — Bannerlord is a multi-tens-of-gigabytes install per era — and launch from the folder with Steam running; the game's own launcher handles the mod list per install, which keeps parallel eras' modlists from cross-contaminating.

05Status in 2026

Bannerlord sits comfortably in this series' good half: a deep official museum (live branches, immune to manifest weather), a modding culture that documents version-switching as routine, and saves whose one-way arrow is at least predictable. The fragile parts are the familiar ones — Workshop-sourced mods rot in place unless copied local, and the museum is TaleWorlds' to curate. So the archive for a campaign you love is the trio this series keeps prescribing: the save folder, the era's mods (big four included), and the version name — kept together, because the dynasty deserves to be playable when it's a memory. When a campaign of mine is worth keeping, that trio is exactly what I archive, and it has never once let me down on the return trip.