Wiki Navigation

Configuration File
XML Format

cfgLimitsDefinition.xml Configuration

Define spawn limits for item categories in your DayZ server. Control the maximum number of items per category to balance gameplay and optimize server performance.

Overview

The cfgLimitsDefinition.xml file defines global spawn limits for different item categories. It controls the maximum number of items per category that can exist in the world, helps maintain balance between loot types, and optimizes server performance by limiting total item counts.

File Structure

The file contains <categories> to define available categories and <limits> to set maximum counts.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<lists>
    <categories>
        <category name="weapons" />
        <category name="magazines" />
        <category name="food" />
        <category name="tools" />
        <category name="clothes" />
    </categories>
    <limits>
        <limit name="weapons" value="120" />
        <limit name="magazines" value="250" />
        <limit name="food" value="400" />
        <limit name="clothes" value="500" />
    </limits>
</lists>

Category Parameters

name string

The name of the category. This must exactly match the category names used in types.xml for items to be properly tracked against limits.

Limit Parameters

name string

The name of the category to apply the limit to. Must match a category defined in the categories section.

value integer

The maximum number of items in this category that can exist in the world at once. When reached, no more items of this category will spawn until some are removed.

How It Works

The cfgLimitsDefinition.xml file works in conjunction with types.xml to control item spawning. Items in types.xml are assigned to categories using the <category> tag, and this file sets global limits for each category.

Category Assignment

Items in types.xml reference categories defined here. Each item can belong to one category that determines which limit applies.

Spawn Checking

When the server spawns items, it checks category limits. If a limit is reached, no more items of that category spawn until some are removed.

Dual Constraints

Individual item limits (nominal values in types.xml) still apply, but category limits provide an additional global constraint across all items in that category.

Performance Impact

Lower limits reduce server load by limiting total item counts. Higher limits allow more items but may impact performance on busy servers.

Common Categories

weapons

Firearms, melee weapons

magazines

Ammo magazines

attachments

Weapon attachments

food

Food and drinks

tools

Tools and equipment

containers

Backpacks, cases

clothes

Clothing items

vehiclesparts

Vehicle components

Best Practices

Recommended

  • Balance limits based on your server's player count and performance
  • Set higher limits for essential items like food and lower for high-tier weapons
  • Monitor server performance and adjust limits accordingly
  • Keep category names consistent with types.xml references

Avoid

  • Setting limits lower than the sum of minimum values in types.xml
  • Extremely high limits that could impact server performance
  • Mismatched category names between this file and types.xml
  • Defining limits for categories that don't exist

Example Configuration

Balanced Server

Standard limits for a typical survival experience

<lists>
    <categories>
        <category name="weapons" />
        <category name="magazines" />
        <category name="food" />
        <category name="tools" />
        <category name="clothes" />
        <category name="containers" />
    </categories>
    <limits>
        <limit name="weapons" value="150" />
        <limit name="magazines" value="300" />
        <limit name="food" value="500" />
        <limit name="tools" value="400" />
        <limit name="clothes" value="600" />
        <limit name="containers" value="200" />
    </limits>
</lists>

Pro Tips

Calculate your category limits by summing the nominal values of all items in that category from types.xml, then add a buffer of 10-20%. This ensures the economy can function properly while maintaining the intended item distribution. Use server logs to monitor which categories hit their limits frequently and adjust accordingly.