DayZ map and mission files

Coordinates for dynamic events. This is where many event spawn points are placed on the map.

Explains coordinate fields used by mission placement files.

Vehicle spawning is split across multiple files. `events.xml` controls population, `cfgeventspawns.xml` controls coordinates, and `cfgspawnabletypes.xml` controls parts/cargo.

Fresh spawn and player spawn point definitions for the mission.

Animal and infected territory definitions. Territory files decide where AI families can spawn and patrol.

Animal territory placement. Controls where wildlife can spawn and which animal families are used.

Defines dynamic event behavior such as vehicle spawns, infected groups, animals, wrecks and other event-driven objects.

Optional custom dynamic event definitions for server-added vehicles, objects, AI groups or map events.

Defines where infected and animals can spawn, how many can occupy zones, and which AI families appear there.

Optional JSON object spawner files can place custom map objects, bases, trader props or event objects through `cfggameplay.json`.

Spawn bubbles define areas where new players can spawn, often grouped by coastal, inland or custom spawn logic.

Controls how spawn areas avoid invalid terrain, water, steep slopes or blocked positions.

Explains what determines which parts a spawned car has and which parts can spawn separately as loot.

Use the Mission Map Editor for coordinate-based mission files through a visual workspace.

AI agent configuration for animals and infected. It defines AI families, spawn groups and behavior references used by territory files.

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

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

Bear-specific territory file on missions that split bear zones from general animal territories.

Main infected territory placement file. Defines where infected can appear and how dense each zone is.

Temporary server startup workflow for generating a fresh mapgrouppos file from placed proxy data. Add the export command to mission init, start the server, wait for generation, then remove the command before normal play.

World positions for cluster prototypes. It places reusable loot clusters at concrete map coordinates.

Prototype data for loot clusters when a map uses clustered economy placement. It groups local loot points into reusable cluster definitions.

World placement of loot groups/buildings. It links building classnames to concrete map coordinates.

Custom world placement file for additional loot groups or custom buildings when supported by the mission.

Loot proxy definitions for buildings and map objects. It tells the economy what categories and loot points a building can contain.

Controls how complete or broken vehicles are when they spawn.

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

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

Complete multi-file workflow for adding or tuning car spawns through the central economy.

Defines grouped spawn compositions for dynamic events. Used when one event should spawn several objects together as a layout.

Underground trigger zones used by bunker or underground areas to change environment behavior.

Weather controller for clouds, fog, rain, wind, overcast transitions and storm behavior.

Workflow for custom mapped areas made in DayZ Editor and loaded on a server through DayZ Editor Loader. DayZ Editor is used offline to build and export edits; Editor Loader reads the exported edit files on server start.

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

Wolf-specific territory file on missions that separate predator zones from generic animal territories.

Explains spacing controls that prevent events from spawning too close to players, other events or unsafe positions.