Skip to content

Destroy triggers and tags at the end of the frame

Changes0.1.0 (in development)

FixedPlanned for 0.1.0

Destroying a trigger or a tag now marks it and lets the frame finish before the object is freed, which is how everything else in the scenario logic retires an object. The two actions used to free each match immediately while still walking the list they were freeing from, so a map that destroyed several at once could read past the end of that list, and a trigger or tag that destroyed its own type pulled itself out from under the action that was still running. A marked trigger stops springing the moment the action runs, so the point at which a map stops seeing it is unchanged.

Affected entities

Credit: ZivDero, tomsons26