Play Multiplayer With Friends | Project Zomboid Guide

Quick Answer

Most 'multiplayer is broken' problems are one unaligned layer. Align in order: branch and exact build on every side, host method chosen (in-game host, dedicated, or managed), one agreed sandbox profile (loot, zombie speed, PVP, water shutoff are world rules), and one shared mod list — on servers, WorkshopItems and Mods are separate fields and both must be enabled per item. Then the make-or-break test: one clean connection with ZERO mods. The captured 42.21 reports (a launch failure traced to one mod, a 127-mod symptom pile) are what happens when this order is skipped.

Table of Contents

Session alignment checks

Most first-session failures come from one unaligned layer, not a broken game. Check them in this order before touching mods or saves — each row says what to compare and what agreement looks like.

Order	The shared layer	Aligned when
1. Branch	Stable or unstable, in every launcher	All clients and the host read out the same branch and build number — screenshot them, don't trust memory
2. Host method	In-game host, dedicated, or managed	Everyone knows the server address and the host's real schedule — only a dedicated server stays up when the host logs off
3. World rules	One sandbox settings profile	Loot, zombie count, water shutoff month, and PvP are agreed in writing before launch night, not argued about after the first death
4. Mod set	WorkshopItems and Mods IDs, plus dependencies	Server and every client hold the same list — mods must be enabled in both the Workshop and the Mods sections to load
5. Join test	One clean connection with zero optional mods	A player joins, moves, and disconnects cleanly — only then does the campaign mod set go in

The mod-set comparison, on paper

Step four done properly: four rows per item, server column next to client column. A Steam Support response adds the field rule — server mods must be enabled in both the Workshop and Mods sections — so three passing rows can still hide the failure.

Field	What it holds	A mismatch here looks like
WorkshopItems	The numeric Workshop IDs the server downloads	The client downloads an item the server never fetched — join-time missing-file errors
Mods	The internal identifiers the game actually loads	Both sides subscribed, nobody loads it — 'the mod isn't on the server' despite the Workshop list looking right
Map	The map-folder identifiers for map mods	The client renders a world the server didn't generate — join fails or terrain disagrees
Dependencies	The items your items require	Intermittent breakage that looks like bugs — a requirement enabled on one side only fails when its code path runs

What 'shared state' actually means

The captured multiplayer reference separates shared world state, player-specific state, global sandbox rules, and Workshop/Mods alignment — four layers that fail in different ways and get fixed in different places.

Shared world state is the save: one authoritative copy on the host or server, and every disagreement about 'what happened' is a sync question, not a gameplay argument. Player-specific state is each character's skills, inventory, and position — which is why one player's broken mod can look like 'my character is glitched' while everyone else is fine. Global sandbox rules (loot, zombie speed, time, water shutoff, PVP) are decided once at world creation: they're world rules, and 'can we turn PVP off now' is a trust question wearing a settings costume.

Workshop and Mods alignment is the layer with the trap: on a server, WorkshopItems= and Mods= are separate fields, both must be enabled per item, and the restart-after-enabling clauses some mods carry apply to the server too. The Steam Support record is blunt about it — server mods must be enabled in both sections. Get the field comparison on paper (server's four rows against one client's four rows) before anyone re-subscribes anything.

The zero-mod join test interprets everything above it: if a clean default session connects and a modded one doesn't, the delta is your mod set, and the bisect method (disable half, test, halve again) finds the culprit in a handful of restarts. If the clean session also fails, you've saved the group a mod hunt — it's branch, network, or the server itself. That's why the clean join is step five and not step one: it only means something after the first four layers are known-aligned.

Reference data

These records describe the shared state a group must agree on before adding optional complexity.

Shared system	How it behaves	Your group must agree on
World state	Time, weather, and zombie distribution are shared	One host or server state
Player state	Skills, inventory, and location stay player-specific	Roles and spawn expectations
Sandbox	Loot, zombie speed, water shutoff, and PVP are server-level	One active settings profile
Mod state	Workshop items and active Mods entries must be compared	Same IDs and dependencies

FAQ

Why can't my friend join my Project Zomboid server?

One unaligned layer, most likely. Check in order: branch and exact build on both sides, the network path (a clean default session connects?), then the mod fields — WorkshopItems and Mods are separate server settings and both must be enabled per item, per a Steam Support response. One affected friend is a comparison problem (their client); a whole group is a server problem.

Can we turn PVP off mid-campaign?

It's a settings change mechanically (PVP sits among the server-level groups) but a trust question socially — the captured reference treats sandbox rules as agreed before launch for exactly that reason. Technically, world rules live in the SandboxVars layer and some changes are generational rather than retroactive; socially, a mid-campaign PVP flip is the kind of change that ends groups. Agree it up front.

Do all players need the same mods?

Yes — server and every client need the same list, and on the server side each item needs BOTH the WorkshopItems and Mods fields enabled. Compare four rows per item: WorkshopItems, Mods, Map, dependencies. The restart-after-enabling clauses some mods carry (Hug the Plushie, Belgian Malinois) apply to the server too.

What should we test in our first multiplayer session?

One clean connection with zero mods: a player joins, moves around, disconnects cleanly. That single test proves branch alignment, network path, and the host configuration — and it makes every later failure diagnosable ('the clean join worked, so it's the mod set'). Skip it and you're in 127-mod-symptom territory, where nothing is attributable.