How to increase zombies on a DayZ server

By Niko Catarino

Updated 3 October 2026

To increase zombies in a DayZ town, edit that area’s dmin and dmax values in the active mission’s env/zombie_territories.xml. Check ZombieMaxCount in db/globals.xml if the server has reached its map-wide cap. Raising the cap alone does not increase the numbers requested by each territory.

DayZ calls these creatures infected in its event names. The steps below cover the vanilla Central Economy on a PC server with mission-file access. A mod that spawns infected through scripts can have its own controls.

Keep a recovery copy: Stop the server before replacing mission files. Back up the active mission, its persistence and any mod-owned data. Check backup inclusions before relying on a panel backup. Make the first change on a test copy and keep player progress intact.

Find the active mission

Confirm which mission your server starts through its configuration, launch settings or hosting panel. Common folders are:

Map	Mission folder under mpmissions/
Chernarus	dayzOffline.chernarusplus
Livonia	dayzOffline.enoch
Sakhal	dayzOffline.sakhal

Scroll to see all columns →

Custom maps and seasonal missions can use other folders. Use the selected mission rather than assuming that the first folder in File Manager is live.

Download its files into a working folder. Keep a second, untouched copy for rollback. In VXPanel, use Files and SFTP for transfers.

Choose the setting that matches the change

File relative to the mission	What to check
env/zombie_territories.xml	Local infected zones, their coordinates, radius and requested counts.
cfgeventspawns.xml	Event-zone counts, including infected at helicopter crashes.
db/globals.xml	ZombieMaxCount, the cap across the map.
db/events.xml	The named infected event, its active flag and available child classes.
cfgenvironment.xml	Whether the mission loads the territory file.
db/economy.xml	Whether infected initialization and respawning are enabled.

Scroll to see all columns →

The official territories and environment configuration show this relationship. These linked files are a Chernarus reference; work from the files shipped with your server’s map and game build.

Increase one existing zone

Find the zone for the place you want to change. Each line gives an event name, an x and z position, and a radius r. Match the position to your map before editing; several zones can share an event name.

Attribute	Meaning for this edit
name	The infected event used by the zone, such as InfectedVillageTier1.
dmin, dmax	Minimum and maximum dynamic infected counts requested by the zone.
smin, smax	Static count limits. Leave them at the existing values for the first test.
x, z	Horizontal map coordinates. z is not elevation.
r	The zone radius in metres.

Scroll to see all columns →

For example, the pinned Chernarus reference includes a village zone with dmin="8" and dmax="12". A first test could increase those two values to 12 and 18:

<zone name="InfectedVillageTier1"
      smin="0" smax="0"
      dmin="12" dmax="18"
      x="12913.3" z="8020" r="80" />

Replace the matching zone line inside your existing file. This fragment is not a complete territory file. Keep its enclosing elements and the other zones. Keep dmin at or below dmax.

The values above are an example test setting, not a capacity recommendation. Start with one location, leaving its radius, event name and static counts unchanged so you can assess the population change. Dynamic activation, event configuration and available capacity can affect what you observe.

Check the map-wide cap

Find ZombieMaxCount in db/globals.xml:

<var name="ZombieMaxCount" type="0" value="1000" />

Bohemia defines this as the maximum spawned infected across all zones. The official Chernarus globals file uses 1000. That number is a reference value, not a promise that your server can sustain it under every workload.

Keep your existing cap for the first local test. If occupied areas compete for the cap, assess a small increase on the test server while recording server FPS and player responsiveness. More active infected add simulation work; a successful test with one player does not establish capacity with players spread across several towns.

Leave ZoneSpawnDist unchanged during that test. Bohemia documents it as the distance that invokes dynamic infected spawning near a zone, so changing it at the same time would change another part of the experiment. See Central Economy configuration.

Add infected to another location

To add a vanilla infected population to an empty location, create a zone using an infected event that already works in your mission:

1. Find a working zone of the desired type and its matching <event name="..."> in db/events.xml.
2. Duplicate that zone line inside the existing territory structure.
3. Set x and z to a position on your map and choose a radius containing usable ground.
4. Use modest dynamic counts for the first test and retain the original static counts.
5. Check for overlapping zones before uploading the file.

Preserve the event name exactly. If you invent a new name, you also need a matching event definition and valid infected classes. A larger zone population does not create a scripted roaming horde or patrol route. Start with an existing event before attempting a custom event or horde mod.

Increase infected at helicopter crashes

Heli-crash infected have their own event-zone counts in the mission’s cfgeventspawns.xml. Find <event name="StaticHeliCrash"> and edit its existing <zone> element, keeping the event’s spawn positions intact.

The pinned Chernarus event-spawn file uses dmin="3" and dmax="5", with static counts of 1 and 3 and a radius of 45. A test edit could raise the dynamic counts to 5 and 7:

<zone smin="1" smax="3" dmin="5" dmax="7" r="45" />

Replace only the matching zone inside that event. This fragment is not a complete event-spawn file. Retain the other values for the first test and use the backup, validation and restart procedure below. Check newly spawned crashes; an existing crash is not proof that the new counts loaded.

Scalespeeder Gaming demonstrates this setting from 0:37 in a tutorial published on 7 August 2026, identified by the author as covering DayZ 1.29. Its larger 8–10 example is separate from the smaller test above. Confirm the event in your own map and game build before applying the edit.

Validate and test the change

Parse the complete edited XML before transfer. For downloaded files on Windows, this PowerShell command checks XML syntax:

[xml](Get-Content -LiteralPath '.\env\zombie_territories.xml' -Raw) | Out-Null

A successful parse does not verify coordinates, event names or in-game behavior.

Use a connected player for the spawn test. An empty server can enter Central Economy idle mode through IdleModeStartup and IdleModeCountdown; a successful startup without a player does not test zone activation. Keep those settings unchanged for the first test. Bohemia documents both in the Central Economy configuration.

1. With the server stopped, upload the edited file to the active mission.
2. Start it and inspect the current RPT and script logs for mission-file errors.
3. Join, approach the edited zone from outside it, and record the population you encounter.
4. Repeat the approach after the zone has had a chance to reset. Do not treat the first count as an exact guarantee.
5. Test with players occupying other zones and compare server FPS with your pre-change readings.

Record the game build, changed zone, old and new counts, player count and test result. If the change causes errors or a performance drop, stop the server, restore the saved configuration file and repeat the original test.

Diagnose missing infected

Symptom	First checks
Nothing changes after restart	Confirm the active mission and re-download the live file to check your edit arrived.
One zone stays empty	Check coordinates, usable ground, event name, dynamic counts and overlapping zones. Approach from outside the area.
Several occupied towns have fewer infected than expected	Check the global cap and collect server diagnostics before increasing it.
Infected are absent across the map	Check ZombieMaxCount, the infected events’ active flags, the territory-file registration and the zombies entry in db/economy.xml.
Only modded infected ignore the change	Check the mod author’s spawning system and settings.
Infected appear but their inventories are empty	Follow the cargo-preset checks in the loot guide.

Scroll to see all columns →

The reference events file and economy switches help identify missing or disabled configuration. Compare them with the matching build; do not replace a customised mission with the reference files.

Reduce or remove infected

For fewer infected in a specific place, lower that zone’s requested counts and test it. For a map-wide zero-cap test, set the existing ZombieMaxCount value to 0, validate the complete globals file and restart. Join and inspect several vanilla zones before opening the server; changing a cap is not proof that every existing entity disappeared. Scripted mod spawns can need a separate change.

To restore the population, put back the cap and territory values from your backup. You do not need to delete world persistence to make these configuration edits.

Continue configuring the server

Use the mod installation guide for PC mod files, keys and load order. For changes to item abundance or infected cargo, follow the loot guide. If you need managed hosting with mission-file access, review DayZ hosting.