3 guides · Build 42.21
Servers
Match Workshop and Mod IDs, diagnose a named client/server file mismatch, and check the Java fingerprint baseline for Viewpoint multiplayer.
Friends cannot join the same modded world?
Begin with the exact failure message and the administrator’s intended mod list. Server configuration, Workshop delivery and Java running on a player’s PC are separate layers. A server entry does not install a local agent or approve a companion JAR. These guides cover mod consistency; they do not supply a full hosting, port-forwarding or RAM-sizing recipe.
Where do Workshop IDs and Mod IDs go?
Use the correct list and distinguish one Workshop item from its modules.
Follow the steps →A file does not match or is missing
Read both file paths and item IDs before changing the implicated installation.
Follow the steps →Simple Mod Check reports a different setup
Compare each client’s Java files with the administrator’s intended baseline.
Follow the steps →Before changing your setup
- Match the actual game build and required dependencies before comparing files.
- Back up the named server configuration and preserve unrelated entries.
- A Lua file mismatch and a Simple Mod Check fingerprint warning need different evidence.
All servers guides
Project Zomboid server mods: WorkshopItems vs Mod IDs
Put numeric Workshop IDs and named Mod IDs in the correct server lists, using a documented Viewpoint/QOL example and preserving other entries.
Read guide →Project Zomboid file does not match the server: read the paths first
Distinguish duplicate Mod IDs, manual copies and update mismatches from a missing file, then collect a targeted client/server comparison instead of deleting everything.
Read guide →Set up Viewpoint QOL and Simple Mod Check for a server
Separate server ini entries from each player’s Java setup, then establish a Simple Mod Check staff baseline with Enforce off.
Read guide →