DayZ Central Loot Economy Settings: How to Change

Updated 7 November 2026 · Standard formula, shown below

This guide explains how to adjust the central loot economy (CLE) on a DayZ server, which controls what items spawn, where they spawn, and how often. You’ll edit the cfgeconomycore.xml file and related loot tables, then reload the economy so your changes take effect. You’ll need file access to your server’s installation folder and a text editor like Notepad++.

What You’ll Need

Access to your DayZ server’s root directory (via FTP or a hosting control panel).
A text editor that handles XML well, such as Notepad++ or VS Code.
Basic understanding of XML syntax (tags, attributes, values).
Ability to restart or run console commands on your server.

Step-by-Step

Locate the economy files. Navigate to DayZServer/MPMissions/dayzOffline.chernarusplus/ (or the map you’re using, e.g., dayzOffline.deerisle). Inside you’ll find cfgeconomycore.xml, cfgeventspawn.xml, cfgloottable.xml, and cfgloottypes.xml.
Back up the original files. Copy all four XML files to a safe location on your computer. This lets you revert if something goes wrong.
Open cfgeconomycore.xml. This is the main file that controls global spawn rates, lifetime, and cleanup. You’ll see sections like <economy>, <spawn>, and <cleanup>.
Adjust global spawn rates. Inside <spawn>, find attributes like spawnmax (maximum number of items in the world), spawnmin (minimum before new spawns trigger), and lifetime (how long an item stays before despawning). For example, to make loot more scarce, lower spawnmax from 5000 to 3000.
Modify item lifetime. In the same <spawn> section, change lifetime to a lower value (e.g., 1800 seconds) to make items disappear faster, or higher to keep them longer. This affects server performance and loot cycling.
Edit cfgloottable.xml for specific item spawns. This file defines which items appear in which loot types (e.g., military, civilian, food). Open it and find a loot type like <type name="military">. Inside, you’ll see <item name="AKM" /> entries. Add or remove items, or change their nominal and min values to control frequency.
Change loot type probabilities. In cfgloottable.xml, each loot type has a nominal attribute (average count in the world) and min (minimum before respawn). Increase nominal for more of that type, decrease for less.
Adjust rarity in cfgloottypes.xml. This file maps loot types to categories (e.g., <type name="military">) and sets their spawn weight. Lower the nominal value for rare items like NVGs to make them harder to find.
Save all files. After editing, save each XML file with UTF-8 encoding (no BOM). Ensure you don’t introduce XML syntax errors.
Reload the economy. On a running server, type #reload in the server console. If you can’t, restart the server entirely. The changes will apply after the reload or restart.
Verify changes. Log into the game and check if loot spawns as expected. Use the in-game debug monitor (if enabled) or check server logs for errors.

Common Mistakes

Editing the wrong files. Some hosts use a different folder structure (e.g., dayzOffline.chernarusplus vs dayzOffline.chernarus). Double-check the path.
Forgetting to back up. A single typo can break the entire loot system. Always keep backups.
Setting values too extreme. Setting spawnmax to 0 or lifetime to 1 will make the server nearly empty or cause constant respawning, hurting performance.
Not using UTF-8 encoding. Special characters in XML can cause parsing errors if saved in the wrong encoding.
Ignoring the <ceiling> and <floor> values. These in cfgloottable.xml set hard limits per item; if you raise nominal above ceiling, it won’t work.

Tips

Start with small changes (e.g., 10% reduction) and test before making big adjustments.
Use the official DayZ Wiki’s loot table reference to understand item categories and IDs.
If you want different loot on different maps, copy the entire mission folder and edit each separately.
Use a tool like Notepad++’s XML Tools plugin to validate your XML before uploading.
Consider using a mod like ‘LootRespawn’ if you need more granular control than vanilla CLE offers.

Troubleshooting

Loot doesn’t change at all: You likely edited the wrong file or didn’t reload the economy. Verify the file path and run #reload again. If using a hosting panel, ensure you’re editing the live server’s files, not a local copy.
Server crashes on startup: XML syntax error. Check the server log (usually server_console.log) for the line number of the error. Revert to backup and redo changes carefully.
Items spawn but disappear instantly: Lifetime is too low. Increase lifetime in cfgeconomycore.xml to at least 600 seconds.
Only some items spawn: The ceiling and floor values in cfgloottable.xml might be conflicting. Set ceiling higher than nominal and floor lower than min.
Changes reset after restart: Some hosts overwrite mission files on restart. Check your hosting control panel for a ‘sync’ or ‘restore’ option and disable it.

Frequently Asked Questions

Do I need to edit all four XML files?

Not always. For basic scarcity, cfgeconomycore.xml is enough. For specific item spawns, you’ll need cfgloottable.xml and cfgloottypes.xml. cfgeventspawn.xml is for dynamic events like heli crashes.

What does ‘nominal’ mean in loot tables?

It’s the target number of that item or category that should exist in the world at any given time. The server tries to maintain this number.

Can I make loot spawn more often without changing amounts?

Yes, lower the lifetime in cfgeconomycore.xml. Items despawn faster, so new ones spawn to replace them, increasing turnover.

Will these changes affect server performance?

Yes, extreme values can cause more frequent respawn checks and higher CPU usage. Keep spawnmax reasonable (e.g., 3000-10000) and avoid setting lifetime below 300 seconds.

How do I reset the economy to default?

Delete the storage_1 folder inside your server’s mpmissions directory (or the equivalent) and restart. This clears the current loot state and forces a fresh spawn based on your XML files.

Is there a way to test changes without restarting?

Yes, use the #reload console command. It reloads the economy files without a full restart, though some changes may require a restart to take full effect.

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