Stellaris & Paradox: the shelf behind the account gate

A Paradox grand strategy campaign is a long-haul commitment — a Stellaris galaxy or an EU4 world spans hundreds of hours across many sessions — and these games update on a relentless cadence of major patches with astronomical codenames (Stellaris 3.7.4 "Canis Minor", and onward), each one reshaping balance and breaking the mod ecosystem beneath it. That ecosystem is enormous: total-conversion mods like Gigastructures are practically their own games, and a 200-hour save built on a stack of them does not survive a patch gracefully. So the version question recurs across the whole catalog — Stellaris, Europa Universalis IV, Crusader Kings III, Hearts of Iron IV all share the same launcher, the same Workshop logic, and the same answer. This page uses Stellaris (app 281990) as the worked example; the method transfers to its siblings unchanged.

01The shelf behind the account gate

Here's the mechanism unique to Paradox in this whole series. The version branches exist in Steam's Betas tab — but for the older builds, the opt-in codes aren't printed in Steam; they live in your Paradox account. The flow:

1. Log in at accounts.paradoxplaza.com/games and link your Steam account so it sees your games.
2. On the game, find "Access earlier versions" and click Show — it reveals the beta code for each historical build.
3. In Steam: game Properties → Betas, paste the code, and Steam switches you to that version.

It's a two-system handshake — Paradox account hands you the key, Steam opens the door — and it's why "just use the Betas dropdown" advice for these games is half the story. The mistake I made first was assuming the dropdown was the whole shelf; the older codes only showed up once I logged into the Paradox account side. The upside is a genuinely deep shelf, often reaching back years of patches, curated by a publisher with a long habit of providing it. The catch is the one in every official-shelf story: Paradox decides which versions stay on that page, and very old ones get pruned — which is the seam the depot route covers.

02Multiplayer is a checksum

Paradox multiplayer enforces version-matching through a checksum — a short code (like e728) that fingerprints the exact game state, and players whose checksums differ cannot play together, full stop. Two facts about it are worth knowing precisely, because they're unintuitive:

• DLC does not affect the checksum — and in multiplayer only the host's DLC is active for everyone. So a group can play even if members own different DLC; the host's set is what's in play.
• Mods do affect the checksum. Every player needs the same game version and the same mods to get a matching checksum — which is why a coordinated group pins both together.

This is the cleanest version-matching rule in the series — not "same patch, roughly," but a literal hash everyone must share. And it gives a concrete reason to use a fixed version branch for a modded multiplayer campaign: a pinned build produces an unchanging checksum that keeps working with the mods made for it, instead of drifting every time Steam pushes an update.

03Mods and the playset

04Where DepotDownloader fits

The account-gated branches are the primary path; the tool covers two seams they leave. Side-by-side: a branch swaps your single install, but grand-strategy players often want the pinned modded campaign beside a current install for the new content — pull a version into its own folder instead:

Fallback: when a version is old enough that Paradox has dropped it from the "Access earlier versions" page, the depot history still has it — date-match the patch against SteamDB's app 281990 depots and pull it directly, no account code required. I'm not hardcoding a manifest: these games carry their content across one or more depots that shift over their long lives, so read the right one off SteamDB for your target patch. Owning the game is still required either way — DepotDownloader checks the same license Steam does. (Saves and the launcher config live under Documents\Paradox Interactive\Stellaris\; back it up before version moves like everything else.)

05Status in 2026

Paradox grand strategy sits near the top of this series' good half. The official shelf is deep and publisher-curated; multiplayer's checksum rule makes version discipline unambiguous rather than guesswork; and an active modding culture documents version pinning as routine. The honest caveats are specific to the model: the deep shelf is gated behind a Paradox account and pruned at the publisher's discretion, and the Workshop erases mod history on its own clock. So the move for a campaign or a modded multiplayer group you care about is the series' standard, with a Paradox accent: pin the version (account code or depot), save and localize the mod playset, and archive the set together — because the checksum that binds your galaxy is only as durable as the files you keep yourself. If it were my campaign, I'd pull the pinned build into its own folder, zip it with the matching playset, and not trust the account page to still list that version a year out.