AttackingAircraftSightRange: Difference between revisions

Latest revision as of 17:10, 2 July 2025

Flag:	AttackingAircraftSightRange
File(s):	Rules(md).ini
Values:	Unsigned integers: All non-negative whole numbers from 0 to either 32767, 2147483647 or 4294967295.
Applicable to:	General

Default to aircraft sight range when the aircraft is in an attack mission. Effectively obsolete, as the sight range is overriden by the aircraft type's Sight value.

Bugs/Side-Effects/Unexpected Limitations

In Red Alert 2, using a value too high causes spawned missiles to reveal the map, as warned by this developer comment in rules(md).ini:

AttackingAircraftSightRange=2 ; //gs 6 Makes the V3 ping the map. Hi, welcome to dumb ideas.

@@ Line 1: / Line 1: @@
-{{DeeZireInclusion}}<br />
+{{Flag
-Sight range, in cells, that an aircraft is considered to have when in an attack mission.
+|name={{PAGENAME}}
+|files={{Categ|Rules(md).ini}}
+|values={{Values|unsigned integers}}
+|types={{Categ|General}}
+|ts=yes
+|fs=yes
+|ra2=yes
+|yr=yes
+}}
+Default to aircraft [[sight]] range when the aircraft is in an attack mission. Effectively obsolete, as the sight range is overriden by the aircraft type's {{f|Sight|link}} value.
+=={{bugs}}==
+In {{ra2}}, using a value too high causes [[Spawned_Missiles|spawned missiles]] to reveal the map, as warned by this developer comment in {{ini|rules}}:
+ AttackingAircraftSightRange=2 ; //gs 6 Makes the V3 ping the map. Hi, welcome to dumb ideas.
+<!--Apparently I have to insert text here for the above template to work.-->