Build updated. The 'next intentions' does something now , but doesn't autoupdate. That's going to take a lot more work than I expected, but it'll be worth it I think. Oh, if you don't have anything targeted, it (should) get the attackers of yourself; should I make a separate control for that?
A couple small but frustrating to track down bugs remain. For one, please test the function of these commands in a nebula with limited awacs.
I'd commit this already if it didn't modify the pilot files. I think I should ask permission from the leaders.
GREAT. I'm going to download and test it now with the famous "A game of TAG" and the SOC mission where you have to find your mate through nav buoys.
OTOH, I would split it because I, (and I suppose most of the people too), have Auto-targeting always enabled so I nearly never have no active target AND attackers on my own. (In fact I fairly use "Target Nearest Target's Attacker")
EDIT ----------------
Impressions with your new build:
1. GREAT work.
2. One bug. It shows the orders for all targeted ships even enemy ones (within these ones it should be hidden).
3. Other issue. The first time you press it, it keeps your actual target (or no one if you haven't) and only multitargets the attackers. At the second press and next ones, it leaves the current target (which should have happened from the begining) and cycles through the multitargeted group.
(I didn't notice before that your new multitarget commands cycled through the group. I don't know if it is a new feature or I was just asleep
)
4. I've tried it within "A Game of TAG" and I haven't found any other crashes or bugs:
4.1. I have left Alpha 2 fighting with the mara wing (which also engages alpha) and I've flown more than 15 Km away (more than radar range for detection of last virgo wing at least). Multi-targeting attackers keeps working but I can normally target every ship even at this distance, (once you have detected a ship it seems you can always target it even if you are far far away).
4.2. When the last virgo wing arrives, and it isn't shown in radar, it can't target Lucity or any other ship (due an actual FSOpen bug). So I can't check "Multi-target attackers" over this ship. (It just doesn't do anything).
If you have some problematic mission and steps to make it crash or detect bugs, please post and I will try it.
5. Which logic does the code use to select the "attackers"?
I will use an example. I have used FSPort 3.0 "The darkness and the light". I have ordered my wing (3 ships) to attack the Aten cruiser (I don't remember its name, let's call it ATEN). Then ATEN shows 3 red dots in its HUD target box. When my wing reaches ATEN, its cover fighters defend it so you can see how ATEN has only 2 dots, then 1 dot and finally 0 dots because my wing is disengaging ATEN to defend themselves. Through all this time, "Multitargeting ATEN's attackers" always select my full wing. I do feel this is the right behaviour because all of them have the order of attack ATEN even if they're not doing it just at the moment.
But then I order my wing to "Engage enemy", so it means no orders AFAIK. In this situation if I target the ATEN it can have zero, one, two or three dots but the "Multitarget ATEN's attacker's" action doesn't select that exact number of fighters from my wing. Sometimes they're the same but other times they're not.
So, how do you build the group of attackers?
I continue testing... (But not today)