How to Fix Project Zomboid Errors, Crashes, Issues, Lag (Build 42.19)

Errors · crashes · lag · multiplayer · save recovery · Build 42.19

Errors, crashes, lag, multiplayer disconnects, and corrupt saves are different failures. A red corner counter, a Workshop version message, a black screen on launch, and a “World Version is zero” load error need different branches. Use the triage table below, then open only the matching section.

1. Symptom triage

2. Universal first steps (every branch)

1. Close Project Zomboid and any dedicated server process so files stop writing.
2. Copy the failing save folder (and optionally the whole Zomboid directory) to a dated backup location. Leave the original in place.
3. Keep console.txt, recent files under Logs/, and logs.zip if it exists. Those files hold the console output, crash history, and mod list you need next.
4. Reproduce the problem once with the same mods and save, then quit and open the new log from that run’s first ERROR / Exception line.
5. Note: platform (Windows / macOS / Linux), single-player or multiplayer, Steam branch/build, host or client, and the first exact error line.

Full backup walkthrough: How to save and back up your game.

3. Mod Lua errors and “Error N”

The number in the corner is a count of recorded exceptions, not a single official error code dictionary. Identify which mod (or load-order conflict) produced the first stack, then disable that mod on the save.

1. Search console.txt for the first ERROR, Exception, Caused by, stack traceback, a path under a mod folder, or a Workshop numeric ID.
2. Match that clue to a folder under Steam Workshop content for Project Zomboid, or under local Zomboid/mods.
3. On the save: Load → More → Mods, disable the suspect, save the list, retest once.
4. If several mods are suspects, binary-disable half the list at a time after each full backup—do not delete the whole Workshop library first.

Step-by-step isolation and an in-browser log helper: How to find which mod causes errors.

4. Workshop item version is different

1. Confirm both sides are on the same Project Zomboid Steam branch (for example stable vs unstable) and the same approximate game build.
2. If you are a player: fully exit Steam, relaunch Steam, wait until Project Zomboid Workshop downloads finish, then rejoin once.
3. If you host or admin: restart the dedicated server (or Host session) after Workshop content has finished updating on the host machine so clients receive a consistent set.
4. Only if a single item still fails to update: unsubscribe that one item, clear its stuck download if needed, resubscribe, and confirm its Workshop folder is present under Steam’s content directory for Project Zomboid.
5. If Steam still reports files as complete while the game rejects them: use Steam’s Verify integrity of game files for Project Zomboid—not a blind wipe of user saves.

5. Error subscribing or downloading a Workshop item

• Confirm the item still exists on the Workshop and is not private/removed.
• Check free disk space and Steam download region; pause other large downloads.
• For server lists of Workshop IDs, fix the ID list in server settings rather than forcing clients to keep a deleted mod.
• Removed Workshop content that the save still lists must be disabled on that save; unsubscribing alone does not rewrite old mods.txt requirements.

6. Startup crashes and black screen

7. Connection failures, p2p errors, and ports

“Cannot connect” is not one error. Read the client and host console.txt for bind failures, timeouts, Workshop mismatches, or exceptions before changing network gear.

1. Confirm the server reached a ready state and that client and host share the same game branch/build.
2. Check the host server config for the real listen ports—do not assume defaults if you changed them. Common settings include DefaultPort (player data; join UI often starts at 16261) and UDPPort. Steam networking may also use separate Steam UDP ports set for that server.
3. For a self-hosted internet server: open/forward the ports that appear in your config on the host firewall and router (inbound to the host). Outbound-only rules on a client do not replace host listen/NAT setup.
4. If the log says a port is already in use, stop the duplicate server process or pick free ports—do not keep launching second instances.
5. Prefer a stable wired path for the host when testing. A VPN can help in rare routing cases but often adds latency or breaks P2P; do not treat it as a universal speed or connection fix.

Multiplayer log triage with bind and timeout patterns: Project Zomboid multiplayer “Code 5”: find the real error. Server option overview: Server administrator tips, Server settings.

8. Lag, freezes, and vehicle “black wall”

Record hardware, resolution, mod count, single-player vs multiplayer, and whether hitching tracks a specific area before changing memory flags.

1. Lower graphics options (lighting, water, 3D corpses, VSync experiments) and retest the same route.
2. Disable heavy map/UI/texture mods temporarily; many “lag” reports are script or streaming load, not a fixed “needs 4G heap” problem.
3. On multiplayer, dense towns plus high vehicle speed can overload chunk streaming for clients—lower server speed limits, keep convoy vehicles closer, and reduce simultaneous stream pressure.
4. Close background GPU/CPU hogs; on laptops use a high-performance power plan while testing.
5. Only after the above, consider memory settings in the next section if the log shows heap pressure or you run large mod sets with spare RAM.

9. Memory settings and OutOfMemory

1. Confirm the log shows OutOfMemory / heap errors, or that RAM is actually exhausted—not only low FPS.
2. Note total system RAM, OS usage with the game closed, resolution, and mod count.
3. On Windows, open the install folder from Steam → Manage → Browse local files. Edit the JVM / launcher config your install actually uses (JSON or batch wrapper), keep a copy of the original, and keep -Xms ≤ -Xmx.
4. Increase modestly (a few hundred MB to about 1 GB steps) and retest. Do not jump straight to “everyone needs 4G.”
5. macOS / Linux: use that platform’s launcher settings; do not apply Windows ProjectZomboid64.bat steps unchanged.

10. Players kicked for moving too fast

The server option Kick Fast Players (KickFastPlayers) kicks clients that appear to move faster than possible. The in-game tooltip still warns it may be buggy—use with caution. If legitimate players are kicked while driving or desyncing, an admin can turn it off after noting the change—but that weakens anti-speed checks, so treat it as a targeted trade-off, not a default for every server.

11. Load failures and “corrupt” saves

• Prefer rolling back to yesterday’s full folder copy over surgical file swaps.
• If a multiplayer friend has an intact copy of the same server world, restore from that world backup rather than mixing single-player and multiplayer DBs.
• Character or base migration between unrelated worlds is not a reliable recovery path.

12. Disk write errors

• Confirm the drive has free space and is not offline or write-protected.
• Exclude Project Zomboid and Steam from aggressive real-time antivirus scanning if logs show access denials.
• Follow Steam’s own disk and install troubleshooting if the client cannot write to the library folder.
• Do not delete save folders to “clear” write errors.

13. Quick checklist

1. Backup save + keep logs.
2. Reproduce once; capture the first real error line.
3. Branch by symptom (mod, Workshop, startup, network, performance, save).
4. Prefer restarts, verify files, and single-mod isolation over reinstalls and DB transplants.
5. Change memory, ports, or server anti-cheat options only with evidence from the log or measured performance.

Related guides

• Find which mod causes errors
• Multiplayer log triage (so-called Code 5)
• Save and back up your game
• Server administrator tips
• Server settings reference