Cloakable - Revision history

Rain-Islet: [bot] Batch update {{Bugs}} templates.

2025-07-02T15:15:47Z

[bot] Batch update {{Bugs}} templates.

← Older revision		Revision as of 17:15, 2 July 2025
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}}		=={{Bugs}}==
	In RA2, a fully cloaked unit (presumably 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.		In RA2, a fully cloaked unit (presumably 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.

Askhati: Undo revision 28432 by AuY (talk) - this key does in fact work on buildings too (at least in TS).

2025-04-22T07:17:19Z

Undo revision 28432 by AuY (talk) - this key does in fact work on buildings too (at least in TS).

← Older revision		Revision as of 09:17, 22 April 2025
Line 4:		Line 4:
	\|values=boolean		\|values=boolean
	\|default=no		\|default=no
	\|types={{Categ\|InfantryTypes}},{{Categ\|VehicleTypes}}		\|types={{Categ\|InfantryTypes}},{{Categ\|VehicleTypes}},{{Categ\|BuildingTypes}}
	\|ra=yes		\|ra=yes
	\|cs=yes		\|cs=yes

AuY at 14:17, 19 April 2025

2025-04-19T14:17:25Z

← Older revision		Revision as of 16:17, 19 April 2025
Line 4:		Line 4:
	\|values=boolean		\|values=boolean
	\|default=no		\|default=no
	\|types={{Categ\|InfantryTypes}},{{Categ\|VehicleTypes~~}},{{Categ\|BuildingTypes~~}}		\|types={{Categ\|InfantryTypes}},{{Categ\|VehicleTypes}}
	\|ra=yes		\|ra=yes
	\|cs=yes		\|cs=yes

ATHSE at 12:07, 12 April 2025

2025-04-12T12:07:19Z

← Older revision		Revision as of 14:07, 12 April 2025
Line 31:		Line 31:
	Explicitly set <tt>Cloakable=no</tt> will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].		Explicitly set <tt>Cloakable=no</tt> will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

	[[SpeedType\|Hovering]]/Flying units do not support Cloakable=yes, however granting them cloakability via [[VeteranAbilities]] or [[EliteAbilities]] is possible.		[[SpeedType\|Hovering]]/Flying units do not support <tt>Cloakable=yes</tt>, 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.		* 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.

ATHSE at 12:06, 12 April 2025

2025-04-12T12:06:19Z

← Older revision		Revision as of 14:06, 12 April 2025
Line 17:		Line 17:

	==In {{ts}}==		==In {{ts}}==
	Strangely, despite [[TechnoTypes]] lacking {{f\|Sensors\|yes\|link}}, they can still automatically attack units that have Cloakable=yes within range, as if there was no cloaking effect.		Strangely, despite [[TechnoTypes]] lacking {{f\|Sensors\|yes\|link}}, they can still automatically attack units that have <tt>Cloakable=yes</tt> 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.		Unlike in later games, TS (and [[Firestorm]]) support <tt>Cloakable</tt> and [[CloakingSpeed]] tags on buildings, without any problems.

	==In {{ra2}}==		==In {{ra2}}==
Line 29:		Line 29:
	In RA2, a fully cloaked unit (presumably 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.		In RA2, a fully cloaked unit (presumably 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.

	Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].		Explicitly set <tt>Cloakable=no</tt> will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

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

ATHSE at 12:05, 12 April 2025

2025-04-12T12:05:01Z

← Older revision		Revision as of 14:05, 12 April 2025
Line 27:		Line 27:

	{{Bugs}}		{{Bugs}}
	* In RA2, a fully cloaked unit (presumably 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.		In RA2, a fully cloaked unit (presumably 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.

	* Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].		Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

	* [[SpeedType\|Hovering]]/Flying units do not support Cloakable=yes, however granting them cloakability via [[VeteranAbilities]] or [[EliteAbilities]] is possible.		[[SpeedType\|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.		* 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.

	* Cloaked units will not trigger / activate ~~celltags~~ on maps. This was an intentional design choice from Westwood, ~~as per~~ analysis of the engine code ~~(per Rampastring work)~~.		Cloaked units will not trigger/activate [[Celltags]] on maps. This was an intentional design choice from Westwood, according to analysis of the engine code.

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

Askhati at 12:54, 10 April 2025

2025-04-10T12:54:28Z

← Older revision		Revision as of 14:54, 10 April 2025
Line 27:		Line 27:

	{{Bugs}}		{{Bugs}}
	In RA2, a fully cloaked unit (presumably 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.		* In RA2, a fully cloaked unit (presumably 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.

	Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].		* Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

	[[SpeedType\|Hovering]]/Flying units do not support Cloakable=yes, however granting them cloakability via [[VeteranAbilities]] or [[EliteAbilities]] is possible.		* [[SpeedType\|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.		** 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.

			* Cloaked units will not trigger / activate celltags on maps. This was an intentional design choice from Westwood, as per analysis of the engine code (per Rampastring work).

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

ATHSE: still

2025-04-10T10:09:54Z

still

← Older revision		Revision as of 12:09, 10 April 2025
Line 29:		Line 29:
	In RA2, a fully cloaked unit (presumably 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.		In RA2, a fully cloaked unit (presumably 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.

	Explicitly set Cloakable=no will ~~still~~ be overridden if a unit gains the abilities through [[Veterancy\|promotion]].		Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

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

ATHSE: move again

2025-04-10T10:08:42Z

move again

← Older revision		Revision as of 12:08, 10 April 2025
Line 27:		Line 27:

	{{Bugs}}		{{Bugs}}
			In RA2, a fully cloaked unit (presumably 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.

	Explicitly set Cloakable=no will still be overridden if a unit gains the abilities through [[Veterancy\|promotion]].		Explicitly set Cloakable=no will still be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

	~~In RA2, a fully cloaked unit (presumably 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.~~

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

ATHSE: moved bug

2025-04-10T10:07:16Z

moved bug

← Older revision		Revision as of 12:07, 10 April 2025
Line 27:		Line 27:

	{{Bugs}}		{{Bugs}}
			Explicitly set Cloakable=no will still be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

	In RA2, a fully cloaked unit (presumably 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.		In RA2, a fully cloaked unit (presumably 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.

	[[SpeedType\|Hovering]]/Flying units do not support Cloakable=yes, however granting them cloakability via [[VeteranAbilities]] or [[EliteAbilities]] is possible.		[[SpeedType\|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.		*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 [[Veterancy\|promotion]].~~

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

← Older revision		Revision as of 12:09, 10 April 2025
Line 29:		Line 29:
	In RA2, a fully cloaked unit (presumably 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.		In RA2, a fully cloaked unit (presumably 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.

	Explicitly set Cloakable=no will ~~still~~ be overridden if a unit gains the abilities through [[Veterancy\|promotion]].		Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy\|promotion]].

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