Configure server loot (types.xml)

DayZ loot is driven by types.xml, an XML file located in your mission folder. It defines, for each item, the target quantity on the map, its lifetime and the spawn conditions (near, restock, flags). It is the central file for tuning rarity.

Cause / The problem

A badly edited types.xml (unclosed tag, comma instead of dot) disables all server loot: no weapon, food or clothing spawns anymore. And without understanding nominal/min, you end up either with too much loot (easy server) or none at all.

Solution

1. Locate the file at /serverfiles/mpmissions/<mission>/db/types.xml. <mission> depends on the map: dayzOffline.chernarusplus for Chernarus, dayzOffline.enoch for Livonia.
2. Back up before editing:

   cp types.xml types.xml.backup

   Essential: one XML error = zero loot at reboot.
3. Understand the fields of a <type> entry:

   <type name="AK74">
       <nominal>10</nominal>   <!-- target quantity on the map -->
       <min>5</min>            <!-- minimum before respawn -->
       <lifetime>14400</lifetime>  <!-- lifetime in seconds -->
       <restock>1800</restock>     <!-- delay between spawns -->
       <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"/>
   </type>

4. Tune rarity with nominal and min: the higher, the more common. For a hardcore server, divide weapon values by 2 or 3.
5. The <flags> control where the item is counted: count_in_map (on the ground), count_in_cargo (in containers), count_in_player (in inventories). The server adjusts spawns based on what already exists.
6. Validate the XML before restarting. A single syntax error kills all loot. Use an online XML validator or an editor with syntax highlighting.
7. Restart the server after every change. Loot regenerates gradually based on lifetime and restock.

For advanced tuning (conditional spawn near, categories), also edit cfgspawnabletypes.xml and events.xml in the same db/ folder.