I think it could work where all members of the group hear every command issued regardless of which subgroup it is issued to. The subgroup the command is relevant to could be specified by adding it to the end of the audio.

For example:
"Attack target, wing 2" or
"Status? wing 1"

Likewise, the subgroup issuing the command could preface the audio when it pertains to the issuer:

"Wing 1 engaging target"

The advantage to doing it this way is that all group members would be aware of what's going on, even if the commands don't necessarily pertain to them. My preference would be to do it this way. What are other people's thoughts? Would this be too confusing? too busy? I suppose anyone could just read the commands from group chat if the audio were only played for the relevant subgroup.

On a related note, having a different voice for each subgroup would be AWESOME. If enough people were to volunteer to lend their voices for such an effort, I think I could even be persuaded to record a set of the voice commands for one of the subgroups...

Here is an update that partially enters phase 2. You can now set which subgroup you belong to, but it has no impact on anything really. I still need to come up with a mechanism to indicate the members of each subgroup.

I cleaned up the messages output to group chat to make them look prettier and added a few new commands, the most significant of which is the plot course command (v-4-3). It displays to group chat the route you have mapped when you execute it, but I figured it might be annoying if it actually changed the designated subgroup(s) route to match. Any thoughts?

Here is the list of commands to date:

v-1 Offence
1 - Attack primary target: @%target% (Set primary target --NYI)
2 - Attack secondary target: @%target% (Set secondary target --NYI)
3 - Open fire
4 - Engage at will
5 - UNUSED

v-2 Defense
1 - Defend: @%target% (set target to defend --NYI)
2 - Evaisive maneuvers --i.e. survive as long as you can
3 - Hold Position
4 - Break off and regroup
5 - Retreat

v-3 Recon
1 - Hostile spotted: %target% --target is optional (may be out-of range)
2 - Sector Clear
3 - UNUSED
4 - UNUSED
5 - Storm!

v-4 Mission
1 - Return to objective
2 - Repair and reload
3 - Begin bomb run (initiates 3 second countdown --implemented)
4 - Plot Course: <NavRoute> (Set nav route to match player issuing command --NYI)
5 - What is your status?

v-5 Personal
1 - I'm engaging: @%target%
2 - I'm taking fire from multiple bogies
3 - I need a target
4 - I'm out of ammo
5 - Help me!

Any changes people would like to see to the commands? Note that there are still some unused slots. I don't particularly like the wording of v-5-2 but am unable to think of anything better.

Use (or bind) the command /gc to open or close the list of commands.

GroupCommand v0.2.0a