Cities: Skylines: no shelf, only the door

Cities: Skylines is held together by mods — not cosmetic ones, but load-bearing tools (Traffic Manager, the network and node editors, Harmony underneath them) that a serious city is literally built on top of. Every major patch and DLC — Plazas & Promenades was the notorious one, when a chunk of the catalog moved to a new Harmony and broke at once — strands part of that ecosystem, and a 300-hour city built against the old mods doesn't care that the new patch is technically better. Two more currents feed the demand: the original game outlived its own sequel's troubled launch and became, again, the version many players mean by "Cities: Skylines"; and the no-overwrite save habit means people guard old cities carefully. The need is ordinary; the game's answer to it is what's unusual.

01The shelf that isn't there

This is the section every other recent guide didn't have to write. Players have asked Paradox for version branches the way other Paradox titles (EU4, Stellaris and friends) provide them — and the answer, per the community discussions, was that they can't offer past versions through the beta tab for this game. So there is no 1.16 entry in a dropdown, no labeled "for incompatible mods" branch like ETS2's, no full archive like Factorio's. The knowledge of how to roll back lives scattered across community guides — some of which Steam has even hidden — precisely because there's no sanctioned channel for it. That's not a knock on using old versions; it's the reason a tool like this exists. When the developer doesn't keep the shelf, the depot history is the shelf, and you're the curator.

02The depot route — the only door

The mechanics are the familiar ones, with extra weight because there's no fallback. Cities: Skylines is app 255710, its main content depot 255711. The reliable method is date-matching: find the patch your mods last worked on — the community broken-mod spreadsheet is the canonical reference for which patch broke what — then take the manifest of that date from SteamDB's depot 255711 and pull it:

You'll see a specific manifest ID passed around in old guides as the rollback target. Treat circulated IDs with mild caution: they point at whatever version their author needed, on whatever date, and they go stale as patches accumulate. The mistake I made first was trusting a circulated ID from a forum post; it pulled a build a patch off from what my mods needed. The date-matching method above always tells you the right one for your mods, which is the number that actually matters. The depot route also reaches what the Steam console can't, and lands each version in its own -dir folder instead of the shared content folder that the console method makes you clear by hand.

03Install and stop the updates

1. Copy the downloaded build over steamapps\common\Cities_Skylines (or keep it in its own folder and launch Cities.exe from there to leave your current install intact).
2. Stop Steam pulling you forward: Properties → Updates → "Only update this game when I launch it", plus the read-only appmanifest_255710.acf trick from the Skyrim guide. With no branch to fall back to, an accidental update here is more annoying than usual to undo — this step is doing real work.
3. Guard the city: saves live in %LOCALAPPDATA%\Colossal Order\Cities_Skylines\Saves\ and load forward only. Work on a copy of any city you care about — Save As a new name — so a future version can never convert your original beyond an old build's reach. Want a clean vanilla run while you sort versions? The -noWorkshop launch option boots the game without Workshop content.

04The Workshop trap, again

Pinning the game without pinning the mods solves nothing — and Cities: Skylines mods are Steam Workshop items, which means the RimWorld trap applies in full: Workshop auto-updates, authors drop old-version support, and the Workshop keeps no version history, so a mod's previous release vanishes the moment it updates. For a pinned city, the defenses are the community's standard kit: unsubscribe and grab local copies of the critical mods while their compatible versions still exist, lean on the broken-mod spreadsheet to know exactly which versions you need, and keep the whole set together. The game's old build will be downloadable from the depot next year; today's version of a mod that breaks tomorrow will not. As always with this game, the burden the developer didn't take up falls to you — so take it up deliberately.

05Status in 2026

Cities: Skylines lands on the cautionary end of this series' spectrum, and usefully so — it's the clearest example of why the depot route matters. There's no official shelf to lean on, the rollback know-how is scattered and sometimes suppressed, and the Workshop erases mod history on its own schedule. What you do have is the depot history itself, sitting under the usual manifest weather like every game's, plus a tool that reads it. So the conclusion is the whole site's thesis at its most literal: when nobody is keeping the version your city needs, you keep it — the build in a folder, the mods copied local, the city saved as its own file. The games with tidy shelves are lucky. This one is why the tool exists. If it were my install, I'd grab the local mod copies the same afternoon I pin the build — every time I've put that off, a mod updated out from under me before I came back to it.