Quick Answer
"Build 42" is a family of patches, not one thing — and the official anchors are: 42.20 reshaped the map (surface area doubled, 1,400 new unique buildings, 20,000 new tiles, seven towns reworked) and 42.21 went Stable on 2026-09-28 (zombie duplication fixes, loadstring/loadstream Lua methods re-enabled after the security investigation). Before following any Build 42 advice: name the exact patch and branch, back up saves and server profiles (42.20.4 saves 'should not be affected' by 42.21, but back up manually anyway), and recheck every mod's live Workshop page after each update.
Table of Contents
Version-family triage
Build 42 advice is only usable once the exact patch is named. The official records anchor the family: 42.20 reshaped the map; 42.21 went Stable on 2026-09-28.
| Ask | Check against | Keep this note |
|---|---|---|
| Which patch does this advice target? | The dated official post | Stable or unstable plus the exact number |
| Does the route or town still exist as described? | The 42.20 rework list for named towns | A pre-42.20 screenshot is not evidence |
| Did the mod survive the last patch? | The live Workshop item | Last update and author statement, as reported |
| Is the server aligned with clients? | Branch and build on every side | 42.21 Stable announced 2026-09-28; both sides match |
| Can the save be recovered? | A dated backup made before the first load | Keep the pre-update copy until the new branch is understood |
The two patches that matter, on the record
Every Build 42 question eventually lands on one of these two updates. The numbers are from the official posts — carry them into your version notes.
| Patch | What the official record says | What it changes for you |
|---|---|---|
| 42.20 — the map patch | Surface area doubled versus Build 41; 1,400 new unique buildings and 20,000 new tiles (35,000 total); Riverside, West Point, Rosewood, Fallas Lake, Muldraugh, Ekron, and Dixie reworked or polished | Map knowledge and route guides older than this patch are hypotheses; inter-town trips became vehicle commitments; most classic map-mod reasons moved into the base game |
| 42.21 — the stability patch | Went Stable 2026-09-28; worst zombie duplication issues in multiplayer and zombie disappearance after chunk re-entry addressed (some instances remained for a later update); XXL tree cutaway behavior changed for players in vehicles (work described as in progress); loadstring and loadstream Lua methods re-enabled after the security investigation that disabled them in 42.20.4 | Multiplayer desync complaints may predate this patch; mod Lua that used loadstring works again; existing 42.20.4 saves should not be affected — back up manually before testing anyway |
Reading Build 42 advice without getting burned
Every piece of Build 42 content — guides, videos, mod pages, forum posts — carries a hidden version stamp. The two official anchors give you the stamp to compare against.
Map and route content divides cleanly at 42.20: the patch doubled the surface area and reworked seven towns, so anything published before it describes a world that measurably changed. Town guides, base-location videos, and 'best route' posts older than 42.20 aren't wrong — they're about a different map. The check takes five seconds: find the date or version mention, place it before or after 42.20, and weight the advice accordingly.
Server and mod content divides at 42.21: multiplayer zombie-duplication fixes landed, the loadstring and loadstream Lua methods came back, and the patch-day reports (a launch failure traced to one mod, a 127-mod symptom pile) show the mod ecosystem taking damage at the boundary. Mod advice from the 42.20.4 era — especially 'this mod is broken' or 'this workaround is required' verdicts — may be stale in either direction, because the update both fixed things and broke things.
The version-family triage table turns those two boundaries into a habit: name the exact patch before applying the advice, back up before acting on it, and keep the note of what you verified. The habit is boring, which is the point — 'should be fine' is the official wording for saves across 42.21, and the manual backup recommendation in the same sentence is the part that's actually yours to do.
Reference data
Build 42 is a version family. These records anchor the site to dated official changes instead of a generic patch label.
| Release | What changed | What it means for you |
|---|---|---|
| 42.20 map | Map surface doubled; 1,400 buildings and 20,000 tiles added | Old map routes need review |
| 42.20 named places | Riverside, West Point, Rosewood, Fallas Lake, Muldraugh, Ekron, and Dixie listed for rework | Town guides need version labels |
| 42.21 Stable | Officially announced on 2026-09-28 | Stable branch is the current site boundary |
| Compatibility | Mods and server branches must be checked against the exact patch | Build 42 is not one frozen state |
FAQ
What changed in Build 42?
Two anchors. 42.20 reshaped the map: surface area doubled versus Build 41, 1,400 new unique buildings, 20,000 new tiles (35,000 total), and seven towns reworked or polished — Riverside, West Point, Rosewood, Fallas Lake, Muldraugh, Ekron, and Dixie. 42.21 went Stable on 2026-09-28 with multiplayer zombie-duplication fixes and the loadstring/loadstream Lua methods re-enabled.
Is Build 42 the same as Build 42.21?
No — 'Build 42' is a family of patches. Advice that just says 'Build 42' without a patch number and branch (Stable or Unstable) can't be applied: a 42.15-era route guide and a 42.21 server-config note live in different worlds. Name the exact patch before following anything.
Will updating to Build 42.21 break my save?
The official patch notes say existing Build 42.20.4 saves should not be affected — and still recommend manually backing up before testing on the new branch. That's the standing pattern for every patch: official 'should be fine' plus your own dated copy equals a testable update.
Did Build 42 change the towns?
Yes — seven on the official 42.20 list: Riverside, West Point, Rosewood, Fallas Lake, Muldraugh, Ekron, and Dixie received major rework or polishing. Any street-level knowledge from Build 41 for those towns is unreliable, and the community beginner guide explicitly warns against relying on old map knowledge.