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.

  • Build 41 & Build 42
  • Solo & Multiplayer
  • Error Logs
  • Workshop Mods

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 problem

Error 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 problem

Mods & 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 problem

Multiplayer & 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 problem

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.

Safe Troubleshooting

Diagnose First, Fix Safely

Use the smallest reversible change that tests one likely cause at a time.

  1. Confirm Your Build

    Check whether you are using Build 41 or Build 42 before following version-specific paths or mod instructions.

  2. Match the Symptom

    Start from what the game shows instead of guessing which component failed.

  3. Save console.txt or logs.zip

    Keep the relevant log before restarting repeatedly or changing files.

  4. Try Reversible Fixes

    Test settings, dependencies, load order, or one mod at a time before removing data.

  5. 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 Log

Quick 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.

Browse All FixesStart With console.txt