Change the server-wide infected ceiling in the active mission’s db/globals.xml. Find ZombieMaxCount, keep type="0", replace its integer value, save valid XML, and restart the server. The documented vanilla value is 1000, but it is a reference default—not a universally safe target.
Prefer not to run the server on your own PC? Godlike.Host offers hosted DayZ servers with free DDoS protection and up to three free backups a day.
If towns still do not look denser, the global cap is not the only control. Infected events, territory limits, and the zombies settings in db/economy.xml determine how that ceiling is used.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What you are actually changing
ZombieMaxCount is a map-wide ceiling: the maximum number of spawned infected allowed across all zones. Bohemia Interactive’s Central Economy reference describes it as the “Maximal limit of spawned zombies across all zones in map” and documents 1000 as the vanilla default.
That value is not a promise that 1,000 infected will exist at once, nor does it assign a fixed number to every city or village. The Central Economy allocates infected through event definitions and territory rules. A higher ceiling gives the economy room to maintain more infected, but local rules, active players, and the current state of the economy still determine what you see.
#1 Best Overall
- Use any means necessary to survive a hostile open world for as long as possible.
- explore the authentic open world of chernarus, featuring 230 square kilometres of hand-crafted terrain based on real-life locations.
- become immersed in a tense, emotional experience driven by the emergent interactions of 60 players on a single server, each one fighting for survival.
- experience a wide variety of complex survival mechanics, from hunting and crafting, through to sophisticated injury simulation and transferable diseases.
- survive against environmental dangers, including the infected, dynamic weather, and animal predators
Global cap versus local density
| Reader goal | Primary file | Scope | What it affects | What it cannot guarantee |
|---|---|---|---|---|
| Allow more infected across the map | db/globals.xml, ZombieMaxCount |
Server-wide | The total ceiling shared by all zones | A particular town having more infected immediately |
| Change infected event or type behavior | events.xml |
Event and type rules | Spawn-event behavior and the percentage chance associated with zombie types | Exceeding the global ceiling |
| Change numbers in individual territories | zombie_territories.xml |
Local zones | Static and dynamic spawn ranges and territory behavior | Raising the map-wide maximum |
| Check whether the subsystem runs and persists | db/economy.xml |
Economy subsystem | Whether zombies are initialized, loaded, respawned, and saved | Replacing the cap or territory settings |
Think of the files as layers. globals.xml supplies the upper bound; events and territories decide how that allowance is distributed; the economy configuration determines whether the infected system is active and persistent.
Before editing: protect the live mission
Make the change while the server is stopped or placed in maintenance mode. Editing a live file can race with a save operation, leaving a partial or reverted configuration. A backup also gives you a known-good recovery point if the server refuses to start.
- Identify the mission selected by the server. Typical vanilla missions use a map-specific folder such as
dayzOffline_chernarusplusor anotherdayzOffline_<map>directory. Use the folder named in the server’s startup configuration or host control panel, not simply the first mission folder you find. - Stop the server, or enable the host’s maintenance mode so no players can join while files are being changed.
- Copy the complete active mission folder to a safe location. Keep the original folder name and record the time of the backup.
- Open the active mission’s
dbdirectory and locateglobals.xml. If your host exposes files through a web manager, download the file before editing so you can restore it independently of the panel.
Step-by-step: raise or lower ZombieMaxCount
- Open the correct file. In the active mission, open
db/globals.xmlwith a plain-text editor that does not add formatting. Do not edit a template mission that the server is not using. - Find the variable. Search for
ZombieMaxCount. A vanilla entry is formatted like this:<var name="ZombieMaxCount" type="0" value="1000"/> - Change only the value. Replace the number inside
valuewith the whole-number ceiling you want. For example, a cap of 1500 is:<var name="ZombieMaxCount" type="0" value="1500"/>Keep
type="0". This variable is an integer setting; changing the type or placing text, decimals, commas, or a negative sign in the value can make the setting invalid. - Preserve the XML structure. Leave the
name, quotation marks, slash, and surrounding tags intact. Do not add comments inside the variable or convert the self-closing tag into malformed markup. Save as ordinary XML text. - Upload the edited file. If you downloaded the file, return it to the same
dbdirectory in the active mission. Confirm that the host did not create a second copy with a suffix such as “(1)” and that the filename remains exactlyglobals.xml. - Restart cleanly. Start the server from the host panel or service manager after the upload. DayZ reads the economy configuration from the selected mission files, so a restart is required for a clean reload.
- Validate in game and in logs. Join after the server is ready. Check the server log for XML or economy errors, then observe infected activity, server FPS, and player desync. Keep the backup until the change has survived a full restart and a normal save cycle.
Choosing the first value
The documented vanilla value of 1000 is a baseline for the configuration, not a recommendation for every machine. If you are increasing the cap, use a measured step rather than jumping to an extreme number. The useful increment depends on your map, concurrent players, mods, hardware, and other Central Economy activity. Record the old value and each test value so you can roll back without guessing.
Why a larger cap may not make towns look fuller
Infected are spawned and maintained through several constraints. A global increase can have no obvious local effect when another layer is limiting the zone you are watching.
The server may be reading a different mission
Many installations contain more than one map mission or a default copy used only as a template. If the startup selection points to another directory, editing that unused copy changes nothing. Verify the mission path in the running server’s configuration and make the edit there.
The server may not have reloaded the file
Changing a file while the process is running does not guarantee an in-memory economy reload. Stop or restart the server after saving, and check the startup log for parsing errors. A typo can cause the server to ignore the setting or fail to initialize the economy.
Rank #3
- 🎮 Collector's Item: Allows for CO/VS functionality for co-op action (cable included). CO/VS multiplayer technology allows two Pocket Players to be linked together for cooperative gameplay using the included CO/VS cable
- 🎁 Konami Licensed Collectible: Includes arcade version of Contra and Super Contra
- High Resolution: This pocket-sized game features a high-resolution 2.8-inch full-color vertical display.
- Powered by either 4 AA batteries or by any micro USB cable (not included)
- 🎵 Built-in front facing speaker, volume control, and 3.5 mm headphone jack.
Events may be limiting spawn behavior
The infected event definitions in events.xml control event and type behavior, including the percentage chance associated with each zombie type. Those rules influence what the economy attempts to spawn; they do not replace the server-wide cap. If event limits are lower than the new ceiling, raising ZombieMaxCount alone will not fill every zone.
Territory ranges may be lower
zombie_territories.xml contains local static and dynamic territory settings, including the ranges used for infected in individual zones. A town can therefore remain sparse even when the global allowance is much higher. Review the territory that contains the town rather than assuming every zone inherits the global value directly.
The zombies subsystem may be disabled or not persisting
Use db/economy.xml to verify that the zombies subsystem is initialized, loaded, respawned, and saved as intended by your configuration. If that subsystem is disabled, a larger global cap has nothing to act on. If loading or saving is misconfigured, you may see temporary behavior that disappears after a restart.
Rank #4
- Award winning innovative design that bridges the gap between roleplaying and boardgaming in space by integrating ship to ship and boarding action.
- You and your friends play characters as the crew of a ship laid out in modular format. Your ship is on a hex map. The enemy controls whatever challenges you face. Your continuing characters rise in power as you face tougher and more exciting challenges.
- Age 12+ / 1-6 players / 60-240 minutes playing time
- Second edition, advanced rule book sold seperately
How the related files fit together
Use this order when diagnosing a result: first confirm that the subsystem is active, then confirm the global ceiling, then inspect event and territory limits.
Recommended Free Tools
db/economy.xml— subsystem state. Establish that infected processing is enabled and that the server can load, respawn, and save its economy data.db/globals.xml— total allowance. SetZombieMaxCountas an integer. This is the shared ceiling for all map zones.events.xml— event and type behavior. Check whether event definitions and type percentages permit the infected mix and activity you expect.zombie_territories.xml— zone-level allocation. Check static and dynamic ranges for the specific settlement or region where you are testing.
This layered model also explains why two servers with the same ZombieMaxCount can show different counts: their maps, territory ranges, events, player locations, and active economy state are not identical.
Performance: raise the ceiling without guessing
Every additional active infected can add AI processing, pathfinding, network updates, and collision work. The practical cost changes with map layout, player population, mods, hardware, and other economy activity. No universal “safe” zombie number has been established, so do not treat 1000—or any larger figure—as a hardware guarantee.
Best Value
- Dress in style on Nasdara, Sakhal, Chernarus or Livonia with our design. Built to survive in the badlands of dayz in any zombie wasteland so take a day off and dress to impress with our low insulation but high cool Z inspired design.
- Compatible with all PC gamers or console players. Game in comfort for dayz. Also a great gift idea for any discerning online survival gamers.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Use staged changes
- Write down the current cap and take a backup.
- Increase it by a moderate step and restart.
- Test with the normal player count, especially in the busiest settlement and during travel between zones.
- Watch server FPS, player-reported desync, and log errors for several minutes rather than judging from the first few seconds after login.
- Keep the value if performance remains acceptable; otherwise restore the previous value or choose a smaller step.
Testing only while alone can hide the cost of multiple active zones. Conversely, a short spike immediately after a restart may not represent steady-state behavior, so compare observations under repeatable conditions.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesUnderstand active-zone distance
The DayZ Modding Wiki lists ZoneSpawnDist as the distance at which infected zones activate around players and gives 300 as a vanilla example value. It is an activation-distance setting, not another global count. A larger active radius can cause more zones to be processed around players and may increase AI work; whether that is worthwhile depends on your server’s layout and capacity. Change it separately from ZombieMaxCount so you can tell which setting caused a performance change.
Troubleshooting by symptom
“I changed the number, but nothing changed.”
- Confirm that the edited path is the mission selected at startup, not a spare map folder or template.
- Check that the line still uses
type="0"and a whole-numbervalue. - Restart the server after uploading the file.
- Inspect startup and economy logs for XML parsing errors.
- Verify that infected processing is enabled in
db/economy.xml. - Inspect the relevant
events.xmlandzombie_territories.xmlrules; local limits can remain below the new global ceiling.
“The server will not start after I edited the file.”
- Stop any repeated restart loop from the host panel.
- Restore the backed-up
globals.xmlto the active mission. - Start the server and confirm that it returns to its previous healthy state.
- Reapply the change carefully, editing only the digits in
value, then validate the XML before restarting again.
Do not troubleshoot by changing several economy files at once; that removes the evidence needed to identify the invalid setting.
“There are too many infected or players report desync.”
Lower the cap to the last stable value, restart, and retest. If the cap is already modest, inspect territory allocation, event behavior, active-zone distance, and other mods or economy systems that may be competing for server time. Measure server FPS and desync while reproducing the problem instead of assuming the cap alone is responsible.
“The number changes after a restart or update.”
Compare the active mission file with your backup and confirm which deployment process the host uses. Some panels expose separate live and default directories; always edit the live mission selected by the server. Keep a dated copy of your working configuration so you can identify whether a later file replacement, map change, or configuration edit altered the result.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A repeatable maintenance checklist
- Identify the live
dayzOffline_<map>mission. - Stop the server or enable maintenance mode.
- Back up the active mission folder.
- Open
db/globals.xmland findZombieMaxCount. - Change only the integer in
value; retaintype="0". - Save valid XML and upload it to the same mission path.
- Restart the server.
- Check logs, infected activity, server FPS, and player desync.
- If local density is unchanged, inspect
db/economy.xml,events.xml, andzombie_territories.xml. - Keep the previous value available for an immediate rollback.
What to change for common objectives
| Objective | First action | Next check | Main risk |
|---|---|---|---|
| Raise the maximum infected anywhere on the map | Increase ZombieMaxCount in the active mission’s db/globals.xml |
Restart, then monitor FPS and desync | More AI work across active zones |
| Make one town denser | Inspect that town’s territory entry in zombie_territories.xml |
Check event definitions and player activation conditions | Changing a local range can affect zone behavior without changing the global cap |
| Change which infected types appear | Review the relevant infected event definitions in events.xml |
Confirm the global cap still permits the desired total | Type percentages and event rules may alter composition rather than total count |
| Ensure infected return after restarts | Verify zombie initialization, loading, respawn, and saving in db/economy.xml |
Restart and observe whether the state persists | A high cap cannot compensate for a disabled or misconfigured subsystem |
Key takeaways
The dependable edit is small: use the active mission’s db/globals.xml, change the integer value of ZombieMaxCount, preserve type="0", and restart. The documented 1000 is a vanilla reference default, not a performance promise. If the visible result does not match your goal, diagnose the layered economy configuration—subsystem state, global cap, events, territories, and active-zone distance—rather than repeatedly increasing one number.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
