Project Zomboid's Build 42.22.2 reached Stable on November 9, 2026, but some modded servers stopped working after updating. If your Project Zomboid server won't load its mods, don't reinstall everything immediately. The cause may be an outdated mod, a version mismatch, or a configuration error.

Here's how to find the problem without putting your saved world at unnecessary risk.

Why Did Project Zomboid Mods Break After Build 42.22?

The Indie Stone warned that some modded saves may not work after the update. Changes to the game's files can make mods built for 42.21 incompatible with 42.22. Java-based mods are especially vulnerable because changes to Project Zomboid's underlying Java code can cause startup crashes; these mods aren't officially supported.

Missing dependencies, incorrect IDs, and load-order conflicts can also prevent Project Zomboid Build 42 server mods from loading, even if the mods themselves are up to date.

Back Up Your Modded Save Before Changing Anything

Make a copy of your world and settings before changing mods or game branches. On a self-hosted Windows server:

  1. In the dedicated server's console, enter save and press Enter. When saving finishes, enter quit and wait for the server to shut down.
  2. Press Windows + R, type %USERPROFILE%\Zomboid, and press Enter.
  3. Open Saves\Multiplayer and copy your server's save folder somewhere outside the active server directory.
  4. Return to the Zomboid folder and copy its Server folder to preserve your configuration files.

Keep both copies somewhere safe, preferably on another drive. A backup made before upgrading is particularly valuable because a world converted to a newer build may not work on an older one.

Check That Your Game And Server Use The Same Build

In Steam, right-click Project Zomboid, open Properties, and select Game Versions & Betas to check which branch your game uses. Then start your dedicated server and look for its version in the console.

If the server is still on 42.21 while your game has updated to 42.22.2, stop it and update the dedicated server through SteamCMD. After logging in and setting the correct server installation directory, enter:

app_update 380870 validate

Wait for SteamCMD to finish, then restart your server. A Project Zomboid server version mismatch can block connections even when the mods are correctly configured.

Check Which Mods Support Build 42.22

Visit the Steam Workshop pages for your installed mods. Check recent updates, required dependencies, and reports of problems with Build 42.22. Start with framework mods and large overhauls, as other mods may rely on them.

If you still can't identify the problem, temporarily disable mods and test them in small groups rather than removing everything at once.

How To Disable Mods On A Self-Hosted Server

  1. In the server console, enter save, then quit, and wait until it closes.
  2. Press Windows + R, open %USERPROFILE%\Zomboid\Server, and use Notepad to open your server's .ini file (usually servertest.ini).
  3. Find Mods= and remove the Mod IDs you want to test. Leave the other IDs separated by semicolons.
  4. Press Ctrl + S to save, restart the server, and check whether the error disappears. Add mods back in small groups, restarting between tests.

You can leave their Workshop IDs in WorkshopItems= while testing; this keeps the files downloaded without enabling those mods. Test on a copy of your world if mods add items, buildings, or map content. Java-based mods installed outside the normal Workshop configuration may also require temporarily moving their files out of the installation.

Check Workshop IDs, Mod IDs And Dependencies

In your .ini file, WorkshopItems= contains numeric Steam Workshop IDs used to download content, while Mods= lists the internal Mod IDs enabled on the server. One Workshop item can contain several Mod IDs, so the two lists won't always match one-to-one.

Check the Workshop descriptions for the correct IDs, required dependencies, and load-order instructions. Save any changes and restart the server; console errors mentioning missing mods or Lua failures can help identify what still needs attention.

Can You Return To Project Zomboid Build 42.21?

Yes. The developers provided a temporary 42.21 branch for players whose mods weren't ready for 42.22. On Windows, open Steam, right-click Project Zomboid, select Properties > Game Versions & Betas, choose 42.21, and allow the download to finish. Your dedicated server and players must also use a compatible branch.

How To Change The Branch With Pine Hosting

In our game panel, open Startup and set Steam Beta Branch to 42.21. Then reinstall the server from Settings using Delete All Files And Reinstall so the selected branch is installed.

Create a complete backup before doing this: deleting all files removes the existing server data. A world already converted to 42.22 may not work on 42.21, so switching versions does not guarantee your old save or mods will load.

How Dedicated Hosting Makes Project Zomboid Mod Management Easier

With Project Zomboid hosting from a provider such as Pine Hosting, you can test mods without repeatedly editing .ini files. In our Workshop page, select More Info beside an installed mod to enable or disable it; Uninstall is available separately when you want to remove it.

The Mods tab also lets you change load order by dragging mods into position. You can check console errors, restart the server, and create backups from the same panel, making it easier to isolate an incompatible mod after an update.

Keep Your Project Zomboid Server Updated With Pine Hosting

Most post-update mod issues come down to compatibility, missing dependencies, or mismatched game versions. Back up your world first, then test changes one at a time so you know which fix worked.

With our Project Zomboid server hosting, you can manage Workshop mods, toggle them on or off, and adjust their load order through our panel. Backups, file access, DDoS protection, and support are available to make server maintenance easier as new builds arrive.