Know which DayZ files a custom event really needs

events.xml defines what the event spawns, its target counts, lifetime, radii, flags, position mode, limit and children. cfgeventspawns.xml gives the identically named event one or more coordinates and optional rotations. The event name must match exactly, including capital letters.

DayZ event names normally begin with a supported purpose such as Vehicle, Static, Loot, Item, Infected or Animal. The child type must be a real classname from the selected map and game version. Do not turn a display name into a guessed classname.

cfgeventgroups.xml is needed when an event uses an event group rather than a simple child spawn. mapgroupproto.xml is relevant when a spawned building or group needs loot-position prototype data. A simple infected or animal event does not automatically need fabricated entries in all four files.

Nominal and min control the event target, while child min and max control what each event instance can contain. Review limit and position modes alongside fixed spawn points. Contradictory values can produce no spawns or far more entities than the server can handle.

Spawn positions are map-specific. Use X and Z from the selected Chernarus, Livonia or Sakhal map and use the angle for orientation when it matters. Four castle points on Chernarus cannot be copied into a Sakhal mission and expected to work.

Insert the new records without deleting unrelated live entries. Parse every changed XML file, compare matching event names across the package and check referenced classes. After upload and restart, use RPT evidence to confirm the server accepted and spawned the event.