ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.

DefaultToGuardArea: Difference between revisions

From ModEnc
Jump to navigation Jump to search
Testid123 (talk | contribs)
mNo edit summary
Testid123 (talk | contribs)
mNo edit summary
Line 13: Line 13:
}}
}}
This dictates that the object should always default to the AreaGuard mission rather than become idle, meaning it is always scanning for nearby targets.
This dictates that the object should always default to the AreaGuard mission rather than become idle, meaning it is always scanning for nearby targets.
Due to the fact that in this situation it automatically enters the Guard state with its Guard target being the cell under its feet, the Guard radius is calculated as 1.1 * min(2 * [[GuardRange]], 16 (4096 Leptons)) to obtain.<br>'''GuardRange from RulesMD.ini'''<br>[[File:GuardRange from RulesMD.ini.png]]<br>
Due to the fact that in this situation it automatically enters the Guard state with its Guard target being the cell under its feet, the Guard radius is calculated as 1.1 * min(2 * [[GuardRange]], 16 (4096 Leptons)) to obtain.

Revision as of 10:28, 20 January 2025

Tiberian Dawn The Covert Operations Red Alert Counterstrike Aftermath Tiberian Sun Firestorm HyperPatch Red Alert 2 Yuri's Revenge Ares Generals Zero Hour Tiberium Wars Kane's Wrath
Flag: DefaultToGuardArea
File(s): rules(md).ini
Values: Boolean values: yes or no, true or false, 1 or 0
Default: no
Applicable to: TechnoTypes:

AircraftTypes, BuildingTypes, InfantryTypes and VehicleTypes



This dictates that the object should always default to the AreaGuard mission rather than become idle, meaning it is always scanning for nearby targets. Due to the fact that in this situation it automatically enters the Guard state with its Guard target being the cell under its feet, the Guard radius is calculated as 1.1 * min(2 * GuardRange, 16 (4096 Leptons)) to obtain.