Recommended Free Tools
When Project Zomboid says a server mod downloaded but the feature, item or map is missing, the download usually is not the failure. The common causes are a Build 41/Build 42 mismatch, putting Steam Workshop numbers in the wrong configuration field, editing an inactive server profile, missing dependencies, client/server list differences, or treating a map like an ordinary gameplay mod. Stop the server, back up its profile and save, verify the branch and active profile, then test a clean server and add compatible mods in small batches while reading the first startup error.
Godlike.Host offers hosted Project Zomboid servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What “downloaded but not active” means
A dedicated server performs at least two separate jobs. First, it downloads Workshop items so the files exist on the machine. Second, it loads the internal mod identifiers from the selected server profile in a defined order. A successful download proves only that the first job completed. If the load list is empty, uses the wrong identifier, points to another profile, or fails a dependency check, the server can contain every file while running as an unmodded world.
As an Amazon Associate I earn from qualifying purchases.
Clients perform a similar check when they join. Each player must have the same compatible content and dependencies. A player can therefore see a mod in a Workshop download queue and still be rejected, desynchronized, or admitted without the intended feature if the server’s active list differs from the player’s list.
First checks: branch, build and profile
Match the game branch and exact build
Build 41 and Build 42 are separate compatibility targets by default. A mod made for an older branch may download normally but fail to load, produce Lua errors, or leave its features absent on a newer branch. Compare the branch and exact build shown by both the host and every client before changing a configuration file. Do not assume that a Workshop page updated for one branch supports the other; read the author’s current compatibility note.
#1 Best Overall
- UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
- COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
- ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
- INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
- SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?
- Record the server branch (for example, the selected beta branch) and full build number.
- Record the client branch and full build number on every affected computer.
- Check the mod’s stated branch, required game version and update date.
- Make the branch decision before troubleshooting load order; a correctly ordered incompatible mod still will not work.
The available configuration guidance was published or updated in September 2026 and discusses Build 42 server setup. Branch labels and mod requirements can change, so recheck the current game and author notes when applying these steps later.
Identify the profile the server actually launches
Project Zomboid can have several server profiles. The file you edit must be the one selected by the launch profile or by the -servername value. Editing a similarly named INI while the server launches another profile produces no visible change and often looks like a broken mod.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Stop the server cleanly. Do not edit a live profile while the process is running.
- Write down the launch command, panel profile name, or
-servernamevalue. - Open the matching server INI and any related settings file in the server’s
Zomboid/Serverdata directory. - Save a copy of the original profile and the world data before changing entries.
- After saving, restart the server and inspect the startup log for the profile name and mod-loading messages.
If the log shows a different profile than the one you edited, stop again and correct the launch selection before investigating individual mods.
WorkshopItems and Mods are different fields
Use numeric Workshop IDs for downloads
WorkshopItems= identifies Steam Workshop items by their numeric IDs. It is a download list, not a list of display names. Use the delimiter and formatting generated by the active launcher or profile: installations commonly use comma-separated or semicolon-separated values, and the correct syntax depends on the tool producing the file.
WorkshopItems=1234567890;2345678901The numbers above are only a formatting example, not real mod recommendations. Copy the exact numeric IDs shown in each author’s Workshop URL or the launcher output. Do not substitute a mod’s title, creator name or folder name.
Use internal IDs to activate and order mods
Mods= contains the internal identifiers defined by the mod and controls the order in which those identifiers load. These IDs are often different from the Workshop item’s number and from the name displayed in the Steam client.
Mods=FrameworkInternalID;ContentInternalIDOne Workshop item can contain multiple internal Mod IDs. Consequently, a one-to-one comparison between the Workshop list and the Mods list is not reliable: one download number may require two or more internal entries, or a collection may contain several independent mods.
| Configuration element | What it contains | What failure looks like |
|---|---|---|
WorkshopItems= |
Numeric Steam Workshop item IDs used to download files | Required files are not found on the server, or the download never completes |
Mods= |
Internal Mod IDs used to activate content and define load order | Files are present but the mod never activates, or it loads in the wrong order |
| Map entries | Map identifiers and the world configuration required by the map | Map downloads but does not appear, gives a wrong spawn, or prevents world startup |
| Dependencies | Framework, library and prerequisite IDs required by another mod | Lua errors, missing classes, partial features or an immediate load failure |
After editing, compare the saved file—not just a control panel’s visual list—with the values printed in the startup log. This catches panels that overwrite manual changes during a restart.
Build a client/server parity checklist
Compare the server and each player’s setup in separate categories. A player may have a matching Workshop number but still be missing an internal ID, a dependency, or a map entry.
| Check | Compare | Typical symptom |
|---|---|---|
| Branch and build | Client and server branch plus exact build | Immediate mismatch, crash, rejected join or incompatible-mod message |
| Workshop items | Numeric IDs and successful downloads | Required mod not found, missing files or content absent |
| Internal mods | Every Mod ID and its dependency order | Downloaded mod never activates or loads incorrectly |
| Maps | Map identifiers and world setup | Map missing, wrong spawn or map startup failure |
| Dependencies | Required frameworks and libraries, with compatible versions | Lua errors, missing classes or only part of a feature working |
| Client parity | Each player’s enabled list and downloaded versions | Desync, kick, checksum error or missing-file error |
Keep a plain-text incident record containing the exact error, timestamp, server and client builds, active profile name and last known working lists. This prevents a later change from hiding the first failure and gives every player one authoritative list to compare.
Load order, dependencies and conflicts
Load prerequisites before dependants
Put frameworks and explicit dependencies before the mods that use them, following the author’s Workshop instructions. A content mod can be downloaded correctly yet fail during initialization when its library has not loaded. If an author supplies a required order, use that order rather than guessing from alphabetical names.
- List the prerequisite framework or library in
WorkshopItems=. - Add its internal Mod ID to
Mods=before the dependent content ID. - Restart and confirm that the prerequisite initializes without errors.
- Add the dependent mod and test again before adding another batch.
Understand overwrite conflicts
Two mods that change the same Lua table, script, item definition or asset can overwrite one another. The later-loaded change may replace the earlier one, so one feature appears to vanish even though both entries are present. Reordering helps only when the authors document a compatible order; otherwise, choose one conflicting mod or contact its author with the exact error and list.
Do not “fix” a conflict by repeatedly shuffling a large list. First reduce the server to the smallest failing pair, test each mod alone, and then apply the documented order if one exists.
Map mods need a separate procedure
A map has two distinct requirements: its files must download, and the world must be configured to use its map identifiers. Download success alone does not add a new area to an already-created world.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteVerify the map identifiers
Read the map author’s installation instructions for the exact map ID, required map libraries and any order relative to the base map. Enter the identifiers in the map section generated by the active server profile; do not replace an identifier with the Workshop number or a display title.
Configure the world at the right time
Some map setups must be present when a world is created or when its map configuration is first generated. If you add a map after the save already exists, the server may continue using the old world layout. A wrong spawn point can also indicate that the map entry is valid but the world setup is incomplete.
- Back up the existing save before changing map entries.
- Confirm the map’s required identifiers and documented order.
- For a test, create a separate world with only the base map and the target map.
- Join at a known location and check the map area before restoring other content mods.
Do not keep loading a valuable save after a map mod reports errors that could alter map or container data. Restore the backup if the first failing test indicates save damage.
Safe isolation workflow
Isolation is faster than changing five variables at once. The sequence below preserves a recovery path and identifies the first failing component.
- Capture the incident. Save the exact error text, timestamp, builds, active profile and current WorkshopItems, Mods and map entries.
- Stop and back up. Stop the server, copy the matching profile under
Zomboid/Server, and back up the world and related Zomboid data. - Verify the launch target. Confirm the branch, build, profile name and
-servernamevalue. - Prove the base server works. Temporarily remove mod entries, start an unmodded server and have a client join. If this fails, repair the base installation or branch before reintroducing mods.
- Restore a known-good list. Put back numeric Workshop IDs and internal Mod IDs from the last working copy, checking each pair rather than copying display names.
- Add prerequisites first. Enable only required frameworks and libraries, restart, and read the startup log.
- Add a small content batch. Add one or a few related mods, restart, and test a fresh character or test world where appropriate.
- Test maps separately. Use a backed-up or disposable world while checking map identifiers and spawn behavior.
- Stop at the first failure. Leave the failing batch disabled, record the first fatal or exact error, and inspect the authors’ compatibility and dependency notes.
- Restore cautiously. If a mod may have changed map or container data, restore the pre-test backup instead of continuing to load the affected save.
Reading startup logs effectively
The first fatal or specific initialization error is usually more useful than the final cascade of “mod failed” messages. A missing class can cause dozens of later errors; fixing the prerequisite often removes all of them.
- Search around the timestamp of the restart, not an old session.
- Record the first named Mod ID, dependency or map identifier.
- Distinguish download warnings from load failures: a download warning points to Workshop access or an ID, while a Lua or class error points to compatibility, dependency or order.
- Check that the log names the profile you edited.
- After each change, compare the new first error with the previous record instead of judging success only by whether the server reaches the lobby.
Common symptoms and targeted fixes
The server downloads everything but no mod appears
Check that Mods= contains internal IDs, that the file belongs to the active profile, and that the server was restarted after saving. A Workshop-only list explains this exact symptom.
A player is rejected or receives a checksum error
Compare that player’s branch, exact build, Workshop downloads, internal IDs, dependencies and versions with the server. Remove stale or incompatible client files only according to the game’s normal Workshop process, then reconnect using the authoritative list.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A mod loads alone but fails in a collection
Test each member separately, then add the documented framework and dependency order. The first pair that fails together identifies a conflict; repeated reordering without author guidance is unlikely to create compatibility.
A map is absent or the spawn is wrong
Verify map identifiers and the world configuration, then test on a new or disposable world. A successful Workshop download does not retrofit an existing save’s map layout.
Changes disappear after restart
Confirm the launch profile and inspect the file after the panel or launcher starts the server. An automated profile generator may be restoring its own values; edit the generator’s fields or disable the overwrite behavior rather than repeatedly changing the generated file.
When managed hosting changes the troubleshooting work
A managed dedicated-server service can reduce routine work when it provides Workshop-ID fields, profile selection, scheduled restarts and backups. It does not remove compatibility requirements: you still need matching client builds, internal Mod IDs, dependencies and map setup. Before moving a world, verify that the service exposes the actual server profile, preserves backups and lets you read startup logs. Treat any hosting migration as a backup-and-restore operation, not as a mod fix by itself.
Free tools Windows power users keep installed
One-click scans. No signup required.
Final pre-launch checklist
- Client and server use the same branch and exact build.
- The launch command or
-servernameselects the profile you edited. - The server is stopped, the profile is backed up, and the save has a restore point.
WorkshopItems=contains numeric Workshop IDs in the syntax generated by the active tool.Mods=contains internal IDs, not names or Workshop numbers.- Frameworks and dependencies precede the mods that require them.
- Map identifiers and world setup match the author’s instructions.
- Every client has the same compatible list and required downloads.
- An unmodded server was tested before the mod batches were restored.
- The first failing batch is isolated and its startup error is recorded.
Project Zomboid’s server-mod problem is usually a configuration mismatch rather than a failed download. Separating download IDs from load IDs, validating the active profile, treating maps as world configuration, and adding compatible mods in controlled batches turns an opaque “not working” report into a specific item to correct.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
