[Fixed] Movement Order Behavior

Started a new game with the most recent update.  I have a tiny fleet comprising one Akkan and two Cobalts.  If I give a move order in-system and then proceed to order them to instead jump to another system, the Akkan will behave normally and change its trajectory to head for the jump point and leave the system.

The Cobalts will not until they have completed their in-system move order first.  They are in a fleet with group jumping enabled.  I will attach a replay if necessary, but I think it should be easily reproducible.

I just tested further and being in or out of a fleet or having the group jump enabled or disabled does not change this odd behavior.

6,082 views 10 replies
Reply #1 Top

I've seen this too.

Reply #2 Top

I just investigated this a litte further and found out that if you designate a Cobalt in this fleet mentioned above as "Flagship" the group behaves normal. If the Akkan is flagship, the odd behaviour of "Cap jumping alone, leaving the Cobalts in the grav well" occurs.

Reply #3 Top

I've read a lot about the colonizer cap ships causing issues with fleets. It might be the colonize ability that is causing bugs.

Reply #4 Top

@Mazuo: Your best bet is to send the replay and the exact steps to reproduce directly to [email protected] :)

Reply #5 Top

I've had something like this happen as well. Playing as TEC with a small starting fleet of a couple of cobalts and an Akkan (although it carried on when the fleet was bigger), after phasing to a new planet with group move on, all of my cobalts then proceded to phase jump to the boundary of the 45 degree phase in area. I'll try to get a screenshot if it helps, or should I email the save file?

Reply #6 Top

I'll try to get a screenshot if it helps, or should I email the save file?
End of quote

They really need to see it in action, so save or replay would be best :) And you can just e-mail it to their support at the above addy.

Reply #8 Top

Been busy irl, will go ahead and find the right save file and send it off.

Edit:  Alright, it's been sent off.  Couldn't get the problem to reoccur in my original game for whatever reason, but creating a new one allowed me to immediately reproduce it.

Reply #10 Top

Great to hear.  Danke Blair.