The types.xml file is the primary loot economy configuration for DayZ. It determines which items can spawn, how many exist at once, their spawn locations, restock rates, and distribution across the map. Mastering this file is essential for balancing gameplay and customizing your server’s loot experience.
The types.xml file defines how items spawn in your DayZ server. It controls:
The types.xml file is composed of multiple <type> elements, each representing a unique item class. Every <type> entry specifies spawn counts, restock intervals, spawn locations, and other parameters that control the item’s behavior in the loot economy.
<type name="PeachesCan">
<nominal>15</nominal>
<lifetime>14400</lifetime>
<restock>0</restock>
<min>12</min>
<quantmin>-1</quantmin>
<quantmax>-1</quantmax>
<cost>100</cost>
<flags count_in_cargo="0" count_in_hoarder="0" count_in_map="1" count_in_player="0" crafted="0" deloot="0"/>
<category name="food"/>
<tag name="shelves"/>
<usage name="Town"/>
<usage name="Village"/>
<usage name="School"/>
<value name="Tier1"/>
<value name="Tier2"/>
<value name="Tier3"/>
</type>The target number of this item that the server will try to maintain. If the count drops below this value, the item will be eligible to respawn.
The time in seconds an item will remain in the world after spawning, if not picked up or interacted with.
The minimum time in seconds before the item is eligible to respawn after being removed from the world.
The minimum number of this item that should always be present on the server. The system will attempt to maintain at least this many.
The minimum quantity for items that have a fillable value (e.g., ammo in a magazine, water in a bottle). Use -1 for items without a quantity.
The maximum quantity for items that have a fillable value. Use -1 for items without a quantity.
A weighting value that influences how likely this item is to spawn compared to others. Higher values increase spawn probability.
If enabled, items stored in cargo (backpacks, crates, vehicles) are counted towards the nominal and min values.
If enabled, items stored in hoarding containers (tents, barrels, stashes) are counted towards the nominal and min values.
If enabled, items inside buildings and on the map are counted towards the nominal and min values.
If enabled, items in player inventories are counted towards the nominal and min values.
If enabled, marks the item as player-craftable only (not spawned by the economy).
If enabled, marks the item as dynamic event loot (e.g., helicopter crash, contaminated zone).
Defines the item’s category group (e.g., weapons, food, tools). Used for filtering and organizing items in the economy.
Specifies the area or context where the item will spawn (e.g., farm, military, town). Up to 4 usages per item.
Defines the item’s value grouping or tier (e.g., Tier1 for spawn zones, Tier4 for high-tier military). Used for regional loot balancing.
types.xml for syntax errors and logical mistakes
types.xml before making changes
<type name="M4A1">
<nominal>8</nominal>
<min>3</min>
<lifetime>14400</lifetime>
<restock>1800</restock>
<flags>1</flags>
<category>weapons</category>
<usage>Military</usage>
</type><type name="TacticalBaconCan">
<nominal>40</nominal>
<min>25</min>
<lifetime>7200</lifetime>
<restock>1800</restock>
<quantmin>1</quantmin>
<quantmax>3</quantmax>
<cost>100</cost>
<flags>1</flags>
<category>food</category>
<usage>Town</usage>
</type>
Always backup your types.xml file before making changes. Use version control or regular backups, and validate your XML after edits. Tools like DZconfig can help manage and validate your configurations automatically. Improper configuration can lead to loot explosions or barren servers—test changes on a staging environment first.