Config Settings XML Format

cfgeconomycore.xml

Governs the core mechanics of the dynamic loot economy, including event triggers, loot respawn logic, and global economy parameters.

Overview

The cfgeconomycore.xml file is the backbone of the DayZ Central Economy (CE). It defines how the server manages loot spawning, cleanup cycles, and economy parameters. This file is located in the server's mission folder and is loaded at startup.

Changes to this file require a server restart. It references other economy files (like types.xml) and controls how frequently the CE processes spawns and despawns.

File Structure

The root element contains CE file references and economy classes that define global parameters.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<economycore>
    <ce folder="db">
        <file name="types.xml" type="types" />
        <file name="spawnabletypes.xml" type="spawnabletypes" />
        <file name="globals.xml" type="globals" />
        <file name="economy.xml" type="economy" />
        <file name="events.xml" type="events" />
        <file name="messages.xml" type="messages" />
    </ce>
    <classes>
        <rootclass name="Economy" setupaliasaliases="" />
    </classes>
</economycore>

Key Settings

Spawn Intervals

The CE processes item spawns in cycles. Each cycle evaluates which items need to be spawned based on their nominal and min values in types.xml. The spawn interval determines how often the CE checks for items below their minimum threshold.

Cleanup Timing

Items that exceed their lifetime value are flagged for cleanup. The CE periodically removes these items to free spawn slots. Cleanup timing affects server performance — shorter intervals mean more frequent processing but faster item turnover.

CE Cycle Parameters

The economy cycle runs continuously, evaluating spawn points, checking item counts, and managing the dynamic loot pool. Key cycle parameters include the initial delay before the first cycle runs and the interval between subsequent cycles.

Configuration Options

Element / Attribute	Description	Default
ce folder	Root folder for economy data files, relative to the mission directory.	db
file name	Filename of the economy data file to load.	—
file type	Type identifier: `types`, `spawnabletypes`, `globals`, `economy`, `events`, `messages`.	—
classes	Defines root economy classes and their aliases for the CE system.	—
rootclass name	Name of the root economy class. Typically `Economy`.	Economy

Adding Custom CE Files

You can split your types into multiple files by adding additional <file> entries. This is common when using mods or organizing loot by category.

<economycore>
    <ce folder="db">
        <file name="types.xml" type="types" />
        <file name="types_weapons.xml" type="types" />
        <file name="types_clothing.xml" type="types" />
        <file name="types_trader_mod.xml" type="types" />
        <file name="spawnabletypes.xml" type="spawnabletypes" />
        <file name="globals.xml" type="globals" />
        <file name="economy.xml" type="economy" />
        <file name="events.xml" type="events" />
        <file name="events_custom.xml" type="events" />
        <file name="messages.xml" type="messages" />
    </ce>
    <classes>
        <rootclass name="Economy" setupaliasaliases="" />
    </classes>
</economycore>

Best Practices

• Split types by mod or category — Keep vanilla types.xml separate from mod types files. This makes updates easier and reduces merge conflicts.
• Back up before editing — A malformed cfgeconomycore.xml will prevent the server from starting. Always keep a working backup.
• Validate XML syntax — Ensure all tags are properly closed and attributes are quoted. Use an XML validator before deploying.
• Order matters for duplicate types — If the same classname appears in multiple type files, the last loaded file wins. Be mindful of file order.
• Use consistent folder structure — Keep all CE files in the db folder or a clearly named subfolder referenced by the ce folder attribute.

Deployment Checklist

Confirm file paths

Every referenced file should exist relative to the configured CE folder.

Validate XML

A malformed economy core file can stop the server from loading economy data.

Keep custom files named clearly

Use names like types_expansion.xml or events_custom.xml.

Watch the first restart

Check RPT output after deployment for missing files, XML parse failures, or duplicate classname warnings.

Troubleshooting

Symptom	Likely fix
Loot stops spawning	Check missing file references, XML syntax, and whether types files are registered as type="types".
Custom event file is ignored	Make sure it is listed with type="events" and deployed in the referenced folder.
Duplicate type behavior is confusing	Search all registered types files for the classname and keep one authoritative entry.
Server starts but CE logs errors	Read the first RPT errors after startup; they usually name the missing file or malformed XML line.