DeployFire: Difference between revisions
en>Testid123 mNo edit summary |
m 5 revisions imported |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
|name={{PAGENAME}} | |name={{PAGENAME}} | ||
|files={{Categ|ini=rules}} | |files={{Categ|ini=rules}} | ||
|types={{Categ|Technoes}} | ;;|types={{Categ|Technoes}} | ||
|types={{Categ|InfantryTypes}},{{Categ|VehicleTypes}} | |||
|values={{values|unsigned integers}} | |values={{values|unsigned integers}} | ||
|default=1 | |default=1 | ||
Latest revision as of 21:40, 31 March 2025
|
|
|
|
|
|
| Flag: | DeployFire |
| File(s): | rules(md).ini
|
| Values: | Unsigned integers: All non-negative whole numbers from 0 to either 32767, 2147483647 or 4294967295. |
| Default: | 1 |
| Applicable to: | InfantryTypes,VehicleTypes |
Can be set to 'yes' or 'no' and determines if this unit can be given the 'deploy' order, which will cause it to fire the weapon determined by DeployFireWeapon at the ground underneath itself.
Notes
- For infantry units, the ART(MD).INI sequence should also specify which frames of its image sequence are to be used when it is deployed. If this is omitted, the unit will be unable to deploy if ordered to.
- For Ra2 This tag cannot be used with VehicleTypes