DayZ Event Editor (events.xml)

Dynamic events are everything the Central Economy spawns on its own: helicopter crashes, vehicle spawns, animal packs, infected, fruit under trees and more. events.xml (in mpmissions/<mission>/db/) defines each event's counts, timing and behavior; cfgeventspawns.xml (in mpmissions/<mission>/) holds the fixed map positions; cfgeventgroups.xml describes multi-object sites like train wrecks.

Raise nominal on StaticHeliCrash (vanilla: 3 active at once, cycling every 35 minutes via lifetime 2100). Keep nominal well below the number of spawn positions — the community rule of thumb is two to three times more positions than nominal, because saferadius and distanceradius shrink the usable set. You can also lower lifetime so crash sites relocate more often.

The classic causes: active is 0; the event has no positions in cfgeventspawns.xml although position is fixed; nominal is higher than the usable positions; the name has no known prefix (custom events must start with Animal, Infected, Item, Static, Trajectory or Vehicle); or a child classname doesn't exist. The editor's checks flag all of these.

No. Mission files are read at server start, so a restart is enough — persistence stays untouched. Exceptions: already-spawned persistent things like vehicles keep existing until destroyed, and in local offline testing the storage_-1 folder must be deleted for changes to apply.

You can, but switching active to 0 is safer: it keeps the vanilla baseline and avoids dangling position entries. Never disable the event called Loot — it drives the entire building loot economy. The editor warns you if Loot is missing or inactive.