Jump to content

Cloakable: Difference between revisions

From ModEnc²
ATHSE (talk | contribs)
first pass
ATHSE (talk | contribs)
testing final
Line 26: Line 26:
The {{f|CloakStop|yes|link}} tag was added to keep a unit like the Attack Sub cloaked when firing or in ambush position.
The {{f|CloakStop|yes|link}} tag was added to keep a unit like the Attack Sub cloaked when firing or in ambush position.


{{Bugs}}
In RA2, a fully cloaked submarine might still reveal itself when retaliating (enabled by {{f|CanRetaliate|yes|link}}), or if the target of attack is sufficiently far away from it.


{{Bugs}}
[[Hover|Hovering]]/Flying units do not support Cloakable=yes, however granting them cloakability via [[VeteranAbilities]] or [[EliteAbilities]] is possible.
*Setting this flag on unit which higher than ground will doesn't work, however granting them cloakability via {{f|VeteranAbilities|link}} or {{f|EliteAbilities|link}} does.
*Ares has removed this hardcode, allowing the definition of the height for determining cloakable, and defaults it to the value of [[HoverHeight]] located under [General], used by hovering units. Therefore by default, just having Ares enables the logic for hovering units, and requires additional configuration to return to vanilla game behaviour.
<ref name="ares fixed">[[Ares]] has removed this hardcode, allowing the definition of the height for determining cloakable, and defaults it to the value of [General] > [[HoverHeight]]= used by hovering units.</ref><br>
*'''Cloakable=no''' will not work if [[TechnoTypes]] Gain abilities. '''Cloaking''' via {{f|VeteranAbilities|link}} and {{f|EliteAbilities|link}}<br>
*Although <u><b>[[InfantryTypes]]</b></u> There will be <u><b><font style="color:#4169E1">Cloakable=yes</font></b></u><br>
But when <u><b>[[InfantryTypes]]</b></u> get ordered to attack the target far away <u><b>[[InfantryTypes]]</b></u> will periodically reveal itself. until reaching the goal<br>
*Causes [[InfantryTypes]],[[VehicleTypes]] to receive the attack cursor[[TechnoTypes]] even though they cannot actually attack (If the warhead is determined to attack It will attack normally).<br>[[File:Dog and Cloakable=yes.gif]]


<references/>
Explicitly set Cloakable=no will still be overridden if a unit gains the abilities through [[Veterancy|promotion]].
That is to say, as long as you use [[Ares]], even if you don't make any changes, you can allow Hover units to use this logic normally.<br>
Of course, you can also use the new keys to disable it to maintain the same effect as their work in {{yr}}


==See also==
==See also==

Revision as of 12:00, 10 April 2025

Tiberian Dawn Red Alert Tiberian Sun Firestorm Red Alert 2 Yuri's Revenge
Flag: Cloakable
File(s): Rules(md).ini
Values: boolean
Default: no
Applicable to: InfantryTypes,VehicleTypes,BuildingTypes


Specifies whether this object has a cloaking device, which can render it invisible to enemy units without Sensors=yes, or buildings without SensorArray=yes. This effect also applies to the mini-map, which will only show the revealed (uncloaked) state of the unit.

In Tiberian Sun

Strangely, despite TechnoTypes lacking Sensors=yes, they can still automatically attack units that have Cloakable=yes within range, as if there was no cloaking effect.

Unlike in later games, TS (and Firestorm) support Cloakable and CloakingSpeed tags on buildings, without any problems.

In Red Alert 2

Earlier games did not have submarines, and so the cloaking effect only applied to terrestrial units, but in RA2 the cloaking system was repurposed for the Soviet Attack Sub. As such, the sound effects were updated to reflect their aquatic nature, with the splash effect played defined by CloakSound under AudioVisual, played for both cloaking and decloaking.

The CloakStop=yes tag was added to keep a unit like the Attack Sub cloaked when firing or in ambush position.

Bugs/Side-Effects/Unexpected Limitations In RA2, a fully cloaked submarine might still reveal itself when retaliating (enabled by CanRetaliate=yes), or if the target of attack is sufficiently far away from it.

Hovering/Flying units do not support Cloakable=yes, however granting them cloakability via VeteranAbilities or EliteAbilities is possible.

  • Ares has removed this hardcode, allowing the definition of the height for determining cloakable, and defaults it to the value of HoverHeight located under [General], used by hovering units. Therefore by default, just having Ares enables the logic for hovering units, and requires additional configuration to return to vanilla game behaviour.

Explicitly set Cloakable=no will still be overridden if a unit gains the abilities through promotion.

See also

CloakingStages

Sensors

SensorArray

RadarInvisible