DayZ server setup

Launcher-oriented map change workflow that connects UI actions to the underlying DayZ files.

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

Main server configuration. Controls public identity, slots, passwords, mission template, time, persistence and several gameplay toggles.

Explains the exact chain that decides which map/mission the server starts.

Use this tab for normal server identity and launch configuration without manually editing `serverDZ.cfg`.

The mission template in the configured `serverDZ.cfg` selects which mission folder the server loads.

High-level order of how mission files become active: server config selects the mission, scripts initialize it, and economy files load registered data.

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

Many servers and mods add custom folders under the mission for extra economy files, trader files, object spawners or mod configs.

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

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

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.

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

Complete workflow for switching the active mission map, including template, mission folder, required map mods and persistence.

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

Use backups before high-risk mission edits, wipes, map changes, mod overhauls or economy experiments.

Use this editor to change starter loadouts without manually rewriting mission script blocks.

Use the Validator before saving mission XML/JSON changes or when diagnosing broken configs.

Use this built-in searchable knowledge base to connect DayZ files, launcher actions and multi-file workflows.

Use metrics and events to understand whether a config or mod change affected runtime health.

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

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

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

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

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

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.

Recommended backup targets before editing configs, economy files, scripts or persistence.

Environment configuration used by some missions for ambient behavior, environment effects and world tuning.

Clear checklist for performing a real wipe, including DayZ storage and mod-created profile state.

Separates config files from state files so a wipe resets gameplay without destroying server setup.

Generic workflow for trader, market or economy mods whose config files live inside the mission folder.

General debugging flow after changing mission XML, JSON, scripts, economy or object spawners.

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

Core central economy folder. Contains most files that control loot, events, globals, messages and economy switches.

Environment and territory folder. Usually contains AI territory XML for infected and animals.