ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
GuardRange: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Aaagh! Will people please stop simply adding stuff to Deezire entries - Deezire entries MUST be REWRITTENwith the template REPLACED! |
||
Line 1: | Line 1: | ||
{{ | {{flag | ||
|types={{Categ|Technoes}} | |||
|values={{values|integer}} | |||
|default={{TTL|Range}} 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, {{TTL|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). |
Revision as of 08:06, 16 August 2008
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: | Template:TTL 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, Template:TTL 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).