Guide

Project Zomboid Build 42 Multiplayer Guide: Co-op Roles, Shared Bases and Stable Sessions

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.

Project Zomboid Build 42 Multiplayer Guide: Co-op Roles, Shared Bases and Stable Sessions

At a glance

The short version

Game
Project Zomboid
Guide type
Events and Mechanics
Read time
4 min read
Last updated
Nov 8, 2026

Quick answer

Inventory transfers, container interactions, loot distribution and TimedActions now execute server-side, while anti-cheat and NetworkState work reduce old desync classes.

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.

The server config editor, Workshop settings open

Guide details

Swipe horizontally to view all columns.

Co-op problemBetter team ruleWhy 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.

A garage with cars on lifts and a workbench. Host or dedicated server? Use the built-in Host flow for a small group that plays while the host is online; use a dedicated server when the world needs independent uptime.

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.

A brick storeroom with shelves, a crate and a chair. Build a shared-base operating system: give food, medicine, crafting inputs, weapons and vehicle parts their own zones, and put a return bin at the entrance.

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.

A workshop interior with benches, tools and a forge. Roles work better than rigid classes: a vehicle lead, an infrastructure lead and a food/medical lead, while everyone keeps combat basics.

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.

The skills panel: Carpentry, Cooking and combat skills, with XP bars. Version and mod discipline: treat the server mod list as a contract, share one preset and load order, and fully restart after changes.

Troubleshooting and common mistakes

Swipe horizontally to view all columns.

ProblemFix / 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.

Crates stacked in a warehouse, the loot window open. Most co-op problems are configuration drift, not mystery bugs: compare build, required mods, preset and load order before blaming the server.

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.

The spawn-selection map, open on a town. For server-required mods, yes, all players need the same mods: keep the same workshop subscriptions and the same 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.

A wooden homestead with stacked logs, workbenches and a stone forge. Switch from Host to a dedicated server when the world needs independent uptime, remote administration, or players joining while the original host is away.
Was this helpful?Your vote is stored on this device only.

Save this guide

Sign in to save guides and sync them across devices.

Sign in