GuardRange: Difference between revisions
en>DCoder No edit summary |
m 4 revisions imported |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{flag | ||
|types={{Categ|Technoes}} | |||
|values={{values|integer}} | |||
|default={{f|Range|link}} of the unit's [[Primary#Current_Primary_Weapon|current primary weapon]] | |||
|ts=yes | |||
|fs=yes | |||
|ets=yes | |||
|ra2=yes | |||
|yr=yes | |||
}} | |||
Specifies the range, in cells, that this unit will scan for targets to attack. | |||
As a special case, {{f|GuardRange|link}} is also used to determine the 'auto-fill' wall placement distance; the number of cells between which a new wall can be connected to an existing wall (assuming there are no obstructions). | |||
Latest revision as of 21:45, 31 March 2025
|
|
|
|
|
|
| Flag: | GuardRange |
| File(s): | rules(md).ini |
| Values: | Signed integers: All whole numbers from -2147483648 to 2147483647; in rare cases, only from -32768 to 32767. |
| Default: | Range of the unit's current primary weapon |
| Applicable to: | TechnoTypes:
AircraftTypes, BuildingTypes, InfantryTypes and VehicleTypes |
Specifies the range, in cells, that this unit will scan for targets to attack.
As a special case, GuardRange is also used to determine the 'auto-fill' wall placement distance; the number of cells between which a new wall can be connected to an existing wall (assuming there are no obstructions).