Change player spawn locations on a DayZ PC server

By Niko Catarino

Updated 3 October 2026

Change fresh-player spawn locations in the active mission’s cfgplayerspawnpoints.xml. The coordinates define areas where DayZ generates suitable spawn candidates. A saved character logging back in is not a fresh-spawn test.

This procedure covers DayZ Standalone PC community servers. It requires mission-file access and a test server you can join. A spawn-selection mod can replace the vanilla behavior; check its configuration first.

Back up the correct spawn file

Read the startup configuration selected by -config, then find its mission template. Open that mission under mpmissions, stop the server and download cfgplayerspawnpoints.xml.

Save an untouched copy outside the live mission. Confirm the filename before replacing it: cfgspawnabletypes.xml controls item attachments and cargo, which is a different job. Save your mission and persistence backup before broader world changes.

If you need a reference, use Bohemia’s Chernarus mission file, or the matching mission for your map and build. That pinned Chernarus file matches the stock copy in our 1.29.163709 test installation. Compare its structure with your installed file; do not import another map’s coordinates.

Edit the fresh-player section

Bohemia’s player spawning reference distinguishes three sections. <fresh> is the relevant section for new characters here. <hop> and <travel> concern official-server transfers; editing those is not a fresh-spawn change for your community server.

Inside <fresh>, locate <generator_posbubbles>. Your file may hold named <group> elements or a flat list of <pos> entries. Keep the existing arrangement and replace one selected position with coordinates from your current map.

This is a template for a position element, not upload-ready XML:

<pos x="X_FROM_YOUR_MAP" z="Z_FROM_YOUR_MAP" />

Replace both labels with numeric world coordinates. x and z are the horizontal axes; do not paste a three-number position containing height into two attributes. Use a map or an authorised PC admin tool to collect the position, then inspect the ground in-game.

For the first test, choose accessible ground away from water, cliffs, toxic areas and enclosed structures. Check the surrounding area as well as the exact point. The generator samples a grid around each coordinate, so a centre on dry land can still produce unsuitable candidates near its edges.

Keep the generation and group rules

Section	What to review
generator_params	Grid dimensions, density and terrain restrictions used to generate candidates.
spawn_params	Runtime suitability checks, including nearby players and infected.
group_params	Whether groups are active and how the selected group rotates.

Scroll to see all columns →

Keep these values unchanged while testing a location edit. Bohemia documents group lifetime and counter behavior; groups_as_regular allows grouped positions to act as regular spawn points when enablegroups is disabled. An enabled group rotation means several respawns can use the same area; one result does not prove that the other groups are ignored.

Do not reduce exclusion distances to zero to force a bad point to work. Choose suitable ground first. Avoid turning every fresh spawn into a single shared location on a public server unless that is the mode you intend to run.

Validate and run the acceptance test

Parse the complete XML in PowerShell before uploading it:

$spawnXml = [xml](Get-Content -LiteralPath './cfgplayerspawnpoints.xml' -Raw)
if ($null -eq $spawnXml.SelectSingleNode('/playerspawnpoints/fresh/generator_posbubbles')) {
    throw 'Missing the expected fresh-player spawn section.'
}
$spawnXml.playerspawnpoints.fresh.generator_posbubbles | Format-List

Check that the edited <pos> is live XML rather than text inside <!-- ... -->. This check detects malformed XML and a missing fresh-player section; numeric coordinates and game behavior still need review.

Upload while the test server is stopped, start it and inspect startup logs. Use a disposable test character or a separate test copy with fresh-character state:

1. Create a fresh character and record where it appears.
2. Repeat across the configured group rotation, checking each changed area.
3. Check access to cover, water and an exit route. Test the area with another connected player because runtime distance rules can change candidate selection.
4. Restart, create another fresh character and confirm the configuration still loads.

Do not delete live characters or world persistence to test a coordinate change. A reconnecting survivor should retain its saved position.

If nothing changes, confirm the selected mission, live filename, fresh section and any spawn-selection mod. If only one area fails, inspect its ground and generated grid. Roll back by restoring the original XML while stopped, then restart and retest.

For a new character’s equipment, use the starter gear procedure. Return to the DayZ tutorial hub for other configuration jobs.