DayZ Types.xml: How to Change Loot Quantity

Updated 9 November 2026 · Standard formula, shown below

Editing types.xml lets you adjust how many copies of an item the DayZ Central Economy tries to maintain across the map. You will need access to your server’s mission files and a text or XML editor; make a backup before changing anything.

What You’ll Need

Access to your DayZ server’s files, either through its control panel, FTP, or the host’s file manager.
The correct mission folder and its db/types.xml file.
A plain-text or XML editor that preserves the file as UTF-8 text.
A backup of the original file and, ideally, a way to review server startup logs.

Step-by-Step

Stop the server. Shut down the server before editing its economy files. This prevents the game or hosting tools from writing changes over your edit and avoids testing a partly loaded economy.
Find the active mission’s types.xml. Open the mission folder used by the server. In a standard DayZ mission layout, the file is under db/types.xml. The folder name varies by map and server setup, so confirm which mission the server launch settings or hosting panel actually uses. Editing a spare mission copy has no effect.
Make a backup. Download or copy the complete types.xml and save it somewhere outside the live mission folder. Keep the untouched original until the edited server has started and you have checked the results.
Locate the item entry. Search for the item’s exact class name, which is the value in its <type name="..."> tag. Do not assume its display name is its class name. You can check the class name against the item list for your game version or existing server configuration. A typical entry looks like this:
<type name="ExampleItem"> <nominal>10</nominal> <min>5</min> <restock>1800</restock> <flags count_in_cargo="1" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="0" deloot="0" /> <category name="tools" /> </type>
Use the item’s existing entry as the template. Do not replace it with this illustrative example.
Set the target quantity. Change the number inside <nominal>. This is the economy’s target quantity, not a promise that this many items will instantly appear in the world. Increasing it generally allows more copies to be maintained; lowering it generally reduces the target.
Review the minimum and counting flags. <min> is a low-water threshold used by the economy, not a second quantity setting to copy blindly. Keep it sensible relative to nominal and follow the structure of comparable entries. The flags determine which locations or states count toward the economy’s totals; for example, cargo, map, player, and hoarder counting can affect how quickly the target is replenished. Preserve the original flags unless you deliberately want to change counting behavior.
Leave restock and other fields alone unless needed. <restock> controls the restock interval in seconds; it does not set the total number of items. Categories, usage, value, and other tags help determine where and how an item can spawn. Changing them along with nominal makes it harder to identify which edit caused an unexpected result.
Check the XML and save. Keep the opening and closing tags paired, retain quotation marks, and edit only the intended numeric value. Save in the same location and encoding. If your editor has XML validation, use it; otherwise, compare the edited entry with the backup and check that the surrounding structure remains intact.
Restart and test. Start the server and inspect its logs for XML or economy-loading errors. Allow the Central Economy to run and replenish items; results may not be immediate. Check several relevant spawn locations and, if possible, compare over time rather than judging from one visit.
Roll back if necessary. If the server fails to load the file or the loot behavior is clearly wrong, stop it and restore the backup. Make one small change at a time, restart, and test again.

Common Mistakes

Editing the wrong mission: Servers may contain several map or mission folders. Only the active mission’s file is read.
Confusing nominal with an instant spawn command: Nominal is an economy target. Existing items, cleanup, spawn rules, and restocking all affect what you see.
Changing the display name instead of the class name: The XML entry must use the item’s exact class name.
Setting min higher than nominal: This creates an inconsistent target configuration. Keep the minimum at or below the intended nominal value unless you have a specific, tested reason otherwise.
Breaking XML syntax: Removing a tag, quote, or closing bracket can stop the economy file from loading.
Expecting restock to control quantity: Restock is timing-related; nominal is the main target quantity field.

Tips

Change one item at a time and keep a short note of the old and new values.
Use modest increases first. Large targets can make loot unusually common and may affect the balance of a server.
Check whether the item is intended to spawn naturally. Some items are controlled by other systems or special event settings, so editing a types entry alone may not produce the result you expect.
Keep a copy of the working file after a successful restart. Reuse it as a recovery point before future edits.
When running mods, verify that the item class and the relevant economy configuration match the installed mod and server version.

Troubleshooting

The server will not start or the economy reports an error: Stop it and inspect the startup log for the file path and XML line mentioned. Check for a missing closing tag, malformed quote, invalid number, or accidental deletion. Restore the backup if the error is not obvious, then reapply the change carefully.

The quantity does not seem to change: Confirm that you edited the active mission’s db/types.xml, the exact item class, and the intended tag. Restart the server after saving. Then allow time for the economy to update; a target does not necessarily create an immediate pile of loot.

The item is still rare or appears in the wrong places: Nominal alone does not define spawn locations. Review the entry’s usage and value tags, category, counting flags, and any event or mod configuration that affects the item. Compare with a similar item that spawns where you expect, and change only one relevant setting at a time.

Changes disappear after a restart: Check whether the host deploys a template, restores a backup, or uses a different mission directory at startup. Edit the source file the server actually loads, not a downloaded copy that is overwritten.

Frequently Asked Questions

What does nominal mean in DayZ types.xml?
It is the Central Economy’s target quantity for that item, subject to the entry’s rules and the state of items already counted by the economy.

Does increasing nominal spawn the extra loot immediately?
No. The economy may need time to restock, and existing items or other spawn conditions can affect when and where replacements appear.

Should min equal nominal?
Not necessarily. Min is a separate low-water threshold. Keep it sensible and consistent with comparable entries rather than treating it as a duplicate of nominal.

Do I need to wipe the server to change loot quantity?
Usually, a full wipe is not needed just to edit a target quantity. Restart the server and allow the economy to update. Server-specific settings and existing item states can affect the transition.

Can I change loot quantity on an official server?
These instructions are for servers whose configuration files you control. You cannot edit the server-side mission files of an official server.

Why does the item not spawn after I add it to types.xml?
The class name may be wrong, the item may need a matching category or usage configuration, or another event or mod setting may control it. Check logs and compare the full entry with a known working configuration.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.