ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
AreaFire: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
(3 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
{{ | {{flag | ||
|values={{values|Boolean}} | |||
|default=No | |||
|types={{Categ|Weapon|Weapons}} | |||
|ra2=yes | |||
|yr=yes | |||
|rp=yes}} | |||
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. | |||
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. | |||
==Bugs== | |||
*'''AreaFire=yes''' makes [[Primary]],[[ElitePrimary]] unable to actually attack. If the target is further than the attack range, [[TechnoTypes]] will attempt to move towards it. But when that goal is found The attack cursor will now be changed to a NoMove cursor instead. |
Latest revision as of 01:39, 22 December 2024
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. 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.
Bugs
- AreaFire=yes makes Primary,ElitePrimary unable to actually attack. If the target is further than the attack range, TechnoTypes will attempt to move towards it. But when that goal is found The attack cursor will now be changed to a NoMove cursor instead.