← All posts
August 7, 2026·4 min read

DayZ types.xml: How to Edit Loot in Bulk Without Breaking Your Server

What nominal, min, lifetime, and restock mean in types.xml, why editing thousands of lines by hand breaks the economy, and how to change loot in groups while keeping a working backup.

types.xml is the file that keeps DayZ admins in a text editor all evening. It describes every item in the world: how many should exist, where it spawns, and how long it lasts.

The file is big — several thousand entries in a vanilla setup. That creates two problems: editing it by hand takes forever, and one wrong character breaks it easily.

How one entry is structured

Each item is a <type> block with parameters:

<type name="M4A1">
    <nominal>5</nominal>
    <lifetime>7200</lifetime>
    <restock>1800</restock>
    <min>2</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="weapons"/>
</type>

Here's what actually matters, by meaning rather than by name.

nominal — how many units of the item the economy tries to keep in the world. Not "how many spawn instantly," but a target count.

min — the threshold below which restocking kicks in. Once the world has fewer than this many, restock begins.

lifetime — how many seconds an item sits untouched before it despawns. 7200 is two hours.

restock — the delay before replenishing, also in seconds.

category, along with nested usage and tier, determine where an item can appear: which location types and which zones of the map.

◆

The most common beginner mistake is bumping nominal for a favorite weapon to a hundred and being surprised it still doesn't show up. The economy isn't limited by that number alone: if the item doesn't have the right usage and tier set, there's simply nowhere for it to spawn.

Why manual editing is risky

Three ways to break a server, all of them common.

An unclosed tag. Miss a </type> and the server won't start. The log will show a parsing error with a line number, and that's the lucky outcome.

A duplicate entry. The same name appears twice. Behavior is unpredictable, and there might be no error at all.

Mod inconsistency. A mod adds items through its own file, you edit the vanilla one, and part of your changes don't apply. Or the reverse — you edit an item that's no longer in the current build.

Scale matters too: a typical request sounds like "cut all military loot in half" or "raise lifetime for every medkit." That's hundreds of entries. By hand, that's an hour of work and a near-guaranteed typo.

How to change things in bulk

The right approach isn't opening the file and scrolling — it's describing a rule.

"Find every <type> with category weapons and tier 4, halve nominal, scale min proportionally, leave everything else alone" — that's one operation on the file, not three hundred edits by hand.

Tasks like this get handled either by a script or by an agent with access to files. The difference is that a script needs rewriting for every new request, while an agent just needs the rule spelled out in words.

What's worth handing off entirely:

  • bulk changes by category, tier, or name pattern;
  • validating the XML and checking for duplicate name values before a restart;
  • cross-checking types.xml against the item list from installed mods;
  • parsing a log's error message to point at exactly what's wrong and where.

Doka does this on the spot: opens the file where it lives, edits it, saves it. You can keep the model local — server configs never leave the machine. It's free to install.

The rule that saves you

Make a copy of the file before any bulk edit. It sounds obvious right up until the first time you skip it.

A reasonable minimum: keep the mission folder under git. Then you can see exactly what changed between runs, and rolling back is one command. For a file with thousands of lines that gets edited iteratively, that pays off within the second week.

Second rule: change one thing at a time and restart. DayZ's economy doesn't react instantly, and if you changed five things at once, there's no way to tell which one caused the odd result.

How to check that it worked

Restarting the server isn't a check. The file can be valid while the outcome still isn't what you had in mind.

Compare nominal totals per category before and after: if the overall loot amount tripled when you meant to double it, an extra entry snuck in somewhere. And give the economy time — after a clean restart, the world fills up gradually, and the first few minutes don't tell you much.

Overall server setup, including launch parameters and ports, is covered in the article on running your own DayZ server.