Sons of the Forest: pinning a moving target

Sons of the Forest never really stopped moving: a year of early access from February 2023, the 1.0 release in February 2024, and substantial content patches well after that — rafts and defensive walls landed in January 2025, two years past launch. Each move strands somebody. The mod scene runs on RedLoader and Thunderstore, and "redloader broke for me" threads bloom after every patch — the loader and half the catalog need updating before a modded setup works again, so modded groups routinely hold a version until the ecosystem catches up. Co-op is the other driver: host and clients must run the same build, so one friend's autoupdate strands the whole crew. And a few people just want the early-access-era game back, harder edges and all. Paid game — -username with an owning account for everything client-side.

01Saves live in LocalLow

02Date-matching and the download

No legendary version numbers here — no v49, no 1.5.97. The community pins whatever era its modpack or its crew was on, which makes the generic method the whole method: open SteamDB's patch notes for app 1326470, find the update your setup worked on, then take the manifest of matching date from depot 1326471 — the game's Windows content depot, and the only one most people need:

Launch SonsOfTheForest.exe from the downloaded folder with Steam running. If it bounces you into the current Steam version instead, that's the restart-DRM pattern — the steam_appid.txt fix from the L4D2 guide applies, with 1326470 as the contents. To pin your main Steam install instead, the usual pair: updates set to "only when I launch", plus the read-only appmanifest_1326470.acf trick.

03The Unity security caveat — read this one

In October 2025, Endnight shipped an update whose entire changelog was a Unity security fix — part of the industry-wide scramble after a vulnerability in the Unity runtime forced thousands of games to rebuild. That gives this game's version history a property most don't have: every build older than October 2025 contains a runtime with a publicly documented vulnerability. In practice the risk profile is modest for a co-op survival game — but it's real, it's documented, and it's the one caveat I won't soft-pedal: make the call knowingly — prefer post-patch builds when your modpack allows it, treat older pinned builds as you'd treat any unpatched software (trusted co-op circles, not a daily driver), and when a security update lands in any game you've pinned, consider that patch the one worth migrating for. Old versions are a preservation tool; security patches are the one category of update this site won't talk you out of.

04RedLoader and mod eras

The modded-era bookkeeping works exactly like Lethal Company's, because it's the same infrastructure: Thunderstore keeps every historical version of every mod, r2modman supports the game, and RedLoader's own releases are versioned on GitHub. So the profile-transplant pattern transfers wholesale — build a profile with era-correct mod versions, verify it loads, then copy the profile's loader folders into your pinned game folder for a standalone modded install. Match three things to one era: game build, RedLoader release, mod versions. Two out of three is how you get the crash logs.

05Co-op and the dedicated server

The dedicated server is its own free app, 2465200, and downloads anonymously like its peers. One genuine oddity: there is no native Linux server build — the official guidance for Linux hosts is to fetch the Windows server and run it under Wine, which is why every SteamCMD tutorial forces the platform type. DepotDownloader expresses that more directly:

Version rules are the strict kind: server and clients match or nobody connects, and hosting providers list version mismatch among their top troubleshooting causes after every patch. A pinned community pins its server the same way it pins clients — by manifest, updated deliberately, in step with the crew — and the Rust guide's stop-download-start rhythm applies unchanged.

06Status in 2026

Like Lethal Company, this is a young catalog — everything dates from 2023 onward, the friendliest case under current manifest weather, and pinning recent eras works routinely. The long game is the usual one: this history ages a patch at a time, and the era your group loves is one Endnight update away from being "old". Few developers do what No Man's Sky's did and archive the early eras for you, so on a young survival game like this the keeping is yours to do — if it were my crew, I'd archive the folder while it's cheap. Just pair the habit with the caveat above — in this game, knowing which old build you're preserving, relative to that security patch, is part of doing it right.