Project Zomboid Build 42 Multiplayer: Patch Stability Guide (B42.15)
Project Zomboid's Build 42 multiplayer launched on the Unstable branch in December 2025 and has been receiving steady patches through early 2026, reaching B42.15 as of March 2026. Running a B42 MP server comes with unique challenges compared to the mature B41 stable branch: updates can break saves, mods aren't always ready between patches, and the game is still being actively balanced. This guide helps server admins navigate B42's fast-moving development cycle.
Unstable branch warning: Build 42 is exclusively on the Unstable branch. Updates can (and do) break save files without warning. Running a long-term community server on B42 requires a robust backup and communication strategy.
How to Run a B42 Dedicated Server
Installing the Unstable Branch Server
The B42 dedicated server requires opting into the Unstable beta branch via SteamCMD:
The B42 dedicated server App ID is 380870 (same as B41 — the branch selects the version). Verify you got B42 by checking the server log on first launch for a line like:
Critical: Always Validate After Updating
Between B42 patches, always run SteamCMD with the validate flag. B42 Unstable patches sometimes ship with partially corrupt files that SteamCMD skips without validation:
B42.15 Patch Highlights (March 2026)
Gameplay Balance Changes
- Trait exploit fixes — Several character creation combinations allowed stacking bonus traits far beyond intended limits. B42.15 patches the most abused combinations. If your server had players with exploited trait builds, those characters may see stat corrections on the next server restart.
- Occupation rebalance — Skill bonuses for occupations were adjusted. The Security Guard and Police Officer occupations in particular received significant passive adjustments.
- Medical system updates — The injury simulation and treatment system (one of B42's headlining features) received balance passes. Wound infection rates and splint effectiveness were adjusted.
- Firearm aim improvements — Improved target selection logic for aiming at partially obscured targets reduces instances of shots hitting walls/obstacles instead of zombies.
Technical Fixes
- Fixed interior lighting calculation errors in multi-story buildings that could cause server-side null pointer exceptions
- Fixed barricades and curtains allowing light pass-through incorrectly during night simulation
- Multiple inventory-related improvements: double-click actions, item equipping while moving
- Fixed chunk boundary desync that could cause zombies to "teleport" when crossing between loaded chunks on the server
Managing Save Files on Unstable Branch
The Save Break Risk
The most painful reality of running a B42 server is that any patch can potentially break existing saves. The Indie Stone explicitly warns that B42 Unstable is not suitable for long-term world persistence. However, many community servers run on B42 despite this — they just need a plan.
Backup Strategy for B42 Servers
Run this script before every SteamCMD update. Keep at minimum 7 days of backups — sometimes a save corruption from a bad patch isn't discovered until days later.
When a Patch Breaks Your Save
Signs your save broke after a patch:
- Server crashes within 30 seconds of startup
- Players can connect but map chunks refuse to load
- Log file shows
LuaExceptionerrors referencing save file parsing - Player character data loads but positions/inventories are wrong
Recovery options (in order of preference):
- Restore from backup — Roll back to the pre-patch save and wait for The Indie Stone to fix the compatibility issue
- Soft reset — Reset only the world map while preserving player character data (using the
/softresetadmin command) - Start fresh — Create a new world on the patched version. Announce the wipe to your community in advance when you see a high-risk patch incoming
Mod Compatibility in B42.15
Mods for B42 are distributed via the Steam Workshop using the B42-specific workshop. B41 mods are not compatible with B42 and vice versa.
Checking Mod Status
After each B42 patch, check the mod's Workshop page for:
- A pinned comment or update from the author confirming B42.15 compatibility
- Recent update date — if the mod hasn't been updated since before the patch, test it on a staging server before enabling on production
- Comments section reporting crashes — players report issues quickly
Running a Staging Server
The best practice for B42 is running two server instances: a staging server (updated immediately when patches drop) and a production server (updated 24–48 hours later once mods are confirmed working). This is easily done on a machine with enough RAM by running two server processes on different ports.
Performance Tuning for B42 Multiplayer
Recommended Server Settings (JVM)
B42's expanded world simulation (skyscrapers, animals, advanced lighting) requires more heap than B41:
ZGC over G1GC for B42: The Z Garbage Collector (ZGC), available in Java 17+, has much shorter pause times than G1GC. B42's heavier simulation means GC pauses are more impactful; ZGC reduces the stutters players notice as lag spikes during garbage collection.
Key Server Performance Settings
Communicating Patch Updates to Your Community
Transparent communication is the most important tool for running a B42 server community. Recommended Discord setup:
- #server-status channel — Pin current version, any known issues, and update ETAs
- #patch-announcements — Post when a new B42 patch drops and when you plan to apply it
- 24-hour notice policy — Announce wipes (when forced by a save-breaking patch) at least 24 hours in advance
- Patch nights — Apply patches at a consistent low-traffic time (e.g., every Thursday at 4 AM) so players know when to expect downtime
When Will B42 Leave Unstable?
As of March 2026, The Indie Stone has not announced a date for Build 42 to graduate to the stable branch. The transition typically happens when the major systems are considered feature-complete and the patch frequency drops to only bug fixes. Based on The Indie Stone's historical release cadence and the current pace of B42 patches, mid to late 2026 is a reasonable estimate, though this is speculative.
Until then, running a B42 server means accepting the tradeoff: access to the new content (animals, skyscrapers, overhauled crafting) in exchange for occasional instability.
Need a Project Zomboid server that handles B42's demanding requirements? Supercraft Project Zomboid hosting runs on high-RAM dedicated nodes optimized for B42's expanded simulation.