SpySat
SpySat is an ini flag introduced from Red Alert 2 for buildings, but in the Phobos extension, there is also an early projectile statement named SpySat used to reveal the entire map for the house to which the invoker belongs. Starting from Phobos DevBuild#47, the latter has been reimplemented and renamed to Reveal to allow defining the reveal range. When it is -1, it is equivalent to the original SpySat=yes.
- For the native SpySat from Red Alert 2, please read below.
- For the latest status of that function in the Phobos extension, please refer to the Phobos documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | SpySat |
| File(s): | rules(md).ini |
| Values: | Boolean values: yes or no, true or false, 1 or 0 |
| Default: | no |
| Applicable to: | BuildingTypes |
Specifies whether the building is a SpySat Uplink, with the effect of revealing all areas on the map for its owner, except those covered by Allied Gap Generator ([GAGAP]).
Notes
This flag is not inclusive with Radar=yes, you need to add them separately.
Starting from Phobos Build#46, SpySat=yes can grant a building through upgrading buildings.
Bugs/Side-Effects/Unexpected Limitations
This does not check whether the building itself is in working status, meaning that this function is not affected by Powered=yes and TogglePower.
This is incompatible with FogOfWar and ShroudGrow.
- For the former, it may cause entities on the map not to display, and its effects may also be overridden by the latter unless all buildings with SpySat=yes are first turned off and then re-enabled.
Event 4 (maybe 5 too) is irreversibly bugged for the remainder of the mission if the player built a SpySat=yes building; only a mission restart fixes it.
The interaction between SpySat and GapGenerator leads to an inconsistent shroud state, which in turn leads to desync.
- This bug has been fixed in Phobos Build#49.