59 — Reduce Tiberium At...
Strips the waypoint's own cell of Tiberium and leaves every cell around it exactly as it was.
Editor data
- Numeric ID
59- Engine ID
TACTION_REDUCE_TIBERIUM- Editor name
- Reduce Tiberium At...
- Need token
NEED_WAYPOINT- Parameters
- Waypoint
waypoint
- Waypoint
- Attachment
- none
INI example
[Actions]
<TriggerID>=1,59,0,0,0,0,0,0,<Waypoint>[Actions]DemoThin=1,59,0,14,0,0,0,0,O ; trigger DemoThin empties waypoint 14, whose label is OThe number 14 is the waypoint whose cell the action empties. The trailing O is the same waypoint written as its label, in the field an editor fills in.
A reduction takes one level off the cell. A reduction of a cell already at its lowest level takes the Tiberium away altogether, restores the cell’s passability, and puts the eight cells around it back in line for a spread pass. Every reduction left in the pass then finds nothing there and does nothing.
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 a reduction around the waypoint. Nothing outside the waypoint's own cell is ever touched.
- That one cell is reduced once for every cell lying within five of the waypoint, which is 109 reductions of a level apiece, so it is emptied however deep the Tiberium in it was.
- Emptying a cell puts the eight cells around it back in line for a spread pass, so a field left with growth switched on closes the hole up on its own.
- 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.