Day[Z] Titan Launcher
DayZ knowledge topic

DayZ serverDZ.cfg

The current knowledge base entries that mention serverDZ.cfg and closely related server configuration values.

matches31 sourceserver
31 current knowledge base matches These cards are selected from the existing knowledge base data, with no new technical content added.
Server config / Instance root

serverDZ.cfg

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

config\serverDZ.cfg serverDZ.cfg
Existing editable values
  • hostname server name in browser.
  • password, passwordAdmin player and admin passwords.
  • maxPlayers player slot limit.
  • template selected mission, for example `dayzOffline.chernarusplus`, `dayzOffline.enoch`, or `dayzOffline.sakhal`.
Launcher workflow / Configuration

Launcher Configuration tab

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

config\serverDZ.cfg server profile state
Existing editable values
  • hostname server name shown to players.
  • map/template selected mission map and `serverDZ.cfg` mission template.
  • maxPlayers player slot count.
  • password, adminPassword access/admin password fields.
Server config / MPMissions

Mission folder and template

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

config\serverDZ.cfg mpmissions\dayzOffline.chernarusplus mpmissions\dayzOffline.enoch mpmissions\dayzOffline.sakhal
Existing editable values
  • template = "dayzOffline.chernarusplus" loads Chernarus mission folder.
  • template = "dayzOffline.enoch" loads Livonia mission folder.
  • template = "dayzOffline.sakhal" loads Sakhal mission folder. Sakhal requires the Frostline DLC.
  • mpmissions folder name must match the template string.
Server config / Server config

What determines which map loads

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

config\serverDZ.cfg mpmissions -mod= storage_*
Existing editable values
  • serverDZ.cfg template main value that selects the mission folder; launcher instances pass it via `-config=...\config\serverDZ.cfg`.
  • mpmissions folder name must match the template, for example `dayzOffline.chernarusplus`.
  • terrain mod custom maps require the terrain mod in `-mod`.
  • mission files selected folder supplies `init.c`, db XML, env XML and map placement files.
RCon and BattlEye / Profiles

BattlEye filters

BattlEye filter files control script, remote execution and object/action restrictions. Launcher-created instances normally use root `battleye` through `-BEpath`; existing servers may use `profiles\BattlEye`.

battleye\scripts.txt profiles\BattlEye\scripts.txt remoteexec.txt createvehicle.txt
Existing editable values
  • scripts.txt filters script commands and script detections.
  • remoteexec.txt filters remote execution calls.
  • createvehicle.txt filters object creation.
  • setpos.txt filters position changes.
RCon and BattlEye / Profiles

BEServer*.cfg

BattlEye server configuration. The launcher-created instance uses root `battleye` through `-BEpath`, while existing servers may keep BattlEye config under `profiles\BattlEye`.

battleye\BEServer_x64.cfg battleye\BEServer.cfg profiles\BattlEye\BEServer*.cfg
Existing editable values
  • RConPassword password used by RCon clients.
  • RConPort UDP port for RCon.
  • RestrictRCon controls RCon access restrictions when supported.
  • MaxPing optional ping limit depending on BattlEye support.
Gameplay / Mission folder

cfggameplay.json

Gameplay feature switches and server-side rules. Commonly used for stamina, base building restrictions, map/navigation settings and player behavior.

mpmissions\dayzOffline.*\cfggameplay.json
Existing editable values
  • WorldsData map and player spawn related world settings.
  • PlayerData stamina, shock, drowning and player stat behavior.
  • BaseBuildingData construction and placement restrictions.
  • UIData player-visible UI feature toggles.
Runtime files / DayZ server install

DayZ runtime addons folder

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

addons addons\*.pbo
Existing editable values
  • addons/*.pbo core server runtime data.
  • SteamCMD update normally repairs or replaces these files.
  • preflight missing_runtime_addons launcher blocks start if runtime addons are missing.
  • do not mix with mods Workshop mods belong in `@ModName\addons`, not this folder.
Runtime files / DayZ server install

DayZ runtime dta folder

Core DayZ runtime data required by the dedicated server executable.

dta dta\*.pbo
Existing editable values
  • dta/*.pbo required runtime data files.
  • preflight missing_runtime_dta launcher blocks start if these files are missing.
  • SteamCMD validate/update correct way to repair missing or damaged dta files.
RCon and BattlEye / Instance root

Instance root battleye folder

BattlEye/RCon config may live under instance root `battleye` as well as under `profiles\BattlEye` depending on setup.

battleye battleye\BEServer_x64.cfg battleye\BEServer.cfg
Existing editable values
  • BEServer_x64.cfg preferred 64-bit BattlEye server config.
  • BEServer.cfg fallback BattlEye server config.
  • RConPassword password used by launcher RCon tools.
  • RConPort UDP port for RCon.
Runtime files / Profiles

profiles crash dump files

Crash dump and crash log files created when the DayZ server process crashes.

profiles\*.mdmp profiles\crash_*.log
Existing editable values
  • *.mdmp binary crash dump for deeper crash analysis.
  • crash_*.log text crash information when generated.
  • RPT near crash time usually contains the lead-up to the crash.
  • mod update correlation compare crash time with recent mod/config changes.
Runtime files / Profiles

profiles folder

Runtime output and admin files: logs, crash clues, BattlEye configuration and server profile data.

profiles *.RPT *.ADM *.log
Existing editable values
  • BEServer*.cfg RCon password and port; the launcher-created default is under instance root `battleye`.
  • *.RPT server runtime log for errors and mod load issues.
  • *.ADM admin log when enabled.
Runtime files / Profiles

profiles folder important files

Describes the most important files and folders inside the server profile directory.

profiles\*.RPT profiles\script_*.log profiles\crash_*.log profiles\*.ADM
Existing editable values
  • *.RPT main DayZ server log. Use for startup, mod, classname and economy errors.
  • script_*.log Enforce script errors and stack traces.
  • crash_*.log crash diagnostic output.
  • *.ADM admin/player activity log when admin logging is enabled.
Runtime files / Profiles

RPT startup log

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

profiles\*.RPT
Existing editable values
  • Cannot open file missing PBO, wrong path or bad mod load order.
  • Addon requires addon missing dependency in `-mod` or `-serverMod`.
  • Unknown entity classname does not exist or mod is not loaded.
  • Script error broken mission script or mod script.
Runtime files / Profiles

script, crash and admin logs

Secondary logs for script runtime errors, crashes and admin activity.

profiles\script_*.log profiles\crash_*.log profiles\*.ADM
Existing editable values
  • script_*.log Enforce script errors and stack traces.
  • crash_*.log crash details useful when the server exits unexpectedly.
  • *.ADM admin/player action log when admin logging is enabled.
  • server_console.log console output when captured by a wrapper or launcher.
Admin workflow / Mission root

Backup before editing mission files

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

mpmissions\dayzOffline.* config\serverDZ.cfg profiles storage_1
Existing editable values
  • mission folder backup protects XML, JSON and script edits.
  • config\serverDZ.cfg backup protects ports, passwords, template and server identity.
  • storage backup protects players, bases, vehicles and loot state.
  • profiles backup preserves logs and BattlEye/RCon config.
DayZ Tools / Steam Tools

DayZ Tools: map and terrain files

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.

Terrain Builder map source files world config mpmissions
Existing editable values
  • Terrain Builder creates/edits terrain source data.
  • world config defines terrain/world settings for the map addon.
  • generated map addon packed as PBO and loaded as a client-required map mod.
  • mpmissions template server needs a mission folder matching the custom terrain.
Launcher workflow / Configuration

How to change map with the launcher

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

Configuration tab config\serverDZ.cfg mpmissions Mods tab
Existing editable values
  • Mods tab install and enable required custom terrain/map mods first.
  • Configuration tab Map select the target map/template where supported.
  • serverDZ.cfg template verify the saved mission template.
  • Files tab confirm the matching `mpmissions` folder exists.
Mods / Instance root

Mod signatures and bikeys

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

keys\*.bikey @ModName\keys\*.bikey @ModName\addons\*.bisign
Existing editable values
  • *.bikey public key copied to the DayZ server install `keys` folder used for signature verification.
  • *.bisign signature next to each client PBO in the mod `addons` folder.
  • verifySignatures `serverDZ.cfg` switch that enforces signature checks.
  • keys folder cleanup remove old keys when replacing mods with incompatible versions.
Mission structure / Mission root

mpmissions file loading order

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

config\serverDZ.cfg init.c cfgeconomycore.xml db\*.xml
Existing editable values
  • serverDZ.cfg template selects the mission folder. In launcher instances this file is normally `config\serverDZ.cfg`.
  • init.c mission startup script.
  • cfgeconomycore.xml registers economy files.
  • db XML central economy values.
Complex workflow / Server config

Workflow: change server map

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

config\serverDZ.cfg mpmissions\dayzOffline.* storage_* -mod=
Existing editable values
  • serverDZ.cfg template set the mission folder name that should load; launcher-created instances store it under `config\serverDZ.cfg`.
  • mpmissions folder ensure the matching mission folder exists.
  • -mod load required terrain/map mods for custom maps.
  • storage_* old map persistence should usually not be reused across different maps.
Complex workflow / Profiles

Workflow: troubleshoot after mission edits

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

*.RPT script_*.log db\*.xml *.json
Existing editable values
  • Validator check XML/JSON syntax first.
  • RPT look for XML load errors, unknown classnames and missing addons.
  • script_*.log check mission script stack traces.
  • selected mission folder confirm `serverDZ.cfg template` points to the folder you edited.
Complex workflow / Server config

Workflow: tune time and night cycle

Configures start time, day speed and night speed for the server.

config\serverDZ.cfg serverDZ.cfg
Existing editable values
  • serverTime fixed time, system time or configured start time.
  • serverTimeAcceleration day time speed multiplier.
  • serverNightTimeAcceleration night time speed multiplier.
  • serverTimePersistent keeps time progressing across restarts when enabled.
World environment / Mission root

cfgenvironment.xml

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

mpmissions\dayzOffline.*\cfgenvironment.xml
Existing editable values
  • temperature ambient temperature behavior when present.
  • wind wind-related environment values.
  • overrides map-specific environment overrides.
  • class names environment preset or area identifiers.
Persistence / Mission storage and profiles

Complete wipe checklist

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

storage_1 storage_* profiles config\serverDZ.cfg
Existing editable values
  • Stop server never wipe while the process is running.
  • Backup back up mission folder, storage and profiles first.
  • storage_1/storage_* delete or archive DayZ world/player/economy persistence according to wipe type.
  • profiles mod state inspect and remove mod-created save files that are not pure config.
DayZ Tools / Steam Tools

DayZ Tools: sign PBOs and create keys

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

*.biprivatekey *.bikey *.bisign keys
Existing editable values
  • private key kept by the mod author; used to sign PBOs.
  • public .bikey copied to the DayZ server install `keys` folder.
  • *.bisign signature file generated next to each signed PBO.
  • verifySignatures server config option that enforces signature checking.
Launcher instance files / Instance config

Launcher instance config folder

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

config config\serverDZ.cfg config\server-settings.json config\modlist.json
Existing editable values
  • serverDZ.cfg DayZ server config used by the selected instance.
  • server-settings.json launcher-managed structured settings that complement `serverDZ.cfg`.
  • modlist.json launcher mod list, order, enabled state and client/server assignment.
  • key-index.json tracks keys synced by the launcher.
Validation / Mission files

Mission file paths and case

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

mpmissions\dayzOffline.*\*
Existing editable values
  • template must match mission folder name.
  • objectSpawnersArr path must match the JSON file location.
  • cfgeconomycore file name must match the XML file.
  • mod folder launch argument must match actual folder.
Launcher workflow / Titan Launcher

Titan Launcher: what it can manage

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

Overview Configuration Mods Editor
Existing editable values
  • New Instance create a local DayZ server instance and prepare the mission/config workspace.
  • Start/Stop/Restart/Kill control the selected server process.
  • Configuration edit common `serverDZ.cfg` values and related server settings.
  • Mods search, add, update, purge and sync keys for Steam Workshop mods.
Persistence / Mission storage and profiles

Wipe: what to keep and what to delete

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

profiles storage_1 config\serverDZ.cfg DayZ server install\keys
Existing editable values
  • Usually keep `serverDZ.cfg`, mod folders, keys, BattlEye RCon config, launcher settings and intentional mod config files.
  • Usually delete for world wipe `storage_1/data`, vehicle/object economy persistence and map object persistence.
  • Usually delete for player wipe `players.db` or equivalent player persistence.
  • Inspect profiles mod banks, garages, territories, groups and traders may have separate state files.
Admin workflow / Server config

Workflow: ports, firewall and visibility

Connects game port, query behavior and RCon/BattlEye access so players and admin tools can reach the server.

config\serverDZ.cfg battleye\BEServer*.cfg launch arguments Windows Firewall
Existing editable values
  • server port game UDP port from launch/config.
  • steam query port server browser/query visibility depending on launch setup.
  • RConPort BattlEye RCon UDP port.
  • firewall rule allow required UDP ports.
Open full knowledge base DayZ server launcher