Risk of Rain 2: the downpatch that went mainstream

When Seekers of the Storm shipped on August 27, 2024 — the first expansion built after the game changed hands from Hopoo to Gearbox — it arrived entangled with an engine update that hurt the base game: physics and timing bugs surfaced run after run, performance went strange, and the entire BepInEx mod catalog broke at once, with prominent modders announcing they wouldn't chase the new version until it stabilized. The community's response was the remarkable part: within days, downpatching instructions were pinned by moderators in the official Discord and published across the gaming press — version rollback as first-class, officially-tolerated consumer advice. Most of this site documents downgrading as a specialist's craft; this page documents the time it was simply what everyone did.

01The canonical target: Devotion

The community settled on one destination: the Devotion update — the last build before the expansion, with the stable engine and the working mod ecosystem. Its coordinates became common knowledge: depot 632361, manifest 9058106608706845920. That's the manifest I pulled and ran, and it's the one I'd point anyone to. The press guides demonstrate the Steam-console route; same command, fewer moving parts here:

Ownership required as always; the download is a complete pre-DLC game, a few gigabytes. To be explicit about what you give up: the rollback removes the expansion's content along with its problems — survivors, stages, the lot. That was precisely the trade thousands chose.

02Launching the old build

1. Standalone (recommended): in the downloaded folder, create steam_appid.txt containing 632360, keep Steam running, and launch Risk of Rain 2.exe from the folder — the same restart-DRM bypass as L4D2's, and here it's documented in the community's own guides. Your Steam install stays current alongside.
2. In-place: copy the downloaded files over steamapps\common\Risk of Rain 2, set updates to "only when I launch", and add the read-only appmanifest_632360.acf trick for insurance. Returning to current is one "Verify integrity of game files" away.
3. Co-op matches versions and mods — a Devotion lobby is Devotion players, the same crew-coordination rule as every co-op title here.

03Thunderstore eras

RoR2 modding is the BepInEx-and-Thunderstore world this series knows well, and the SotS break split it into eras visible right in the infrastructure — Thunderstore literally sections the catalog by game version. For a Devotion build, the routine is the profile-transplant pattern: an r2modman profile assembled from era-correct mod versions (Thunderstore keeps every old release), verified once, then copied into the downpatched folder for a standalone modded install. The era rule in its usual three parts: game build, BepInEx pack, mod versions — all pre-SotS, no exceptions, because the engine change is exactly the kind of boundary plugins don't survive crossing.

04The aftermath, honestly

Time did its work: Gearbox shipped repair patches through late 2024 and beyond, the worst engine bugs receded, and the mod ecosystem gradually crossed over — by now the current version is the reasonable default and the mass-downpatch moment has passed. What remains pinned is the long tail this series always finds: modpacks and runs built in the Devotion era, players who never saw a reason to leave, and the manifest above as their stable address — the same long tail of version-pinned speedrunners and modders that keeps a build like Hollow Knight's named patches in active demand (recent enough to sit on the friendly side of manifest weather — archive the folder if that's you). On my last check, June 2026, that manifest still answered cleanly, but I keep the Devotion folder zipped regardless. The episode's lesson outlived its crisis, though: when a release goes wrong enough, version rollback becomes consumer protection — and the communities that already knew how to do it, the skills this whole guide series teaches, were the ones that simply kept playing that week.