WARDENHUB

DAYZ SERVER UTILITIES / GUIDES

Server Configuration Guide

A practical reference for common DayZ server files, what they are generally used for, and a safer workflow for making changes. File access and support can differ between PC, console, game version and hosting provider.

Platform note

This guide is intentionally general. A file being documented for DayZ does not mean it is editable or supported on every game server or hosting setup. Check the files exposed by your own server panel and the documentation for your exact platform and version.

Common configuration files

serverDZ.cfg

Server identity and session settings

Commonly holds server name, passwords, player limit, mission selection and other server-level settings. Exact available options depend on the server build and host.

SERVER SETTINGS
cfggameplay.json

Gameplay configuration

Used for supported custom gameplay settings when the server is configured to use the custom gameplay file. It can also reference object-spawner JSON files in supported configurations. JSON syntax and exact paths matter.

GAMEPLAY / JSON
types.xml

Central Economy item definitions

Contains item type records and economy values such as nominal, minimum, lifetime, restock, quantity ranges and cost, with category/usage/value metadata where used.

ITEM ECONOMYOpen Types.xml Editor ↗
events.xml

Dynamic event definitions

Defines event records and their related settings. Some events also contain nested child definitions. Keep the nested structure intact when changing individual values.

DYNAMIC EVENTSOpen Events.xml Editor ↗
globals.xml

Economy-wide values

Holds global Central Economy parameters. These values can affect broad economy behaviour, so avoid changing them to solve a problem that belongs to one item or event.

ECONOMY GLOBALS
cfgeconomycore.xml

Economy file registration and structure

Commonly used to describe how economy configuration files and related data are organised or referenced. Do not copy paths from another server without checking the target folder layout.

ECONOMY STRUCTURE
cfgspawnabletypes.xml

Spawn attachments and cargo

Commonly defines attachments and cargo items that can be created with supported spawnable types. This is separate from deciding how frequently an item appears in the economy.

ATTACHMENTS / CARGO
mapgrouppos.xml / mapgroupproto.xml

World loot group data

These map-group files are associated with loot locations and group definitions. Their format and availability are version/map dependent. Treat them as map data, not as a simple item-rate setting.

MAP LOOT GROUPS

Safe change workflow

  1. Back up first.Download the original file and keep an untouched copy outside the server folder.
  2. Identify the right file.Change the narrowest setting that matches the problem. Do not edit global economy values to fix one classname.
  3. Change one thing at a time.Record what changed and why. This makes rollback and troubleshooting much easier.
  4. Validate syntax.Use the JSON/XML tools, then compare the edited file with the original. Syntax checks do not prove DayZ schema correctness.
  5. Restart and test deliberately.Use a controlled test location or condition. Allow for economy timers and restart behaviour before deciding the change failed.
  6. Keep or roll back.If the result is worse or unclear, restore the backup before making another change.
JSON Formatter ↗ XML Validator ↗ File Comparison ↗

Quick troubleshooting direction

Item does not appear

Check the classname, the matching type record, category/usage/value metadata, map loot groups and economy state. Do not assume that adding a type record creates a world spawn point.

Dynamic event does not appear

Check that the event definition is present and well-formed, then review its related child definitions and any linked configuration. Confirm the event is supported by the platform and server build.

Custom objects do not load

Check whether custom gameplay configuration is enabled, whether the referenced JSON path matches the actual folder and filename, and whether the JSON structure matches a known-working file for that server.

Server behaves differently after an edit

Compare the current file with the backup, isolate the last change, and check server logs or host diagnostics. Avoid stacking several unverified edits together.

Accuracy note

This is a general reference, not official Bohemia documentation or a complete schema catalogue. It does not guarantee that a listed file exists, is editable, or behaves the same way on every console or PC server. Use your own server's known-working files as the source of truth.