Event Connector Not Triggering Groups Properly

For my fighter craft to dock with a carrier I have the thrusters grouped so they can all be turned off by the connector event. This works. Unfortunately, whenever one fighter disconnects they all turn on. And I would think that an event controller should only be monitoring its connector it was told to watch, and since this is a connector event, once the fighter disconnects only its thrusters should turn on.

However, I had a solution for this. I placed an event controller on the carrier to monitor all carrier connectors and whether a fighters connects or disconnects it is set to turn all craft thrusters off. That worked. Though, it made the craft event controllers halfway redundant. But the latest state of the game has the carrier connectors event failing to catch the craft thrusters. They are staying on and fowling the carrier.

I hope you might test this yourself and see what I mean. Two craft sharing a thruster group in the terminal, docking to the same grid will switch them off, but launching just one switches both back on. I already think that should be wrong for the connector event, and I am not using the on/off toggle. At each stage I am using the all off or all on command.

I'd first like to hear that you can find the problem of why the carrier's event controller solution stopped working and that it can be fixed. I would also think that a disconnecting craft shouldn't be causing this kind of problem to begin with seeing as the command to turn the thrusters on should be given by the fighter disconnecting so that even though other thrusters share the terminal group they shouldn't have a chance to communicate.

Thank you.