Wiki Navigation

Configuration File
XML Format

cfgeconomycore.xml Configuration

Configure the Central Economy system's core behavior, dynamic event settings, and logging options for debugging and monitoring your server's loot system.

Overview

The cfgeconomycore.xml file controls the Central Economy's core mechanics. It manages dynamic event parameters (spawn radius, timing, and distances), logging options (for debugging loot spawns, cleanups, and events), and startup behavior (whether to save events and types on server start). This file is essential for fine-tuning economy performance and troubleshooting spawn issues.

File Structure

Each <default> element sets a named parameter with its value.

<defaults>
    <default name="dyn_radius" value="30" />
    <default name="dyn_smin" value="0" />
    <default name="dyn_smax" value="0" />
    <default name="dyn_dmin" value="1" />
    <default name="dyn_dmax" value="5" />
    <default name="log_ce_loop" value="false"/>
    <default name="log_ce_dynamicevent" value="false"/>
    <default name="save_events_startup" value="true"/>
    <default name="save_types_startup" value="true"/>
</defaults>

Dynamic Event Settings

dyn_radius integer

The radius in meters around dynamic events where items can spawn. Larger values spread loot over a wider area around crash sites and other events. Default is 30 meters.

dyn_smin integer

Minimum spawn distance from the event center. Items won't spawn closer than this distance. Set to 0 to allow spawns at the exact event location.

dyn_smax integer

Maximum spawn distance from the event center. Works with dyn_smin to create a spawn ring. Set to 0 to use dyn_radius as the maximum.

dyn_dmin integer

Minimum delay in seconds before a dynamic event can trigger after conditions are met. Prevents events from spawning too quickly in succession.

dyn_dmax integer

Maximum delay in seconds for dynamic event triggering. The actual delay is randomized between dyn_dmin and dyn_dmax for variety.

Startup Settings

save_events_startup boolean

When enabled, the server saves the current events.xml state on startup. Useful for preserving event configurations but can slow startup on large servers. Recommended to keep enabled.

save_types_startup boolean

When enabled, the server saves the current types.xml state on startup. Helps preserve loot configurations and can aid in debugging economy issues. Recommended to keep enabled.

Logging Parameters

Enable these options temporarily for debugging. Keeping them enabled permanently can impact server performance and generate large log files.

log_ce_loop boolean

Logs each Central Economy processing loop. Generates high volume output. Use only for deep debugging of economy timing issues.

log_ce_dynamicevent boolean

Logs dynamic event spawns like helicopter crashes and airdrops. Useful for verifying events are triggering correctly.

log_ce_vehicle boolean

Logs vehicle spawn and despawn events. Helpful for debugging vehicle economy and tracking vehicle counts.

log_ce_lootspawn boolean

Logs every loot spawn event. Extremely verbose - use sparingly. Helpful for tracking down why specific items aren't spawning.

log_ce_lootcleanup boolean

Logs when items are cleaned up by the economy system. Useful for understanding item lifetime behavior and cleanup cycles.

log_ce_lootrespawn boolean

Logs loot respawn events when items are regenerated. Helps debug restock timing and respawn rate issues.

log_ce_statistics boolean

Logs economy statistics periodically. Provides overview of item counts and economy health. Lower impact than other logging options.

log_ce_zombie boolean

Logs zombie spawn and despawn events. Useful for debugging infected population issues and spawn rate problems.

log_hivewarning boolean

Logs warnings from the hive database system. Recommended to keep enabled to catch database synchronization issues early.

Best Practices

Recommended

  • Keep hive and mission file warnings enabled for early problem detection
  • Enable statistics logging temporarily to monitor economy health
  • Test dynamic event timing changes on a staging server first
  • Keep save_events_startup and save_types_startup enabled

Avoid

  • Leaving verbose logging (lootspawn, loop) enabled in production
  • Setting dynamic event delays too low (causes event spam)
  • Disabling hive warnings (masks critical database issues)
  • Making multiple changes at once without testing each

Pro Tips

When debugging economy issues, enable logging options one at a time to isolate the problem. Start with log_ce_statistics for an overview, then drill down with more specific options. Remember to disable verbose logging after debugging to maintain server performance. Dynamic event timing affects player experience significantly - shorter delays create more action but can make rare loot too common.