Not sure if bug or oversight: multiple docking ports in the same action group

[allmhuran]

Say you build a ship with multiple docking ports, perhaps added with symmetry, which you want to undock all at once at some later time. Maybe you're doing a multi-port connection for a stronger construction, or maybe you're self docking, or, well, any number of reasons.

Easy, right? Action groups to the rescue. Just assign an action group to "undock node"... or... wait... should that be decouple node? And which of the docking ports should you assign to the action group? After all, a docking connection takes two ports.

Ah, there's the rub. There doesn't seem to be any way to know which port will need to be "undocked" (or "decoupled"). And, unfortunately, if you assign *all* the ports to undock (and decouple?) via the action group then it doesn't work, because *some* of the ports can't be undocked, and this seems to cause the whole action group to fail.

Long story short, I think the undock/decouple action should be merged (there does not seem to be a good reason to have two functions that seem like they should be one), and also, please, please, allow the action group to undock whichever nodes can be undocked when multiple ports are put into the same group.

Edited September 29, 2015 by allmhuran