Server Config XML Format

cfgplayerspawnpoints.xml

Manages player spawn points, locations, and related settings. Essential for customizing where new and respawning players appear on the map.

Overview

The cfgplayerspawnpoints.xml file controls where players spawn on the map. It defines a list of coordinates that the server randomly selects from when a player joins for the first time or respawns after death.

This file is located in the mission folder (e.g., mpmissions/dayzOffline.chernarusplus/) alongside other CE configuration files.

XML Structure

Each spawn point is defined as a <spawn> element within a generator that targets PlayerSpawnHandler:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<playerspawnpoints>
    <generator type="PlayerSpawnHandler">
        <spawn id="0">
            <pos x="2500" z="5000" />
        </spawn>
        <spawn id="1">
            <pos x="3000" z="5200" />
        </spawn>
    </generator>
</playerspawnpoints>

Parameters

Parameter Description
idUnique numeric identifier for the spawn point
pos xX coordinate on the map (East-West position)
pos zZ coordinate on the map (North-South position)

Note: The Y coordinate (height) is not specified — the engine automatically places the player at ground level. Coordinates use the DayZ map grid system where (0,0) is the bottom-left corner.

Fresh Spawn vs Respawn

The server uses the same spawn point list for both scenarios:

  • Fresh spawn — A new player connecting for the first time is placed at a random point from this list.
  • Respawn after death — The server selects a random spawn point, attempting to avoid the player's previous spawn location when possible.
  • Respawn button — When a player uses the respawn button, the same random selection applies with a cooldown timer.

All spawn points have equal probability. To weight certain areas, add multiple spawn points in that region.

Example: Chernarus Coastal Spawns

The default Chernarus configuration spawns players along the southern and eastern coast:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<playerspawnpoints>
    <generator type="PlayerSpawnHandler">
        <!-- Kamyshovo area -->
        <spawn id="0"><pos x="12100" z="3500" /></spawn>
        <spawn id="1"><pos x="12200" z="3450" /></spawn>

        <!-- Elektrozavodsk area -->
        <spawn id="2"><pos x="10400" z="2200" /></spawn>
        <spawn id="3"><pos x="10500" z="2100" /></spawn>

        <!-- Chernogorsk area -->
        <spawn id="4"><pos x="6600" z="2500" /></spawn>
        <spawn id="5"><pos x="6700" z="2600" /></spawn>

        <!-- Solnichniy area -->
        <spawn id="6"><pos x="13400" z="6200" /></spawn>
        <spawn id="7"><pos x="13300" z="6100" /></spawn>

        <!-- Berezino area -->
        <spawn id="8"><pos x="12900" z="9800" /></spawn>
        <spawn id="9"><pos x="12800" z="9700" /></spawn>

        <!-- Svetlojarsk area -->
        <spawn id="10"><pos x="14000" z="13200" /></spawn>
    </generator>
</playerspawnpoints>

Tips

  • Use the in-game debug monitor or an online map tool (like iZurvive) to find exact coordinates.
  • Avoid spawning players inside buildings or on steep terrain — the engine handles height but not collision perfectly.
  • For PvP servers, consider spreading spawns across the entire map rather than just the coast.
  • Keep spawn IDs sequential and unique to avoid conflicts.

DZconfig Workflow

Import first

Upload your existing player spawn XML so the editor reflects the live server before you move points around.

Use map review

Check clusters against roads, towns, military areas, coastlines, and player travel routes.

Generate XML

Export after reviewing coordinates and keep the generated file with the rest of your mission config bundle.

Restart cleanly

Deploy spawn changes during a planned restart so every player receives the same updated point list.

Troubleshooting

Problem Check
Players spawn in waterCoordinates may be from another map or too close to the shoreline.
Players spawn in the same town too oftenThat area may have more spawn entries than the rest of the map.
Spawn changes do not applyConfirm the deployed file is in the active mission folder and restart the server.
Fresh spawns feel too punishingMove points away from predators, high-tier PvP routes, and dense infected zones.