AttackingAircraftSightRange: Difference between revisions
en>Crimsonum Un-Deezire'd |
Rain-Islet (talk | contribs) m [bot] Batch update {{Bugs}} templates. |
||
| (One intermediate revision by one other user not shown) | |||
| Line 12: | Line 12: | ||
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. | 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}} | =={{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}}: | 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}}: | ||
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.