AreaFire: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 10: | Line 10: | ||
{{bugs}} | {{bugs}} | ||
Due to the way the logic is handled, [[InfantryTypes|infantry]] can use such weapons only as their deploy weapon | Due to the way the logic is handled, [[InfantryTypes|infantry]] can use such weapons only as their deploy weapon, otherwise, they will not fire it at all. If the <tt>AreaFire</tt> weapon is the [[Primary]] or [[ElitePrimary]], the unit may approach the target, and then do nothing. | ||
Using <tt>AreaFire</tt> on a {{f|LimboLaunch|yes|link}} weapon, may result in the unit returning to its original cell immediately, before detonating the warhead. | Using <tt>AreaFire</tt> on a {{f|LimboLaunch|yes|link}} weapon, may result in the unit returning to its original cell immediately, before detonating the warhead. | ||
Revision as of 13:51, 11 April 2025
|
|
|
|
|
|
| Flag: | AreaFire |
| File(s): | rules(md).ini |
| Values: | Boolean values: yes or no, true or false, 1 or 0 |
| Default: | No |
| Applicable to: | Weapons |
Setting this tag to 'yes' causes this weapon's Warhead to be detonated at the cell currently occupied by the firer, instead of firing the weapon at the target.
Bugs/Side-Effects/Unexpected Limitations
Due to the way the logic is handled, infantry can use such weapons only as their deploy weapon, otherwise, they will not fire it at all. If the AreaFire weapon is the Primary or ElitePrimary, the unit may approach the target, and then do nothing.
Using AreaFire on a LimboLaunch=yes weapon, may result in the unit returning to its original cell immediately, before detonating the warhead.