-
Notifications
You must be signed in to change notification settings - Fork 33
proposal of radical alteration of paradrop code
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.
Since the Paradrop code does little else than create a group of player-owned units inside an aircraft, then assigns that aircraft to "attack" at the designated drop zone, would it not be possible to use radically different combinations of task forces to be called up by Superweapons? For example, a SW could, when fired, create a group of infantry or other units entering from outside the map, just like in Paradrop, but without the plane, or with another type of transport, and with a "Move" com assigned to the target location of the SW. To define the group called for, such a superweapon could use tags akin to those used in AI.ini for taskforces, and maybe could also have a tag for the action to perform at the destination. This would give modders a great deal of freedom and would remove the need for seperate "Airstrike", "Paradrop" and "Spyplane" logic - each of these could simply be the same SW, but "Airstrike" calls in a taskforce of, say, two bombers, with the action "Attack" assigned, while "Paradrop" would call in some infantry inside a transport plane, with the transport assigned attack, while a "Spyplane" would just call for a spyplane with the action "Move" assigned, etc.
- 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 Millennium/kotaka
- Imported request at LaunchPad
- Blueprint meta-data at LaunchPad