Build 42 mods not showing or loading?

Name the failure before changing files

There are three different jobs hidden inside “my mod is not showing.”

1. Workshop download: you subscribed, but no mod files arrived.
2. Mod discovery: files exist, but the Build 42 mod list does not show the item.
3. Save activation: the mod is visible globally, but an existing world still loads without it.

Start at the earliest failed step. Build 42 also has an official Mod Manager with search, dependencies, incompatibility information, load order and presets. Use that screen to tell “not installed” from “installed but disabled”; do not start by editing a save.

The developer has warned that Build 41 saves and mods are not compatible with Build 42. Treat a B41 tutorial as background, not as proof that its file layout or mod package will load in B42.

Workshop item is missing from the list

1. Open the Workshop page and confirm that Steam says you are subscribed. Leave Steam open long enough for the download to finish.
2. Restart the game only after the download has completed, then search the in-game Mod Manager by the item name or ID.
3. If the item still is not present, check the Workshop content tree under <SteamLibrary>\steamapps\workshop\content\108600\<WorkshopID>. The numeric folder is a diagnostic check, not a folder to copy into the game directory.
4. If the subscription is present but the folder never arrives, try Steam’s Settings → Downloads → Clear Download Cache as a reversible download troubleshooting step. A January 2025 player case reports that this unstuck that player’s Workshop downloads; it is not a universal mod repair.

If the item appears but is marked incompatible or has missing dependencies, read those warnings first. Do not force-enable it just because the Workshop page is visible.

Local mod: do not reuse the old B41 root layout

A local mod is a separate path from Workshop content. In a Build 42 support case, the author found that the mod was invisible until it used a versioned folder and a sibling common directory. The reported shape was:

Zomboid/mods/YourModName/
├─ 42/
│  ├─ mod.info
│  ├─ poster.png
│  └─ media/
└─ common/

The common folder may be empty in the Steam support example. Another Indie Stone support reply specifically calls out putting mod.info inside 42 and using a lower-case media directory. These are structure checks from support cases, not permission to copy a B41 package wholesale. Check the mod author’s current B42 package and exact build if the folders disagree.

↑ Back to contents

The mod exists, but the old save does not use it

For an existing save, a Steam support reply says to use Load rather than Continue, open the save’s Mods button, and enable the subscribed mod for that world. This is different from enabling a mod in the global list. Follow the displayed dependency and load-order warnings, then make a backup before opening the world.

If the mod is not in the save’s picker at all, go back to the Workshop/local-path checks. Do not remove the save, rename its files, or paste B41 files into it to make the list appear.

When to stop and collect evidence

If a cleanly downloaded, current-build package is still absent, record the game branch, Workshop ID or local folder tree, whether the mod appears in the global manager, and whether the problem is new or existing saves. Then capture console.txt immediately after reproducing the issue and use the official support channels. A missing entry can be a version or package problem even when the log has no obvious red line; this page does not promise to repair an incompatible mod.