Jump to content

Selectable: Difference between revisions

From ModEnc²
en>Mevitar
spawnable aircraft should not have Selectable=no set
en>Mevitar
mNo edit summary
Line 16: Line 16:
Usually this is combined with uncontrollable objects and/or spawns, to prevent the player from selecting objects that they should not have control over. Examples include the V3 Rockets and Dreadnought Missiles (the actual missiles, not their launcher units).
Usually this is combined with uncontrollable objects and/or spawns, to prevent the player from selecting objects that they should not have control over. Examples include the V3 Rockets and Dreadnought Missiles (the actual missiles, not their launcher units).


== Bugs ==
{{Bugs}}
Adding ''Selectable=no'' to spawned [[AircraftTypes]] with aircraft [[Locomotor]] randomly causes them to fly over the map border instead of landing, and thus crashing the game.
Adding ''Selectable=no'' to spawned [[AircraftTypes]] with aircraft [[Locomotor]] randomly causes them to fly over the map border instead of landing, and thus crashing the game.


== See Also ==
== See Also ==
*{{f|IsSelectableCombatant|link}}
*{{f|IsSelectableCombatant|link}}

Revision as of 16:19, 11 August 2014

Tiberian Dawn Red Alert Tiberian Sun Firestorm Red Alert 2 Yuri's Revenge
Flag: Selectable
File(s): rules(md).ini
Values: Boolean values: yes or no, true or false, 1 or 0
Default: yes
Applicable to: TechnoTypes:

AircraftTypes, BuildingTypes, InfantryTypes and VehicleTypes



Set Selectable=no to an object that should not be selected by the player.

Usually this is combined with uncontrollable objects and/or spawns, to prevent the player from selecting objects that they should not have control over. Examples include the V3 Rockets and Dreadnought Missiles (the actual missiles, not their launcher units).

Bugs/Side-Effects/Unexpected Limitations Adding Selectable=no to spawned AircraftTypes with aircraft Locomotor randomly causes them to fly over the map border instead of landing, and thus crashing the game.

See Also