Every numbered BG3 patch replays the same forum day: "Patch 7 broke my mods", "Patch 8 broke my mods", a wave of load-order autopsies, and a quieter group asking the more interesting question — how do I just not take the patch until my hundred-hour campaign is finished? That's the heart of BG3 version discipline: mid-campaign stability. A heavily modded honour-mode run wants zero variables changed until the credits roll. Add the usual suspects — mod stacks pinned to a patch, co-op groups who must match versions and mods, and modders testing against older builds — and you have steady demand the community answered with a dedicated wiki tutorial. No anti-cheat anywhere in this story; it's all single-player and co-op.

01One Larian folder to guard

Old and new builds share this folder Everything lives in %LocalAppData%\Larian Studios\Baldur's Gate 3\ — saves, player profiles, mod settings. The modding wiki's sternest warning is that downloaded old builds use this same folder, so a version mismatch can cost real data: copy the whole directory before running anything old. Two extra BG3-specific cautions: saves from a newer patch generally refuse to load on an older one ("incompatible version" is this game's standard sad screen), and Larian's own cross-save sync is a second cloud beyond Steam's — make sure neither is pushing newer saves at your pinned build.

02Larian's rollback branches

Larian handles patch days better than most studios: alongside major patches they've published stay-behind branches in Steam's Betas tab — when Patch 7 landed, a branch let players remain on (or return to) Patch 6 precisely so mid-campaign runs and unupdated mods could finish in peace. Check Properties → Betas first, every time; if your target patch is sitting in the dropdown, that's the whole tutorial, and switching back later is picking "None". The names vary per patch and branches for older eras come and go — which is exactly the gap the rest of this page covers. (Patch 7 also shipped the in-game mod manager, whose multiplayer verification screen can upgrade and downgrade managed mods to match a host — official infrastructure quietly admitting version-matching matters.)

03The depot recipe

For patches the branch list doesn't carry, the BG3 Modding Community Wiki documents the depot route (their title says it plainly: legally obtaining old builds — ownership required, nothing bypassed). It teaches the method rather than a frozen table, and so will we: find your patch's release date in the patch notes history, take the matching manifest from SteamDB's list for depot 1086941 (the main Windows depot; macOS lives separately under app 1086940), and run:

> .\DepotDownloader.exe -app 1086940 -depot 1086941 -manifest <manifest-id> \
    -username you -remember-password -dir .\bg3-pinned

Budget a serious download — BG3 is a 100+ GB game, so a pinned era is a real commitment of disk space. A community manifest list for old patches existed on Nexus but stopped being maintained after Patch 7 — a small object lesson in why this site teaches date-matching instead of mirroring tables: method outlives lists.

04The Steam-closed launch

Here's BG3's quirk, and it's the inverse of most games on this site: the wiki's instruction for old builds is to launch the executable (bin\bg3.exe or bg3_dx11.exe in the downloaded folder) with Steam fully exited — an open Steam client tends to interpose and push you toward the current version. Most of our guides say "keep Steam running"; this one says quit it first. If you'd rather pin your main install in place instead of running a side folder, the standard pair works as everywhere: updates to "only when I launch" plus read-only appmanifest_1086940.acf.

05Script Extender eras

The mod stack follows the same era law as Skyrim's and Cyberpunk's, with BG3's specific anatomy: Norbyte's Script Extender sits under half the interesting mods and tracks the game binary tightly — its releases are versioned on GitHub, and a pinned game wants the extender release from the same era, not today's. Above it, mod versions from Nexus's old-files tabs, assembled with your mod manager of choice against the pinned install. The discipline is the series standard: game, extender, mods — all from one patch's world. Co-op raises the bar once more: everyone matches everything, which is precisely the chore the official mod manager's verification screen was built to reduce.

06Status in 2026

BG3's whole catalog is young — 2023 onward — which keeps it on the friendly side of manifest availability, and Larian's branch habit means the most-wanted rollbacks are often live branches that don't depend on manifest goodwill at all. The forces to respect are the usual two: each new patch ages the others, and branches are published at Larian's pleasure, not yours. For the campaign you actually care about, the play is the one this whole series keeps arriving at: decide your era at campaign start, pin it, archive the folder — and patch between campaigns, not during them.