PAYDAY 2: legacy builds

PAYDAY 2 is where most people — me included — learn this workflow, and there's a reason. The game shipped over 230 updates across a decade. Each one could break BLT mods, rebalance a build you'd perfected, or remove a mechanic a speedrun category depended on. And then came Update 237, which bolted Epic Online Services into the game for crossplay — the moment that turned "downgrading PAYDAY 2" from a niche trick into a small industry. The community responded with manifest spreadsheets covering every update back to release, an automated downgrader.bat on ModWorkshop, and more forum guides than any other game on Steam.

You don't need the batch file. The manual process is four steps, you'll understand what each one does, and when something breaks you'll know where. If you've never downgraded anything before, skim the universal guide first — this page assumes its basics and adds what's PAYDAY-specific.

01First: save your saves

02Picking a target build

The three numbers: AppID 218620, the Windows content depot 218621, and a manifest ID per update. The community keeps the update→manifest mapping better than I ever could — the modding wiki and the long-running Steam guides maintain spreadsheets covering updates from launch through the Epic integration, and SteamDB's manifest page for depot 218621 has the raw chronological list.

That said, one target accounts for most of the traffic to this page:

Match the manifest to your goal precisely — BLT mod loaders are version-sensitive (more in section 05), and a speedrun category that says U24 means U24, not "somewhere around there".

03Downloading the build

One command (PAYDAY 2 is friendly this way — for most legacy purposes the single Windows content depot is all you need):

You must own PAYDAY 2 on the account you log in with — depot keys are license-checked, no exceptions. Expect roughly a full game install's worth of download (legacy builds are smaller than the modern ~80 GB monster, one of their underrated charms). If you don't have the tool yet, installation takes two minutes; old guides telling you to run it via dotnet DepotDownloader.dll are describing the framework build — the normal release zip needs no .NET at all.

04Launching it — the steam_appid.txt trick

Here's where PAYDAY 2 differs from the generic recipe. You have two options, and I prefer the second:

Option A — replace the Steam install. Back up steamapps/common/PAYDAY 2, copy the downloaded build over it, set updates to "only when I launch", launch through Steam. Works, but Steam will eventually try to drag you back to the present.

Option B — run it standalone, next to the modern install. The community's better idea: keep the legacy build in its own folder and launch the exe directly. PAYDAY 2 needs Steam running and needs to know its own AppID when launched this way, so:

1. In the downloaded build's folder, create a text file named steam_appid.txt containing exactly 218620.
2. Make sure Steam is running (your account, owning the game).
3. Launch payday2_win32_release.exe straight from the folder.

The game finds Steam through the appid file, you get working ownership checks and friends — and Steam's updater never touches the folder, because as far as the library is concerned this install doesn't exist. Modern and legacy versions live side by side; speedrunners keep three or four of these folders around.

05Mods on legacy builds

Half the reason anyone is here. The crucial fact: the BLT mod loader is version-matched. Modern SuperBLT works on the pre-Epic build and most of the later legacy range — drop the DLL into the game folder, launch, accept the base-mod download, restart. But the further back you go, the older the loader you need: early updates predate SuperBLT entirely and want classic BLT. The ModWorkshop wiki's legacy modding section maintains the loader-to-update mapping; check it before assuming your usual mods folder will transplant.

Also keep mods folder per version — a mods/ directory full of current-version hooks pointed at a U24 build is a crash generator, not a time machine.

06Playing with other people

PAYDAY 2's peer-to-peer lobbies need matching versions — you'll only see and join lobbies on your exact build, which in practice means coordinating with friends or with the legacy-version communities that organize around specific updates (pre-Epic players are easy to find; U24 crews exist but you'll be scheduling, not matchmaking). Versions mismatched by even a point release won't connect. And the usual disclaimer applies less harshly here than for most games — PAYDAY 2 isn't VAC-secured — but Overkill's own anti-cheat and plain courtesy still say: keep experimental setups in friends-only lobbies.

07If the manifest is dead

The honest section. PAYDAY 2's deep manifest history is exactly the kind of content affected by Valve's manifest restrictions — a build from the spreadsheet may answer with "No manifest request code was returned" and a 401. When that happens to you: it's not your command, not your account being banned, and not fixable client-side. Check whether the build you want survives in any beta branch (Properties → Betas in Steam; the game has carried various branches over the years), try a logged-in account rather than anonymous if you weren't already, and check the status page for the current weather. If U236.1 is your target, good news as of this writing: it's the most-requested legacy manifest on Steam and the community notices within hours when it breaks — search any recent PAYDAY 2 downgrade thread before assuming the worst.

And the broader lesson PAYDAY 2 taught everyone in January 2025: if a legacy build matters to your crew, archive it while its manifest still answers. A 30 GB folder on an external drive outlives any policy change.