Skip to content

RadarEventSuppressionDistances

The cells within which a radar event swallows a later event of its kind, one entry per event kind.

Specification
Applies to
global rules
File
rules.ini
Section
[General]
Value
list of integers
When omitted
(empty)The list stays empty and one of the three suppressible kinds is used to index it anyway, dereferencing a null pointer.

Entries are positional: one per radar event kind, in the order that page lists them. Before an event is created the engine measures the straight-line cell distance from the proposed cell to every event of the same kind still in play, and drops the proposal if any of them is strictly closer than that kind’s own entry. Events stay in that scan after they have stopped being drawn, until RadarEventDurations removes them.

Only three kinds are tested this way: combat, harvester attacked and enemy sensed. The other three are always created, and the entries they would use are parsed and never read.

The distance also throttles three EVA lines across two events, because each is spoken only when its event is actually created rather than swallowed. The harvester-under-attack line follows a harvester-attacked event, raised when a harvester-type unit of the local player’s takes damage that registers a result and survives it — a killing blow raises no event and speaks no line; the cloaked- and subterranean-detected lines follow an enemy-sensed event, raised as a sensed enemy that is cloaked or underground has its blip repositioned on the radar.