Skip to content
OpenTS Manual

25 — Crosses Horizontal Line...

Satisfied when an object of the named house reaches any cell in the row of cells the tag sits in.

Editor data
Numeric ID
25
Engine ID
TEVENT_CROSS_HORIZONTAL
Editor name
Crosses Horizontal Line...
Need token
NEED_HOUSE
Parameters
  1. Househouse
Attachment
cell
INI example
[Events]
<TriggerID>=1,25,0,<House>

What the line is made of

Section titled “What the line is made of”

Each tagged cell whose tag watches for a horizontal crossing draws a line along its row. Each time an infantry or vehicle finishes moving into a cell on such a line, every tag in that row that watches for a horizontal crossing is offered the event.

The offer does not depend on the direction of travel or on which side the object came from. Every step that ends on a cell of the line makes an offer. This includes an object that started the scenario on the line and moves along it.

The row covers the whole map rectangle, including cells outside the playfield. Those extra cells change nothing, because objects cannot reach them.

A tag whose triggers watch for a horizontal crossing draws its row and never its column, even if the same tag also watches for a vertical crossing. Crosses Vertical Line… describes the effect on the vertical event.

Valid values

  • A house by number, either a country or a [spawn house](/formats/scenario-objects/#spawn-houses). A spawn house names whoever holds that start position. The test compares the house with the owner of the object that moved.
  • The no-house value, -1, skips that comparison, so an object of any house satisfies the test.
Caveats
  • A named house that is not in play, or a start position that nobody holds, never matches, so the event is never satisfied.
  • The row is every cell with the same Y coordinate as the tagged cell, from edge to edge of the map rectangle, the square of cell coordinates that encloses the playfield. The cell grid's axes run diagonally on screen, so the row runs from upper left to lower right, not horizontally.
  • Two tags in one row that both watch for a horizontal crossing are both offered the event by a single crossing.
  • A tag listed against several cells of one row is offered the event once for each of those cells. A persistent trigger on such a tag can fire that many times for a single crossing.
  • Only a tag placed on a cell in [CellTags] draws a line, and the lines are drawn once, when the scenario is read. A tag that rides only on an object is never offered this event.
  • A fully cloaked object makes no offer.
  • Once satisfied, the event stays marked as satisfied, whatever the tag's persistence. A persistent trigger holding only this event therefore fires on every later offer the tag receives, including a crossing by an object of any house.
  • Satisfying the event also marks each temporal event written before it on the trigger's [Events] line that is satisfied during the same offer, as [remembering a satisfied event](/systems/trigger-springing/#remembering-a-satisfied-event) describes.