Getting Started with Project Zomboid Modding

Project Zomboid modding is Workshop-first. The Indie Stone built mod support into the engine, the Workshop is the canonical channel, and most installs are subscribe-and-go. If you've modded Don't Starve Together or any other Workshop-native game, the patterns transfer directly.

This guide walks the standard install on the current Build.

Step 1 — Subscribe through Workshop

Open the Project Zomboid Workshop. Subscribe to any mod. Steam downloads it.

Most Zomboid mods are subscribe-only — no manual file management needed.

Step 2 — Enable mods for a world

In-game Mods menu (Main Menu → Mods). Two-step process:

1. Mods list — toggle subscribed mods enabled/disabled for the world you're creating.
2. Mod load order — drag to reorder. Later-loaded mods override earlier ones.

Save the configuration. When you create a new sandbox world, the active mods at creation time are remembered for that world.

Important: changing the mod list mid-save can produce undefined behaviour. Best practice is to commit to a mod list before starting a multi-hour playthrough.

Step 3 — Recommended first mods

Three solid first picks:

• More Traits — adds a substantial set of additional character traits at creation.
• True Music — improves the in-game music system with more variety and configurability.
• Common Sense — adds intuitive interactions to many game objects (e.g. dragging a corpse, smashing windows with weapons).

Subscribe via Workshop, enable in-game.

Step 4 — Sandbox mode unlocks the most mod features

Many mods only show their full effects in Sandbox mode (where you can configure rules manually). Preset modes (Apocalypse, Survivor, Builder) lock down some parameters that mods would otherwise affect.

If you find a mod isn't doing what its description says, check whether the rules it touches are sandbox-only.

Step 5 — Multiplayer

For dedicated server hosting:

1. Install mods to the server's mod folder (or subscribe via Steam Workshop if the server has Workshop integration).
2. Edit the server's servertest.ini (or equivalent) to list the active mods.
3. Restart the server.
4. Clients auto-download mods from Workshop when joining.

For in-game peer-to-peer hosting, the host's enabled mods are the server's mod set; joiners auto-download.

Step 6 — World save handling

Worlds are at %Username%/Zomboid/Saves/. Each save folder contains the mod list it was created with.

Removing a mod from an existing save:

• Cosmetic mods, UI mods: removable safely.
• Content mods (added vehicles, weapons, professions): removing leaves dangling references; the items may vanish.
• Map mods: do not remove on a save that's used the mod's added map regions; the world coordinates would be invalid.

Back up before disabling content mods.

Common gotchas

• Mod doesn't appear after subscribing. Restart Steam and Zomboid. Sometimes the Workshop sync is delayed.
• Mod enabled but no effect. Check whether the mod is sandbox-only and you're playing a preset world. Or check the mod's load order — a later mod may be overriding it.
• Build update broke a mod. Wait a few days. The Indie Stone usually gives mod authors heads-up time, but major Build transitions (40→41, 41→42) cause temporary breakage.
• Multiplayer disconnects on join. Mod-set mismatch between client and server. Compare; reconcile.
• Mod has no in-game settings page. Not every mod exposes settings. Some are pure XML/Lua tweaks with no configurability beyond enable/disable.

If you're authoring your own mod, Zomboid's Lua API is well-documented and the game's mod folder (Zomboid/mods/Examples/) contains official example mods worth studying.