Find the Error Before You Delete Anything
Fix Project Zomboid Errors & Mods
Start with the symptom, confirm your build, and work through safe fixes for crashes, error logs, broken mods, and multiplayer problems.
Start Fixing the Problem Here
Project Zomboid Errors & Mods Troubleshooting Checklist
Use these checks before opening another guide. They cover the safest first actions for launch errors, broken mods, multiplayer mismatches, and the logs that reveal what failed.
Game Will Not Launch or Keeps Crashing
Separate a damaged installation from a mod or save-specific failure before deleting any Project Zomboid data.
- Restart Steam, confirm whether you are launching Build 41 or Build 42, and retry once without changing files so you can record the exact symptom.
- Verify the installed game files in Steam, allow any missing files to download, and test a clean launch before enabling or removing Workshop content.
- Save console.txt or logs.zip from your user Zomboid folder and look for repeated exceptions near the end of the failed launch instead of treating every warning as the cause.
Mods Are Missing, Disabled, or Not Working
Most mod failures come from build support, missing dependencies, incomplete Workshop downloads, or a different configuration between solo and multiplayer.
- Open the Workshop page and confirm that the mod supports your current build, then install every dependency named by the author.
- Confirm the mod finished downloading and is enabled in the correct place; a solo Mods selection does not automatically configure a hosted or dedicated server.
- Load required libraries before dependent mods and test one suspect mod at a time so a load-order or compatibility conflict can be identified.
Multiplayer Is Stuck or the Server Rejects Files
Treat multiplayer failures as a synchronization problem first: the server and clients must agree on the game build, Workshop files, dependencies, and server configuration.
- Confirm that the host, server, and joining clients use the same Project Zomboid build before investigating individual mods.
- Compare the server mod list, Workshop IDs, dependencies, and load order, then restart the server after a controlled configuration change.
- Record whether the connection stops at initializing, getting server info, downloading mods, or loading the world, and keep the matching server and client log messages.
Protect Saves Before Advanced Fixes
A useful troubleshooting step should test one cause and be reversible. Resets and deletions belong at the end of the process, not at the beginning.
- Back up saves, server databases, and important settings from the user Zomboid folder before changing or removing persistent data.
- Do not delete the entire Zomboid folder as a universal fix; preserve logs and isolate the smallest configuration, cache, or mod set related to the symptom.
- After each change, reproduce the same action and note the result. If nothing changes, restore the previous state before testing the next likely cause.
Start With What You See
Choose Your Project Zomboid Problem
You do not need to know the cause yet. Pick the symptom that looks closest to your problem.
Startup & Crashes
- Nothing happens after pressing Play
- Black screen during startup
- Crash while loading a save or joining a game
Use this path when the game will not start, shows a black screen, or crashes while loading.
Explore this problemError Messages & Logs
- A red Error number appears
- An unexpected error occurred
- The game tells you to check console.txt
Use the visible message and console.txt to narrow down what failed before changing files.
Explore this problemMods & Workshop
- A mod is missing from the menu
- A mod is enabled but has no effect
- Dependencies or load order cause conflicts
Check installation, version support, dependencies, and load order when a mod is missing or broken.
Explore this problemMultiplayer & Servers
- The host terminates unexpectedly
- Connection is stuck initializing or getting server info
- A client file does not match the server
Follow server-specific checks for hosting failures, connection loops, and client-server file mismatches.
Explore this problemPopular Fixes
Common Problems, Direct Answers
Open the guide that matches the message or symptom you are seeing.
Unexpected Error Occurred
Build 41 & Build 42
The game stops and tells you to check console.txt.
Open this fixHow to See the Error Log
Build 41 & Build 42
Find console.txt or logs.zip and identify the useful error lines.
Open this fixBuild 42 Console.txt Errors
Build 42
Read Build 42 console errors without treating every warning as the cause.
Open this fixRed Error Counter
Build 41 & Build 42
Understand the red Error 1–4 counter and find the underlying log entry.
Open this fixHost Terminated
Build 42
Troubleshoot a hosted server that stops or reports that the host terminated.
Open this fixView All Fixes
Mods & Multiplayer
Fix the Problems That Usually Need Different Checks
Mod and server issues often look like game errors, but they need their own installation, dependency, version, and synchronization checks.
Mod Troubleshooting
Check where mods are installed, whether they loaded, and whether they support your build.
Browse Mod TroubleshootingMultiplayer Troubleshooting
Separate local game problems from hosting, server configuration, and client-server synchronization issues.
Browse Multiplayer TroubleshootingSafe Troubleshooting
Diagnose First, Fix Safely
Use the smallest reversible change that tests one likely cause at a time.
- Confirm Your Build
Check whether you are using Build 41 or Build 42 before following version-specific paths or mod instructions.
- Match the Symptom
Start from what the game shows instead of guessing which component failed.
- Save console.txt or logs.zip
Keep the relevant log before restarting repeatedly or changing files.
- Try Reversible Fixes
Test settings, dependencies, load order, or one mod at a time before removing data.
- Back Up Before Last-Resort Changes
Copy saves and important configuration before deleting, resetting, or replacing folders.
Current guides prioritize Build 42. Build 41-only steps are labeled, and paths, menus, mod structures, or server settings are separated when they differ.
Deleting the Zomboid folder, saves, databases, or Workshop data is never presented as a universal quick fix.
Learn How to Read the Error LogQuick Answers
PZ Troubleshooter FAQ
What does the red Error number mean?
It is an error counter, not a fixed error code. Open console.txt and look for the related error entry to identify the actual cause.
Where is console.txt?
It is stored in your user Zomboid folder. The error-log guide shows how to find console.txt or logs.zip and which lines are useful.
Are Build 41 mods compatible with Build 42?
Not automatically. Check the Workshop page for supported builds, required dependencies, and recent author updates before enabling a mod.
Why do mods work in solo play but not multiplayer?
The server and every client may need matching mod versions, dependencies, and server mod or Workshop settings. Treat it as a synchronization problem first.
Should I delete the Zomboid folder to fix an error?
Not as a first step. Diagnose the symptom, save the logs, try reversible fixes, and back up saves and settings before any reset or deletion.
Still Not Sure Where to Start?
Choose the closest symptom, keep your current log, and begin with the safest checks.
