DayZ server mods and Workshop

Use DayZ Tools key utilities to sign custom PBOs so servers can verify clients with `verifySignatures` enabled.

Explains what is inside a DayZ mod folder and which parts matter for loading, signatures and server setup.

Signature files prove that client PBOs match server-accepted keys. Public modded servers usually depend on this.

Instance-local storage for mods managed or referenced by the launcher.

DayZ has a separate Steam tool package named DayZ Tools. Server owners and modders use it to create maps, make mods, pack PBOs, sign keys, publish Workshop items and import models.

Use DayZ Tools Publisher to upload a custom mod or map to Steam Workshop so servers and players can subscribe/update it.

Server-side public keys for signed mods. Clients need matching mod signatures to join.

Mod metadata and class definitions. These files explain what classnames, weapons, items, vehicles or scripts a mod adds.

How to make modded items actually spawn: load the mod, register or merge its economy files, and ensure clients can join.

Use DayZ Tools to build your own mod from source files, configs, scripts, models or textures.

Local folder intended for server-side mods or separated server mod organization.

Use maintenance actions for update and cleanup work that admins often do manually.

Use this tab to manage Workshop mods and their server-side key workflow.

How server-managed mod economy folders are loaded without merging every mod entry into vanilla XML.

Explains what decides whether a mod must be loaded by players or only by the server.

Use DayZ Tools when creating or editing a custom terrain/map. Generated terrain/world data then needs a matching terrain mod and mission folder for the server.

Use DayZ Tools/Object Builder workflows when importing custom models, preparing geometry, materials and config class definitions.

Step-by-step knowledge for diagnosing why an item configured in `types.xml` does not appear in-game.

Controls which mods the server loads and whether clients must load them too.

Explains which mission files are needed after adding a mod, depending on what the mod contains.

Classnames used in economy files must exist in vanilla game data or loaded mods.

Steps for diagnosing script restriction, remoteexec or createvehicle kicks after installing mods or editing mission scripts.

Debugs errors where the server cannot find a classname used by loot, events, starter gear or object spawners.

Tracks `.bikey` files copied by the launcher during key sync so mod signature keys can be managed predictably.

The vanilla DayZ Dedicated Server runtime PBO folder. This is different from mod `@ModName\addons` folders.

Explains which complex tasks the current launcher can help with directly and which still require manual/mod-tool work.

Complete reasoning chain for adding a custom zombie/infected type, making it spawn, and giving it loot.

Use this tab to quickly find and open important server paths without browsing the filesystem manually.

High-level map of current launcher capabilities so admins know whether a task can be done through the UI or requires manual file work.

Adds modded vehicles correctly, including mod loading, keys, economy event setup, spawn positions and parts.

Diagnostics for vehicles, wrecks, animals, infected or custom objects configured as central economy events.

Path and filename rules that prevent hard-to-see mission load mistakes.

Common reasons custom placed objects do not appear after adding object spawner JSON files.

The launcher's source of truth for installed/enabled mods, mod order and whether each mod is client-required or server-side.

The launcher's per-instance configuration folder. It stores DayZ config plus launcher-managed state for mods and keys.

Main DayZ server runtime log. Use it to diagnose failed startup, missing mods, bad classnames, script errors and economy load problems.