DayZ types.xml and Loot

How DayZ loot tables change a server, what a bad economy feels like, and why the listing cannot see your XML.

types.xml and the rest of the central economy are why two Chernarus servers with the same slot count feel like different games. The Chernarus list cannot tell a scarce military spawn from a server where every barn is an armory. Players can. They stay or they do not, and then they describe your economy in the hostname arguments you did not write. If you change loot, you are designing the server. Treat the files like code.

The economy is a set of XML files in the mission, not a slider in serverDZ.cfg. Nominal, min, lifetime, and restock change how often an item exists in the world. Flags for crafting and for categories change where it is allowed to be. A single typo can zero out a class. The symptom is "no food on the coast" or "no mags," and the argument in chat will be about cheaters. Diff the file. Do not buff everything because one town felt empty on a Tuesday. Empty is information. A coast with an M4 in the first house is also information, and it will fill your server with people who leave when the next server buffs harder.

Modded items have to be in the economy or they exist only as dead files in an @ folder. The mod install is not finished when the server boots. It is finished when the new gun can spawn, can be stored, and can despawn. Map mods often ship their own types. Load those instead of pasting half of them into Chernarus and wondering why the bunker is bare. Namalsk and Deer Isle are the usual places this goes wrong.

Persistence and loot argue with each other. If tents never decay and types never restock, the map fills with player storage and the military zones go quiet. If you wipe types without wiping storage, players walk out of a "fresh economy" holding last month's kits. The wipe schedule and the hive note belong in the same announcement. Say which files you reset. "Full wipe" is a phrase players have been burned by.

DayZ Manager will not show your nominal values. It will show mods, map, perspective, and whether the server is busy. A loot change that you cannot feel in the player chart after two weeks was a change you made for yourself. That is allowed. It is not a marketing plan. Watch the server page. If the population only spikes on wipe day, the economy might be the reason people do not stay, or the reason they do. Learn which.

CFTools Cloud is useful here as operations, not as an XML editor. Logs and restarts tell you whether the mission you think is loaded is the mission that booted. CFTools Architect holds the files so a bad edit can be rolled back if you kept a copy. Keep a copy. The management tools page is the wider set. None of them decide that bandages should be rare. You do, in the XML, on purpose, with a restart you scheduled.

Edit one class, then walk to it

Loot is the mission economy, not the hostname. types.xml and the files it pulls in decide what exists. A change that "doubles guns" also doubles the argument at the coast and the time you will spend reversing it. Edit one category. Restart. Walk to a spawn you understand on Chernarus or whichever map the mission actually is. If the item is not there, the server did not load your file. Another types file in a mod is a common shadow. Mods ship their own economy. Your edit in the vanilla file will not touch their class names. Read the mod note before you tune a number that is not consulted.

Back up the file you are about to save. XML that does not parse fails the mission start, and the failure looks like a crash loop, not like a typo. A missing quote is enough. Keep the last good copy beside the profile, and restart only when the process is stopped so you are not saving under a lock. CFTools Cloud can restart the process after the file is in place. It cannot validate your XML. You do that by joining.

Publish the philosophy, not the spreadsheet. "Scarce weapons, normal food" is a sentence players can use. A dump of nominal and min values is not a rules post. If you run a vanilla flagged server, say that loot is edited or remove the word vanilla. The flag means mods, not nominals. You can be unmodded and still run a different economy. The official list is the comparison people think they are getting. Do not borrow that expectation and then spawn helicopters in every barn.

After a wipe, loot edits and persistence interact. Old items on the ground are not the new table. If you needed a clean economy, wipe persistence on purpose and say so. If you only wanted future spawns to change, say that instead. The chart on the server list will dip either way if you restart at peak. Dip at the hour you chose. Then walk the same road you walked in the test, on the live hive, before you declare the economy fixed in Discord.

Questions

Does the server list show my loot table?

No. DayZ Manager shows map, mods, players, and rules the crawler can see. Loot is inside the mission files.

Can I edit types.xml while the server is running?

The running mission will not pick up the file until you restart, and a restart in the middle of a fight should be one you announced.

Do modded items spawn automatically?

Only if the economy files know about them. Installing the mod folder is the first half.

More in this section