How to increase loot on a DayZ server

By Niko Catarino

Updated 3 October 2026

To increase world loot on a DayZ server, adjust the target nominal and replenishment threshold min for selected items in the active mission’s types configuration. Keep their location filters and other fields unless you intend to change those behaviors. Food and gear carried by infected use separate spawnable-type and cargo-preset settings.

Start with one item or category. A higher target can request more loot, but the economy still needs eligible spawn positions and room under its counting rules. A restart does not guarantee that your new target appears on the ground at once.

Preserve the world: Stop the server before replacing files. Back up the active mission, persistence and mod-owned data, then edit a working copy. A loot adjustment does not require a routine persistence wipe. Check backup inclusions and test on a separate server before applying broad changes.

Find the file for the loot you want to change

Confirm the active mission through the server configuration, launch settings or panel. Under mpmissions/, Chernarus commonly uses dayzOffline.chernarusplus, Livonia uses dayzOffline.enoch, and Sakhal uses dayzOffline.sakhal. Custom and seasonal missions can differ.

Desired change	File or configuration
More world-spawned vanilla items	db/types.xml, or a registered types override.
Natural spawns for a content mod	The author’s types file, registered in cfgeconomycore.xml.
Food or ammunition inside an infected’s inventory	cfgspawnabletypes.xml and its referenced cargo presets in cfgrandompresets.xml.
Equipment worn by infected	The referenced attachments or attachment presets.
More infected to carry that loot	Infected territory counts.

Scroll to see all columns →

Trader stock and scripted loot systems can have their own settings. Follow their authors’ instructions rather than assuming that types.xml controls every source of an item.

Increase loot on a Nitrado DayZ server

On Nitrado, the file controls differ from VXPanel. Its loot settings guide places File Browser under Tools and gives this Chernarus path:

dayzstandalone/mpmissions/dayzOffline.chernarusplus/db/types.xml

For Livonia or Sakhal, use the selected mission’s dayzOffline.enoch or dayzOffline.sakhal folder. Confirm the active mission and the file access available on your service before editing.

1. Preserve the original mission files and verify the persistence backup. Stop the server before replacing files.
2. Download the current types.xml. Start with one item and record its original nominal and min values.
3. Change those targets while retaining the other fields, or use the separate override procedure if your service exposes cfgeconomycore.xml and permits extra mission files.
4. Parse the complete edited XML, transfer it to the same active mission and restart. Read the new logs and test natural loot in eligible locations.

Keep persistence when testing these loot changes.

Check the file through the active economy

A file can pass an XML parser while referring to a missing mod class or a loot location your terrain does not define. Trace the working copy through these checks before raising item targets:

Check	Evidence to collect
Document structure	A complete XML document with a <types> root and the intended <type name="..."> entries.
Active mission	The mission selected by startup settings and the path downloaded from that mission.
Registration	Each relevant type="types" entry in cfgeconomycore.xml, with its folder and filename present.
Item identity	The exact classname supplied for the installed mod version.
Location rules	Category, usage, value and tag names checked against cfglimitsdefinition.xml and any user definitions.
Running economy	Current startup/economy logs and natural spawns in locations allowed by those rules.

Scroll to see all columns →

Spawning a class with an admin tool checks that it loads. Natural ground loot also needs the economy entry and eligible positions.

Use the economy change record to retain the source paths, competing overrides, changed values and observed results. Its result fields are blank so your own test supplies the evidence.

Understand nominal and min

nominal is the target count for a type. min is the threshold that triggers replenishment under the economy’s counting rules. Neither value is an item count per building.

Field	What it changes
nominal	Desired population of the item type.
min	Low-stock threshold used for replenishment. Keep it at or below nominal.
lifetime	Item lifetime in seconds, subject to persistence and refresh behavior.
restock	Restocking interval in seconds. It does not guarantee a drop at a specific place or time.
quantmin, quantmax	Quantity within a spawned item, where supported, such as magazine fill. These do not set world abundance or item health.
usage, value, tag, category	Filters used to match eligible loot positions.
count_in_map, count_in_cargo, count_in_hoarder, count_in_player	Whether stock in those contexts counts toward the configured population.

Scroll to see all columns →

Leave the fields outside your intended change intact. For example, increasing magazine nominal requests more magazines; it does not fill each one or make it pristine. A types entry with nominal set to 0 can be disabled for world spawning, so review its purpose before enabling it.

VetGamer23 explains the types fields from 2:09 in a tutorial published on 30 January 2026. Treat its item values as examples from that installation. The actual Bohemia Chernarus types file provides a version-pinned reference.

Increase one item through a types override

Use a separate override so your local settings are easier to compare when the game’s mission files change. Bohemia’s mission-file modding reference supports partial overrides of existing types.

The linked Chernarus reference sets TunaCan to nominal 20 and min 15. An example test increases those to 30 and 22:

1. Create a folder named custom inside your working mission copy.
2. Save this complete XML document as custom/loot-overrides.xml:

<?xml version="1.0" encoding="UTF-8"?>
<types>
    <type name="TunaCan">
        <nominal>30</nominal>
        <min>22</min>
    </type>
</types>

3. Add this fragment inside the existing <economycore> element in the mission’s cfgeconomycore.xml, before its closing tag:

<ce folder="custom">
    <file name="loot-overrides.xml" type="types" />
</ce>

4. Keep all existing classes, defaults and file registrations. Check whether another registered file already overrides TunaCan; resolve competing definitions before testing.
5. Validate both complete XML files, then transfer the folder and edited cfgeconomycore.xml while the server is stopped.

These are test values, not a recommended balance for every community. The partial override changes only nominal and min; it leaves the type’s other fields intact. If you redefine multi-value fields such as usage, tags, values or flags, Bohemia’s merge rules can replace the corresponding originals. Read those rules before broadening the override.

Adding usage, tag or value names replaces the original names within that group. Defining flags requires the full flag set. A new usage entry can therefore remove an item’s previous locations. For a new mod class, start with the author’s complete economy definition; partial overrides of an existing vanilla type cannot supply that new class’s missing fields.

For a syntax check on your downloaded working copy, run:

[xml](Get-Content -LiteralPath '.\custom\loot-overrides.xml' -Raw) | Out-Null
[xml](Get-Content -LiteralPath '.\cfgeconomycore.xml' -Raw) | Out-Null

Parsing proves XML syntax, not file registration, classname validity or natural spawning.

Parse types.xml without uploading it

For a downloaded db/types.xml, this Windows reader rejects DTDs and checks the document without resolving external resources:

$xmlSettings = [System.Xml.XmlReaderSettings]::new()
$xmlSettings.DtdProcessing = [System.Xml.DtdProcessing]::Prohibit
$xmlSettings.XmlResolver = $null
$xmlReader = [System.Xml.XmlReader]::Create(
    (Resolve-Path -LiteralPath '.\db\types.xml').Path, $xmlSettings)
try { while ($xmlReader.Read()) {} }
finally { $xmlReader.Dispose() }

Success produces no output. Resolve a parsing error before transferring the file, then check registration, classnames and filters. The reader accepts well-formed XML with the wrong root or an unknown classname, so those still need inspection.

Edit categories with the VYKIX economy editor

For a group edit, the DayZ economy editor accepts a mission ZIP and processes it in your browser. It keeps the original ZIP unchanged and does not upload your files.

1. Import a ZIP of the active mission into the editor.
2. Set the loot multiplier you want to test. Leave infected, wildlife and event multipliers at 1× for a loot-only experiment.
3. Select Preview Changes and inspect the changed paths, old and new values, and configuration checks.
4. Download the edited-files ZIP and read VYKIX-CHANGES.json.
5. Apply only the intended changed files to a backed-up test mission while its server is stopped.

The export contains changed supported files, not a complete replacement mission. Review custom registrations and mod-specific configurations outside the editor’s supported scope. Its XML checks do not establish gameplay balance, server capacity or the behavior of a live server.

For a single item, use the manual procedure above. The editor does not support individual item editing or standalone types.xml imports.

Register modded loot

If a clothing or weapon mod loads but its items never spawn as world loot, check whether the author supplies an economy file. Keep that file separate from vanilla db/types.xml and register it with a type="types" entry in cfgeconomycore.xml.

Follow the mod guide’s economy registration steps. Check the mod’s installed version, dependencies and exact classnames before changing population values. An item you can spawn through an admin tool still needs the correct economy configuration for natural spawns.

Change food and gear on infected

World loot targets do not control the contents of an infected’s pockets. Follow the infected class through its spawnable-type entry to the preset it references:

1. Find the target class in the mission’s cfgspawnabletypes.xml.
2. Read its <cargo preset="..." /> and <attachments preset="..." /> entries.
3. Find the named preset in cfgrandompresets.xml.
4. Change one preset’s outer chance and test newly spawned infected of that class.

For example, the reference spawnable types link ZmbM_PatrolNormal_Autumn to foodArmy. In the reference random presets, that cargo preset has an outer chance="0.1". Testing 0.2 raises that outer chance from 10% to 20%; it does not promise a particular item or a drop on every second infected.

Change the opening tag’s chance in your complete preset, retaining its name, child items and closing tag. Keep the item-level chances unchanged for the first test. Presets can be shared by several classes or containers, so check all references before changing one. If you need a change for one class, use a distinct preset and point that class to it, preserving any other cargo or attachments it needs.

If you move the class edit into a separate registered spawnabletypes override, defining cargo replaces that class’s original cargo list, and defining attachments replaces its original attachment list. Retain the complete list you need. The complete-truck tutorial explains this merge behavior with a vehicle example.

Decimal chance values need care: 0.5 means 50%, while 0.005 means 0.5%.

Do not expect an existing infected or corpse to acquire new loot after the edit. Validate the complete files, restart, and sample new spawns. A few empty inventories can still occur with a working chance-based configuration.

Diagnose loot that does not spawn

Symptom	First checks
All loot stops after an upload	Save the logs, stop the server and check XML errors or accidental replacement of vanilla db/types.xml. Restore the known-good configuration.
Only mod items are missing	Check package loading, registered file paths, the author’s classnames and their population values.
The change has no effect	Re-download the live file, confirm the active mission and check for another override of the same type.
Loot appears in some buildings but not others	Check usage, tier, tag and category filters against available loot positions.
A higher nominal does not produce more visible loot	Check counted existing stock, eligible positions, restock timing and the economy logs.
Items disappear sooner than expected	Compare lifetime, item damage, cleanup settings and any mod behavior.
Infected spawn but have no new cargo	Check the class-to-preset link, shared presets, chance values and whether you tested new spawns.

Scroll to see all columns →

Increasing a target beyond available positions can add unsuccessful spawn requests. Bohemia’s custom-terrain economy guide explains the relationship between type counts and loot space. Avoid multiplying every field or raising all targets to the same large value.

Verify the result and keep a rollback

Start the test server and inspect the current RPT and script logs. Visit areas that match the edited item’s filters, move away to allow normal spawn processing, then repeat your checks. If you have diagnostics that show loaded type values or economy counts, compare them with the edited file as well as observing the ground loot.

An empty server can enter economy idle mode. Bohemia’s economy configuration reference documents IdleModeStartup and IdleModeCountdown in db/globals.xml. Check those settings when interpreting waiting time without players, and use a connected player for the natural-spawn check.

Record the game build, mission, item, original and edited values, registered files, player count and observed result. Check vanilla loot too when adding a mod. Keep that record with the backup so the next update has a known comparison point.

To roll back, stop the server, restore the saved configuration files and restart. A configuration rollback does not remove items the altered economy has already spawned; their later cleanup follows the restored rules and persistence state. Treat a world wipe as a separate decision with its own backup and player communication.

Use the server update guide to retain custom registrations when replacing stock mission files. For the next world change, follow the infected spawn guide, or review managed DayZ hosting if you need a service with mission-file access.