Skip to content
OpenTS Manual

43 — Meteor Impact At...

Drops one voxel debris type onto a waypoint and plays the meteor storm warning.

Editor data
Numeric ID
43
Engine ID
TACTION_METEOR_IMPACT
Editor name
Meteor Impact At...
Need token
NEED_METEOR_AND_LOCATION
Parameters
  1. Meteor sizemeteor-size
  2. Waypointwaypoint
Attachment
none
INI example
[Actions]
<TriggerID>=1,43,0,<Meteor size>,0,0,0,0,<Waypoint>

The piece is created at the waypoint’s ground height, raised by the bridge height where a bridge covers or has covered the cell. What happens next is entirely a property of the type dropped: a debris type set to fly in as a meteor is placed back along its approach and comes down onto the waypoint, and one that is not simply appears there and is thrown about by the ordinary debris physics.

A stock rules tree registers ten entries under [VoxelAnims], of which the two meteors sit at positions 7 and 8. Nothing the action supplies distinguishes them; they are two separate debris types, and how each falls and how hard it lands are settings on those types. The list is counted from zero even though the shipped keys are numbered from one, because a registration list is read by position and its key text decides nothing.

rules.ini
[VoxelAnims]
1=PIECE      ; position 0
2=TIRE       ; position 1
; ...
8=METEOR01   ; position 7
9=METEOR02   ; position 8

Valid values

  • A position in the rules [VoxelAnims] list, counted from 0, and a scenario waypoint.
Caveats
  • The size setting is a position in the rules voxel debris list rather than a size. Whatever is registered at that position is dropped, so the same number means different things in two rules trees, and adding, removing or reordering a [VoxelAnims] line shifts every number already stored in a map.
  • The position is used without a range check. One at or beyond the end of the list reads past it.
  • The warning is spoken whichever piece is dropped, including one that is not a meteor at all.