Project Zomboid Build 42.17 Update — Patch Notes & Server Impact
Build 42.17 dropped on April 20, 2026 — the latest unstable patch in The Indie Stone's ongoing B42 development cycle. This article summarises what changed and, more importantly, what it means if you run a dedicated server.
TL;DR
- Refined sandbox-customization options.
- Continued occupation & trait rebalances (follows the major B42.16 occupation overhaul).
- Dozens of multiplayer stability fixes.
- Expanded crafting (pottery, blacksmithing, stonework, brewing) continues to mature.
- Still unstable branch — saves are not B41-compatible.
What Changed
Occupations & Traits
B42.16 rolled out a complete rebalance of nearly every starting profession with generalized skill bonuses. B42.17 adds fine-tuning on top: a few traits had their XP bonuses tweaked, and the new Tinkerer and Target Shooter traits introduced in 42.16 saw small balance passes. The renamed classics like Bushcrafter stay in place.
Sandbox Customization
Refined sandbox UI for difficulty tuning. If you've been waiting for a clean way to adjust zombie behavior + loot rates without diving into raw config files, this patch closes that loop.
Multiplayer Stability
Dozens of fixes around desync, world-state sync, and player-data persistence on dedicated servers. If your B42 community has been hitting the dreaded "stuck on getting server info" or random rollback bugs, 42.17 should help — though as with any unstable patch, expect a few new bugs in their place.
Server Impact — What Admins Need to Know
1. Save Compatibility
Critical: Saves created in earlier B42 builds (42.0–42.15) may NOT be compatible with B42.16 and later versions. Always back up your /Server/ save folder before patching.
2. Mod Compatibility
The B42 mod ecosystem is still volatile. Most mods that targeted 42.10–42.15 will NEED an update for 42.16/42.17 because of the occupation/trait restructure. Recommended workflow:
- Check each mod's Steam Workshop page for B42.17 confirmation BEFORE updating.
- If unsure, freeze your server on the previous version until critical mods catch up.
- See our PZ Mod Manager guide for managing mod sets cleanly.
3. Configuration Changes
The sandbox-config improvements in 42.17 should not break existing server configurations — values from earlier B42 builds carry forward. Verify by running a sandbox-config diff against your current settings if you're paranoid.
4. Pre-Patch Checklist
- Stop the server cleanly. Use
servermsg "Server restarting in 5 minutes"via RCON. - Snapshot the world. Either via your panel's backup tool or by archiving
/Server/. - Verify Steam Workshop mod versions. Patch unless flagged as incompatible.
- Update game files via SteamCMD.
- Test on a copy of the world before pushing to production if you have a 100+ hour campaign at risk.
- Restart server. Watch logs for first 5 minutes for unexpected errors.
Should You Update Right Now?
Three categories:
| Your situation | Recommendation |
|---|---|
| Hosting a public server, running on B42 unstable already | Update. The MP stability fixes alone are worth it. |
| Long-term private community, 100+ hours invested, on earlier B42 | Wait or test on a copy. Take a backup first. |
| Still on B41 (stable) | Do not migrate yet. Wait for the B42 stable release. See B42 stable migration guide. |
Resources
- Official Project Zomboid news blog — primary patch announcements.
- PZwiki Build 42 page — community-maintained version history.
- Our companion guides: B42 multiplayer lag optimization · "Stuck on Getting Server Info" fix · B42 dedicated server setup.
Run B42 cleanly. Host a Project Zomboid server with Supercraft — we keep the server build current and let you roll back to a prior B42 patch in one click if a new patch breaks your community.