Flagships are able to use asteroids as waypoint in time machine which will be generated by Genesis in the future. This can cause a dangerous issue: waypoints change.
Current case which let to discovery: we wanted to send our flagship to another nearby sector using one of the new asteroids as waypoints, action was planned a few hours ago. In the meantime we - as well as our enemy - generated new asteroids, but it is still time for this command to come on. So when I now forward in TM our flagship is send across the whole map to the sector where the enemy created some asteroids.
I faced it twice today, first it was another roid in our own sector as we edited our Genesis commands. There I saw no huge issue, I was more like irritated a bit. But now with enemy asteroids causing it as well, I feel like reporting. If we would have been to bed now with no one checking we would wake up to our FS being halfway on-route to the enemy.
I could imagine it is a similar reason which leads to failing chain ray orders: each asteroid gets a consecutive but not unique number. So let's say my Genesis is generating asteroids 32 and 33. And we send FS to roid 33. In the meantime some one else uses Genesis and creates roids 32 and 33 somewhere else. FS command still says 'use asteroid 33' and sends it wherever asteroid 33 is.
White Star AGQ-5120
I cannot keep it in TM. But think it can be reproduced as mentioned above.
#Flagship waypoints change after genesis
toxic badger
swift geode
This is probably a similar issue to the chain ray linking issue. IE: time machine orders set by list position order rather than using an object uuid.