DefaultToGuardArea: Difference between revisions
en>Testid123 mNo edit summary |
m 7 revisions imported |
||
| (One intermediate revision by one other user not shown) | |||
| 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. | 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. | ||
Latest revision as of 21:40, 31 March 2025
|
|
|
|
|
|
| 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.