Skip to content
OpenTS Manual

31 — Bridge destroyed

Satisfied when a bridge span that runs through or beside the tagged cell is destroyed.

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,0

What counts as destroyed

Section titled “What counts as destroyed”

A low bridge makes its offers when a hit breaks a section of its deck. The offers cover the whole low bridge in line with that section, including sections broken earlier, so a tag anywhere along the bridge is offered the event.

A high bridge or a rail bridge makes its offers when a span collapses. A tag along a collapsing span can be offered the event several times during that one collapse, so a persistent trigger on it can fire several times even when the tag holds a single cell.

Damage that weakens a bridge but leaves its deck in place offers nothing.

Caveats
  • Only a tag placed on a map cell in [CellTags] is offered this event. A tag on an object is never offered it, even on a structure standing on the bridge.
  • Every cell tag along the destroyed span except its last cell is offered the event, wherever along the span the hit landed. On a high bridge or a rail bridge, the first cell of the span is skipped as well.
  • Tags on cells beside the span are offered the event too. For each cell of a span running along the X axis, that is the cell one step toward larger Y and the cells one and two steps toward smaller Y. For a span running along the Y axis, it is the cell one step toward larger X and the cells one and two steps toward smaller X.
  • The cells beside a skipped cell are skipped too. On a span running along the X axis, the last cell is the one with the largest X coordinate and the first cell the one with the smallest; on a span running along the Y axis, the same holds for the Y coordinate. A tag placed only on skipped cells is never offered the event.
  • A tag placed on several of these cells is offered the event at least once for each of them. A persistent trigger on that tag can therefore fire several times for one span.
  • Any offer of this event satisfies it. The event tests nothing else.
  • On a persistent tag, the event stays marked once it is satisfied, so it counts as satisfied on every later offer the tag receives.
  • A semi-persistent tag fires on this event only when exactly one object or cell holds it. The offer is not made for a particular cell, so it never removes the tag from the cells that hold it.