cfgspawnabletypes.xml

Purpose

cfgspawnabletypes.xml defines what spawns with an item when it appears in the world — its attachments, the contents of its cargo, and the damage state it spawns in. It does not control whether an item spawns or how many exist; that is types.xml. This file controls the quality and loadout of items when they do spawn.

If a weapon has no entry here, it spawns completely bare with no attachments. If a container has no cargo entry, it spawns empty.

Console Path

dayzxb_missions/dayzOffline.<mapname>/cfgspawnabletypes.xml    (Xbox)
dayzps_missions/dayzOffline.<mapname>/cfgspawnabletypes.xml    (PlayStation)

Connects To

types.xml (db/) — every name= in this file must match a classname in types.xml
cfgrandompresets.xml — preset= references point to named presets defined there

Full Block Structure

<spawnabletypes>

  <!-- Weapon with attachments and condition -->
  <type name="M4A1">
    <attachments chance="0.50">
      <item name="M4_RISHndgrd" chance="0.35" />
      <item name="M4_OEBttstck" chance="0.25" />
      <item name="M4_CQBBttstck" chance="0.20" />
    </attachments>
    <attachments chance="0.30">
      <item name="ACOGOptic" chance="0.10" />
      <item name="ReflexOptic" chance="0.20" />
    </attachments>
    <damage min="0.0" max="0.3" />
  </type>

  <!-- Container with cargo preset -->
  <type name="GunCase_Medium">
    <cargo chance="0.70" preset="MilitaryWeaponsAmmo" />
    <damage min="0.0" max="0.2" />
  </type>

  <!-- Container with inline cargo items -->
  <type name="Backpack_CoatPack">
    <cargo chance="0.60">
      <item name="BandageDressing" chance="0.50" />
      <item name="Morphine" chance="0.20" />
    </cargo>
  </type>

</spawnabletypes>

Field-by-Field Reference

`<type name="...">`

The classname of the item whose spawn package you are configuring. Must exactly match the classname in types.xml. Case-sensitive.

Only one <type> block per classname. If an item does not have an entry here, it spawns bare with engine defaults.

`<attachments chance="...">`

chance: Float 0.0–1.0
The probability this entire attachment slot group is evaluated at all. 0.50 means there is a 50% chance this block of possible attachments is even considered when the item spawns.

Multiple <attachments> blocks on the same item represent different attachment slot groups (e.g. one block for handguard/stock, another for optics). Each block is evaluated independently with its own chance.

<attachments chance="0.50">
  <item name="M4_RISHndgrd" chance="0.35" />
  <item name="M4_OEBttstck" chance="0.25" />
</attachments>

When this block fires (50% chance), the engine then rolls against each <item> inside it.

`<item name="..." chance="...">` (inside attachments)

Attribute	Type	What it controls
`name`	String	Classname of the attachment candidate
`chance`	Float 0.0–1.0	Probability this specific attachment is selected

The items inside an <attachments> block are rolled against each other. A higher chance item is more likely to be selected. The engine selects at most one item per attachment block.

Note: The chances inside a block do not need to sum to 1.0. If no item is selected (all chances fail), the slot spawns empty.

`<cargo chance="..." preset="...">`

Defines what spawns inside a container when it appears in the world.

Two forms:

1. Preset reference:

<cargo chance="0.70" preset="MilitaryWeaponsAmmo" />

chance — probability this cargo block fires at all (0.0–1.0)
preset — name of a cargo preset defined in cfgrandompresets.xml

2. Inline items:

<cargo chance="0.60">
  <item name="BandageDressing" chance="0.50" />
  <item name="Morphine" chance="0.20" />
</cargo>

Each <item> inside is rolled independently. Multiple items can be selected in the same cargo block.

Multiple <cargo> blocks can exist on one type. Each is evaluated with its own chance.

`<damage min="..." max="...">`

min: Float 0.0–1.0 — minimum damage applied on spawn
max: Float 0.0–1.0 — maximum damage applied on spawn

0.0 = pristine condition
1.0 = completely ruined

The engine picks a random value between min and max and applies it as the item’s damage state on spawn.

<damage min="0.0" max="0.3" />

This spawns the item between pristine and lightly worn.

Note: Setting both to 0.0 forces pristine spawns for that specific item, overriding the global LootDamageMin/LootDamageMax in globals.xml.

`<attachments chance="..." preset="...">`

In addition to inline <item> entries, an <attachments> block can reference a named preset instead:

<attachments chance="0.50" preset="MilitaryOptics" />

preset — name of an attachment preset defined in cfgrandompresets.xml, used the same way <cargo preset="..."> references a cargo preset.

If the referenced preset name doesn’t exist in cfgrandompresets.xml, the attachments block is silently ignored, same as a bad cargo preset=.

`<tag name="...">` and `<hoarder>`

Less commonly edited. <tag> assigns context tags that interact with loot point filtering. <hoarder> marks the item as a hoarder-class item for CE counting purposes. Leave these at their defaults in normal operations.

Additional native tokens

The native loader also recognizes unique, subcounter, batch, and equip tokens in this file’s schema. Their exact consumers and gameplay effect have not been independently traced yet — treat them as present-and-recognized, not fully documented. Avoid relying on undocumented behavior for these on a production server without testing first.

What Console Admins Typically Adjust

<damage min="..." max="..."/> — set both to 0.0 on boosted servers for pristine spawning items.
<attachments chance="..."> — raise to make fully kitted weapons more common.
<item chance="..."> inside attachments — adjust individual attachment selection rates.
<cargo chance="..."> — raise to make containers spawn more reliably pre-filled.

Safe Edit Pattern

Change damage range first — safest, lowest impact.
Raise attachment chances in small steps (e.g. 0.40 → 0.60).
Never set attachment chance to 1.0 on every item — creates guaranteed full-kit spawns across the board.
Always match the name= to an existing classname. Mismatched names are silently ignored.

Common Mistakes

Mistake	Result
`name=` doesn’t match types.xml classname	Entry silently ignored
Attachment chance `1.0` on everything	Every weapon spawns fully kitted — economy breaks
Referenced `preset=` doesn’t exist in cfgrandompresets.xml	Cargo block is silently ignored
Multiple blocks with combined high chances	Near-guaranteed full loadout items on every spawn