I've locked out order submissions from working for now so that I can diagnose and debug this situation. Sadly I don't have time right now.... it may need to wait until Thursday if I can't find time tomorrow. The game will look okay but any submitted orders simply won't go in. Check back on this thread for when it is going to proceed.
I've lifted the lockout.
Found three independent bugs, and (I think/hope) they are all fixed.
First, I did mess up the incoming missile detection algorithm so that it basically never thought there were ever any incoming missiles (a simple typo error). Easily fixed.
Second, I found another typo in the orders widget (that incoming transmissions tab) which might have caused non-ship owners to be unable to see when someone else's ship isn't submitting an order because they are waiting on tail information (aka the orange colour coding). Consequently, you guys, if you couldn't before, will now notice that one of the Zeta's and Bravo 1 are marked as needing tail information from someone else. This is clearly a problem, since this is the end phase and they should only be in that 'waiting' state during movement phase.....
.. leading into bug 3. I couldn't find where the "I'm tailing someone" state was being reset, so I made it a mandatory reset for all ships during the movement phase processing and cleanup. I could have manually removed the orange colour-coding from these two ships, but I've left them in as a trial. The colour code will persist through the next movement phase, and should vanish during the combat phase.
I had recently coded in missile-fired-by associations, but they seem to be mostly defaulting to null. It isn't critical to know who fired the missile except when it is a DF. I'll dig into that next, but it isn't a game-breaking bug.
Ironduke, we're waiting 100% on you now that I've unlocked the command windows again to actually function. Note that, as expected, Zeta 1 now has only evasive action as its recourse for avoiding the DF.