Install Workshop Mods on a Project Zomboid Build 42 Server

Checks before installation

First validate a vanilla server and a complete player connection. For every mod, read its Workshop description, update date, Build 42 statement, dependencies, required order and removal instructions. Avoid Build 41-only or abandoned content, especially when it modifies maps, crafting, animals or zombie tables.

Stop the server and copy the entire Zomboid folder off the machine. An INI-only backup cannot restore map and player data. Record the server build and export the ordered mod list.

Add Workshop and mod IDs

1. Open each Workshop page and copy the numeric item ID from its URL.
2. Find the internal mod ID in the author's instructions or metadata; do not assume it matches the title.
3. Open the active profile, such as Zomboid/Server/servertest.ini.
4. Put numeric IDs in WorkshopItems and internal IDs in Mods, with compatible ordering. Preserve the format generated by your current Build 42 profile or panel: current documentation illustrates comma-separated values, while some control panels serialize the list themselves.
5. Place libraries before dependent mods, save and restart.

When a panel provides a Workshop editor, prefer it if it reliably writes both fields. Do not mix panel and manual lists without checking the resulting INI.

Validate without risking the world

Watch the first download. Workshop items should be retrieved before the world loads. Search logs for a missing item, dependency or Lua error. Connect with a clean client and let Steam download the same set, then use a test character to visit the world and exercise the feature.

For a long list, enable small batches. When an error begins, stop, preserve the logs and remove the last batch rather than deleting the save. Map and spawn mods may only affect unexplored cells, so not seeing them in an existing area does not prove the installation failed.

Update, remove and troubleshoot

Use a maintenance window: graceful stop, backup, server update, Workshop download, start and validation. If a client reports a mod-version mismatch, compare the item ID and update timestamp on server and client before changing network rules.

Never remove a live mod that adds items, vehicles, recipes or map cells without reading its removal notes. Test against a copy and keep a full restore point. A “Loading Map” hang can result from client build, missing dependencies or load order; the server-not-showing guide separates mod and network faults.

For automated Workshop handling with downloadable saves, compare Project Zomboid hosting plans.