Skip to content
OpenTS Manual

63 — Apply 100 damage at...

Stages five separate 100-point blasts around a waypoint and brings down a bridge span there.

Editor data
Numeric ID
63
Engine ID
TACTION_DAMAGE
Editor name
Apply 100 damage at...
Need token
NEED_WAYPOINT
Parameters
  1. Waypointwaypoint
Attachment
none
INI example
[Actions]
<TriggerID>=1,63,0,0,0,0,0,0,<Waypoint>

The five blasts

Section titled “The five blasts”

The first blast is centered on the waypoint. The other four are offset a third of a cell along each axis, one toward each diagonal, and each carries its own 100 points through the same warhead. Every blast gathers what stands in its own cell and the eight around it and scales the damage by distance, so the five overlap heavily and an object at the waypoint is hit by all of them in the same frame.

The height is the cell’s own ground height, raised by the bridge height where a bridge covers or has covered the cell, so a waypoint under a bridge is struck at deck level rather than on the ground beneath it.

map file
[Actions]
DemoDamage=1,63,0,12,0,0,0,0,M ; trigger DemoDamage detonates at waypoint 12, whose label is M

The number 12 is the waypoint the action acts on. The trailing M is the same waypoint written as its label, in the field an editor fills in.

The bridge

Section titled “The bridge”

After the blasts, the action tries up to four times to bring down a bridge span in the waypoint’s cell, then marks the surrounding area for redraw. The attempt is made on every firing and does not depend on the blasts having found anything; a waypoint with no bridge over it simply has nothing to take down.

Valid values

  • A scenario waypoint. The action reads it from the waypoint number the line carries, not from the waypoint name at the end of the line.
Caveats
  • The editor text describes one blast of 100 damage. Five are staged, each of 100 in its own right, so anything standing at the waypoint takes all five with only the falloff between them to tell them apart.
  • The warhead is C4Warhead from the rules rather than a fixed high-explosive one, so retuning that setting retunes this action.
  • A bridge span over the waypoint is brought down as well, whether or not the blasts found anything to damage.
  • The number field is where the engine writes this waypoint as well as where it reads it, so the number a line carries there survives the engine writing the scenario out again. The name at the end of the line is written from a separate field, which is the one an editor is prompted to fill in and the one that the actions reading a waypoint from the end of the line work from.
  • No firer is recorded, with the same consequences as a scripted explosion — no points, no anger, no veterancy, and no Destroyed by any house event on what the blasts destroy.