31 — Bridge destroyed
Satisfied when a span of bridge that includes or borders the tagged cell is brought down.
Editor data
- Numeric ID
31- Engine ID
TEVENT_BRIDGE_DESTROYED- Editor name
- Bridge destroyed
- Need token
NEED_NONE- Parameters
- None
- Attachment
- cell
INI example
[Events]
<TriggerID>=1,31,0,0What counts as destroyed
Section titled “What counts as destroyed”The offers are made where a run of bridge is actually taken out of use, and that is a different moment for each kind of bridge. A low bridge makes them at the damage step that replaces its deck with the destroyed state, having first measured the run of low bridge cells either side of the one that was hit. A high bridge and a rail bridge each make them as the collapse reaches the end of a span, and the collapse then carries on into the next span, which makes its own offers in turn.
Damage that only scars a bridge, leaving the deck in place, offers nothing.
Caveats
- The offer reaches map cells only. No object's tag is ever offered this event, so a tag riding on a structure standing on the bridge receives nothing.
- The whole span is measured before the offers are made, so a tag anywhere along the run is sprung wherever along it the damage landed.
- The cell at one end of the span is passed over. The walk stops on reaching it, so a tag placed on the eastmost cell of an east-west span, or the southmost cell of a north-south span, is never offered the event.
- The offer covers a band beside the span as well as the span itself. Along an east-west span each cell offers the event to its own tag, to the tag one cell south, and to the tags one and two cells north; along a north-south span, to its own tag, to the tag one cell east, and to the tags one and two cells west.
- The event carries no test of its own beyond needing an offer that names it, so any offer that reaches the tag satisfies it.
- The event describes a moment, so a persistent trigger marks it off the first time it arrives and treats it as satisfied from then on.