Weirdness with cycling orders:
I have a freighter taking infrastructure from Earth to Mars on infinite loop. Orders are
Refuel at Earth
Load infrastructure at Earth
Unload infrastructure at Mars
in that order (with the cycle button checked). On the system map (F3) the ship shows at about 1/2 way back to Earth, and both F3 and F12 claim 2:11:05 as an ETA. I wanted to change over to carrying construction factories, so started to delete the last two orders. The first time I hit the Remove button though I get a pop-up "The current order is still being carried out and has & 0:00:49 time remaining. Are you sure you wish to delete it?" Note that I just restarted Aurora after going out to dinner, so whatever's messed up is probably in the DB.
My prime suspect here is that Aurora is mixing up orders between my freighter and one of the civies (there's one at Mars right now).
The message (which is badly formatted and I have now fixed that particular issue) should appear if you attempt to delete a partly completed order that requires the passage of time, such as load/unload or surveying, etc.. In this case an order with 49 minutes remaining. I haven't seen it appear in the situation above but I will do some testing. Did you by any chance press yes to the delete and see if the order disappeared?
As far as I can tell from the code, the check is performed on the last order in the queue and it applies to the active fleet only. The active fleet is set when you select it on the window. It's a straightforward piece of code so I don't think the problem lies there. Perhaps the active fleet is somehow being changed. I'll get back to you on this one.
Steve
Yes I pressed yes, and yes it disappeared - I'm not sure that it disappeared in the correct order though.
You might want to look for a similar bug (object vs. DB) to the one described above for civies - this feels like the same "duplicate sequence number" issue, even though I didn't have any special orders set. OTOH, I did have the "repeat in a loop" flag set, which might go through a similar piece of special processing code. It's possible that my freight did an entire "lap" of its order queue, in a single update, which ISTR gets handled in a difference branch of the code, which in turn might be generating a duplicate sequence number.
I think I've only seen this one time in my ships (as opposed to the civie freighter bug you discussed above), so whatever it is I suspect it might be a weird corner case.
John