Build 42 multiplayer is more server-authoritative than older Project Zomboid networking. Inventory transfers, container interactions, loot distribution and TimedActions now execute server-side, while anti-cheat and NetworkState work reduce old desync classes. For players, the practical lesson is simpler: divide jobs, standardise base storage, keep the same mods and build version, and stop treating co-op like several solo saves happening in one house.
Quick answer
For two to four friends, the in-game Host flow is enough; use a dedicated server when the world must stay available without the host client.
Split responsibilities early: one player handles vehicles, another construction/power, another medical/cooking, while everyone keeps a baseline combat role.
Every player should use the same Build 42.20.4 branch and the same server-required mod set before troubleshooting mysterious join errors.
At a glance
Swipe horizontally to view all columns.
| Co-op problem | Better team rule | Why it helps |
|---|---|---|
Everyone loots the same thing | Assign primary roles and a shared “needs” board | Reduces duplicate trips and missing essentials |
Storage becomes chaos | Zone shelves by category and label overflow | Makes server-side transfers easier to read |
One player owns every skill | Use specialist roles plus cross-training | Keeps the team functional when someone is offline |
Mods desync | Lock a shared preset and load order | Prevents file mismatch and dependency drift |
Host or dedicated server?
Use the built-in Host flow when one player is happy to own the session and the world only needs to exist while they are online. Move to a dedicated server when uptime, remote administration, larger groups or long-running community worlds matter more than convenience.
Build a shared-base operating system
Give food, medicine, crafting inputs, weapons and vehicle parts fixed zones. Keep “return bins” near the entrance so players can unload quickly, then sort during quiet periods. Shared bases fail from friction more often than from a lack of floor space.
Roles work better than rigid classes
A vehicle lead can keep Mechanics high, an infrastructure lead can handle Carpentry/Electrical, and a food lead can run Cooking/Farming. Do not turn those jobs into hard restrictions. Everyone should know basic first aid, melee spacing and emergency driving.
Version and mod discipline
Treat the server mod list as a contract. If the host changes a Workshop dependency or load order, everyone should update before the next session. Build 42’s official manager can show dependencies and incompatibilities; use presets instead of manually rebuilding a list from memory.
Troubleshooting and common mistakes
Swipe horizontally to view all columns.
| Problem | Fix / response |
|---|---|
Friend cannot join | Confirm exact Build 42.20.4 branch, server address/port and required mods first. |
Inventory feels delayed | Check server latency and load before assuming the item disappeared; actions are server-authoritative. |
Workshop mismatch | Restart after Workshop updates and verify all required dependencies are present. |
Base storage keeps collapsing | Use category zones, unload bins and a routine sort period instead of more random crates. |
FAQ
Is Build 42 multiplayer server-side now?
More of it is. The official 42.20 overview says inventory transfers, container interactions, loot distribution and TimedActions execute server-side.
Do all players need the same mods?
For server-required mods, yes. Keep the same Workshop set and load order.
When should I switch from Host to a dedicated server?
When the world needs independent uptime, remote administration or a larger long-running group.