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. How it arrives depends on the type dropped:

  • A type set to fly in as a meteor starts back along its approach and comes down onto the waypoint.
  • Any other type appears at the waypoint and is thrown about by the ordinary debris physics.

The stock rules register ten entries under [VoxelAnims]. The two meteors, METEOR01 and METEOR02, are at positions 7 and 8. They are separate debris types, and how each falls and how hard it lands are settings on those types.

The list is counted from zero, although the stock keys are numbered from one. 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 Meteor size parameter is a position in the rules [VoxelAnims] list, not a size. Whatever is registered at that position is dropped, so the same number drops different debris under two different rules files. 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 meteor storm warning is spoken whichever piece is dropped, including one that is not a meteor.