Jump to content

AreaFire: Difference between revisions

From ModEnc²
en>Testid123
mNo edit summary
en>Testid123
mNo edit summary
Line 12: Line 12:
==Bugs==
==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.
*'''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.
*If [[VehicleTypes]] '''(Parasite)''' uses the tag '''AreaFire=yes''' +{{f|LimboLaunch|yes|link}} on [[Primary]]+[[ElitePrimary]]+,[[Weapon1]],[[EliteWeapon1]] it will cause [[VehicleTypes]] '''(Parasite)''' to have strange attacks.<br>[[File:AreaFire=yes+LimboLaunch=yes.gif]]<br>'''AreaFire=yes+LimboLaunch=yes'''<br>

Revision as of 03:33, 12 January 2025

Tiberian Dawn Red Alert Tiberian Sun Firestorm Red Alert 2 Yuri's Revenge
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