DefaultToGuardArea: Difference between revisions
en>DCoder No edit summary |
en>DeathFish mNo edit summary |
||
| Line 1: | Line 1: | ||
{{ | {{Flag | ||
|name={{PAGENAME}} | |||
|files={{Categ|ini=rules}} | |||
|values={{values|Booleans}} | |||
|default=no | |||
|types={{Categ|Warhead|Warheads}} | |||
|ts=yes | |||
|fs=yes | |||
|ets=yes | |||
|hp=yes | |||
|ra2=yes | |||
|yr=yes | |||
}} | |||
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. | |||
Revision as of 15:37, 10 January 2025
|
|
|
|
|
|
| Flag: | DefaultToGuardArea |
| File(s): | rules(md).ini |
| Values: | Boolean values: yes or no, true or false, 1 or 0 |
| Default: | no |
| Applicable to: | Warheads |
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.