Quick Answer
Subscribing only downloads the mod — activation is a separate step per context. New game: enable in the in-game mod manager (restart first if it doesn't appear). Existing save: back up, then Load > your save > More > Choose Mods. Server: WorkshopItems= and Mods= are separate fields, and a Steam Support response says server mods must be enabled in BOTH. Two captured gotchas: Hug the Plushie and Belgian Malinois require a restart after enabling, and a subscribed mod can sit in the list unactivated while another shows up — prove installs with one visible feature before piling on more.
Table of Contents
Activation context
The same subscription can still fail at a different activation layer. Name the context before you touch files.
| Context | Confirm | If it fails, check |
|---|---|---|
| Workshop download | The item and dependencies finished downloading | Reopen the item and note the Workshop ID |
| Existing save | The mod is on for that save, not just globally | Back up and retest the save-specific flow |
| Hosted session | Host and clients share the item and dependency set | Compare the host list with one affected client |
| Dedicated server | Server Workshop items and Mods IDs agree | Compare the active profile with the client downloads |
The install flow, step by recorded step
The PZwiki flows below are version-marked 42.14.0 — the mechanics have been stable, but re-verify the menu names on 42.21. The server rows come from a March 2026 Steam Support discussion and the 42.20.0-marked dedicated-server page.
| Where you are | Do exactly this | The recorded detail that trips people |
|---|---|---|
| Subscribing (any context) | Subscribe on the Workshop page, wait for the download to finish, restart the game if the item doesn't appear, then enable it in the in-game mod manager | The restart is part of the flow, not a workaround — and a subscribed item can stay unactivated indefinitely until you enable it |
| Existing save | Back up the save first, then Load > select the save > More > Choose Mods, and enable per-save | A mod enabled globally is not automatically on for an old save — the save keeps its own selection |
| Items with restart requirements | Read the author's description for a restart clause before reporting a broken install | Hug the Plushie requires a restart after enabling; CD: Belgian Malinois requires a full restart — both will look 'not installed' until you do |
| Hosted or dedicated server | Fill in BOTH the Steam Workshop items and the Mods sections — a Steam Support response says server mods must be enabled in both | WorkshopItems= and Mods= are separate fields; enabling one half gives you a subscribed-but-inactive mod on the server |
| Proving the install | Enable exactly one visible feature and confirm it appears in-game before adding the next item | A user reported one subscribed mod appearing in the list while another didn't — visibility in the list is not proof of activation |
Dependency chains: install them whole or not at all
Most 'the game is broken after I installed a mod' reports are dependency reports. The captured sample shows what a complete chain looks like.
Three of the eight captured Build 42 mods carry hard requirements: Hug the Plushie needs Workshop item 3749026793, pz3d needs ZombieBuddy (3619862853), and CD: Belgian Malinois needs Companion Dogs 0.8.0 or newer. Each requirement is itself a mod with its own build target and its own update cycle — so subscribing the headline item alone leaves you one patch away from a broken install, and the failure surfaces as symptoms that look like game bugs: menus misbehaving, inventory errors, load failures.
The install order for a chain is: subscribe every item in the chain, let all downloads finish, restart once, then enable from the framework down. Load-order instructions from authors (Hug the Plushie says it should load after other affected mods) are part of the install, not fine-tuning — capture them from the description at subscribe time, because 'it doesn't work' six weeks later usually means the order note was never applied.
The proof step closes the install. One visible feature, tested on the right context (your actual save, not a new throwaway, if the claim you care about is save-safety), and only then the next item. The captured reports of broken 42.21 upgrades all have the same shape: many changes at once, no record of which item did it — which is a diagnosis problem created at install time.
Reference data
The save activation procedure traces to a PZwiki page marked 42.14.0. Server activation adds separate WorkshopItems, Mods, and Map fields from the PZFans reference (Build 42.19), so the 42.21 interface still needs a fresh check.
| Where you're activating | What to do | How current it is |
|---|---|---|
| Workshop | Subscribe, wait for the download, restart if the item is absent | PZwiki page marked 42.14.0 |
| Existing save | Load the save, open More, then Choose Mods | PZwiki page marked 42.14.0 |
| Hosted or dedicated server | Keep WorkshopItems, Mods, and Map as three separate fields | PZFans server reference labelled Build 42.19 |
| Backup | Back up the save before changing its mod set | Safety recommendation |
| Proof | Verify one visible mod feature before adding more | Our suggested routine — no in-house test claimed |
FAQ
Why is my subscribed mod not showing up?
Three recorded reasons: the game wasn't restarted after subscribing (the restart is part of the PZwiki flow, not a workaround); the item has a restart-after-enabling clause (Hug the Plushie and CD: Belgian Malinois both require one); or the mod is activated in the wrong context — an existing save keeps its own mod selection via Load > More > Choose Mods, and server mods need BOTH the WorkshopItems and Mods sections enabled.
How do I add mods to an existing save?
Back up the save first — that's explicit in the PZwiki flow. Then Load > select your save > More > Choose Mods, and enable the mod for that save specifically. A globally-enabled mod does not automatically apply to old saves. The flow is documented on a 42.14.0-marked page, so re-verify the menu names on 42.21.
Why do server mods need two settings?
WorkshopItems= and Mods= are separate server fields — the PZwiki dedicated-server page (42.20.0-marked) distinguishes them, and a March 2026 Steam Support response says server mods must be enabled in both the Steam Workshop and Mods sections. Enabling only one half leaves the mod subscribed-but-inactive on the server.
What does 'safe to add mid-save' actually mean?
It's the author's claim about their own scope, not a guarantee. In the captured sample, Dynamic Gear Rattling and Hug the Plushie say safe to add and remove mid-save; Heart Health Meter and Over the Shoulder say safe to add to ongoing games. The risk reference draws the class boundary: UI/QoL is lower-risk, loot and vehicle changes depend on unvisited map cells, map mods are unsupported for casual mid-save changes. Back up and test regardless.
Do I need to install a mod's dependencies separately?
Yes. Hug the Plushie requires Workshop item 3749026793, pz3d requires ZombieBuddy (3619862853), Belgian Malinois requires Companion Dogs 0.8.0+. Subscribe the whole chain, let everything download, restart once, then enable from the framework down — and capture any load-order note from the description at subscribe time.