DayZ FriendConsole focused management
en
Server Files

Server Files

Published 10/29/2026Updated 10/29/2026

Which DayZ server files can you edit? Browse practical XML and JSON guides for loot, events, messages, gameplay, effect areas and mission loading.

Looking for DayZ console bot setup guides?

See our feature pages for DayZ auto ban, and DayZ economy bot.

Server Files

These are the files that shape a vanilla DayZ server: loot, events, spawn positions, gameplay settings, server messages and map-specific behaviour.

The useful way to read them is by the job you want to do. types.xml controls what the Central Economy knows about an item. events.xml describes event populations. cfgeventspawns.xml supplies fixed event positions. cfggameplay.json exposes gameplay switches and map-specific settings. messages.xml controls scheduled messages shown to players.

Start with the file you need

  • types — quantities, lifetime, category, usage, value/tier and tags for CE-managed items.
  • events.xml — event populations for animals, infected, vehicles and special events.
  • cfgeventspawns.xml — fixed event positions, rotations and event zones.
  • cfgspawnabletypes.xml — starting damage, attachments and cargo for spawned entities.
  • cfgeffectarea.json — named effect areas such as static contaminated zones.
  • cfggameplay.json — supported player, base-building, map, vehicle and world settings.
  • Messages.xml — welcome messages, repeating notices, connect messages and shutdown countdowns.
  • Nasdara sandstorms — the SandstormData settings in cfggameplay.json and what the supplied source proves about them.
  • Nasdara bunker broadcasts — bunker code timing, active bunker count and the broadcast window.
  • cfgeconomycore.xml — CE roots and supported external CE files.
  • init.c on console servers — why a custom mission script is different from an editable XML or JSON file.

A few rules worth remembering

Always keep the XML or JSON structure valid, use the exact classnames already present in the game build, and validate a changed file before uploading it. A valid XML file can still fail in-game if it refers to an unsupported classname or an unsupported loader.

On console, “editable” means the host exposes that mission file. It does not mean that a mission file can add new script classes, engine code or mod functionality.

Pick the right file before you edit

The most common server-file mistake is changing a file that describes the wrong part of the system. Use this order when troubleshooting:

1. Does the classname exist? Check the item, vehicle or object in the supplied database first. 2. Is the system enabled? Check active, enable, or the relevant gameplay switch. 3. Is there a position or compatible spawn point? Events need cfgeventspawns.xml; loot items need matching building points and filters. 4. Does the spawned entity need a loadout? Add its supported attachments and cargo in cfgspawnabletypes.xml. 5. Is the file actually registered and in the right folder? Check cfgeconomycore.xml and the mission path.

Changing the number in types.xml will not create a new vehicle event. Adding a position to cfgeventspawns.xml will not make an inactive event run. Adding an attachment to cfgspawnabletypes.xml will not create a slot that the entity does not have.

A reliable edit cycle

Make one small change, keep a copy of the working file, validate the complete XML or JSON document, upload it to the matching mission folder, restart or reload the server as required by the host, and then check the result in-game. If the change does not appear, compare the deployed file rather than assuming the editor saved the file you intended.

For a new custom CE setup, the dependency chain is usually:

cfgeconomycore.xml → registers files → events.xml defines an event → cfgeventspawns.xml supplies fixed positions → cfgspawnabletypes.xml supplies starting contents.

Loot follows a different chain:

types.xml → declares the item and its filters → map group prototypes provide compatible loot points → map group positions place those buildings in the world.

What this guide can verify

The examples in these pages come from the supplied DayZ 1.30 mission files and extracted scripts. Where the files expose a setting but the engine implementation is not included, the guide explains what can be seen in the configuration and avoids promising an undocumented result.

Source basis: supplied config/Knowledgebase/configuration, the DayZ 1.30 mission files and the audited source notes. No external wiki data is used here.

Console Bot Quick Links

Explore DayZ console-focused pages for PlayStation, Xbox and Switch 2 server owners:

Attachments

(0)
No attachments for this page yet.