-
Notifications
You must be signed in to change notification settings - Fork 33
flagging weapons
This specification was automatically generated from a feature request imported into Ares's LaunchPad bugtracker. If you are interested in fleshing out this feature, please update this page.
Currently, if a unit attacks any object, other units of the same type aren't forbidden from attacking it too. The only exception to this are Yuri Disk's draining weapons (which somehow forbid other disks from draining the same building) and mind-control weapons (as objects, due to obvious reasons, won't try to mind-control something that is already mind-controlled). The idea of this feature is to make something similar available for all TechnoTypes/weapons (it doesn't matter for me whether if it will be a TechnoType or a weapon tag).
There should be 2 'variations' of this logic available: a 'timed flag' and an 'on-fire flag'. Timed flag has a limited time duration, that renews after being fired at. This is mostly for EMP, Psychedelic and possibly modifier weapons, so other units won't try attack a target that already been affected by such. On-fire flag simply prevents other objects of the same type (or firing the same weapon) from attacking the target as long as the 1st attacker is still firing its weapon on it.
Perhaps there will be no need for 2 variations, and only 'timed flag' will be enough, as long as it won't prevent the 1st attacker from firing its weapon on the target while the flag lasts.
The reasoning behind this feature is both to improve the AI a bit without dabbling too much with the way it handles targets, and make micro-managing for some weapons easier. An example could be creating an AI version of an EMP beam unit utilizing this logic, which would give an illusion micro-managing multiple targets my the AI, forcing each of unit to attack a separate target at the same time (and if the mod creator sees it appropriate, make it so for the player version too).
- This needs to be filled by a supporter/drafter of this specification.
- This needs to be filled by a supporter/drafter of this specification.
- Original request by mevitar/mevitar
- Imported request at LaunchPad
- Blueprint meta-data at LaunchPad