End Turn and autopilot accidently attacking an ally

I was in a Huge map game and had established an alliance with all but one civilization. I proceeded to conquer this last race. With only one planet left in their pocession, they admitted their defeat and turned the planet over to me. Knowing that I had won an alliance victory, I simply hit the "End Turn" button.
Unfortunately, one of my ships that was on autopilot was set to end it's turn in a sector containing one of my ally's ships. A message informing me of this fact appeared so I clicked the "Done" button thinking I would be taken to my ship so I could adjust it's path. Instead, I got into an endless loop of trying to end the turn and getting the warning message about my ship attacking an ally.
I finally had to kill the game through the Windows task manager.
Another one to add to the list.
6,020 views 8 replies
Reply #1 Top
Happens to me too, but I just hit no, and that's it. It never went into a big deal about it. The ship just wouldn't move to that parsector. The game didn't freeze, but that probably is a quark in the game.
Reply #2 Top
I thought this was one of the things they fixed in the latest patch? Try right clicking REALLY quickly away from the ship after clicking done.
Reply #3 Top
I get that in 1.2 Beta 1. Not sure if it happened before.

I click 'cancel' (or whatever the don't do it button is) repeatedly and quickly maybe 20 times. The box goes away having ended the ship's turn without combat and forfeiting the rest of the ship's movement. No biggie, but a bug. The pop-up warning should only trigger once, then kick in some error handling routine if it tried to pop up twice in a row based on the same trigger.

Reply #4 Top
+ Fixed bug if a ship was on auto-explore and passed into a tile with another ship the “Are you sure you want to declare war” message would keep popping up infinitely


From the 1.2 Beta 2 change log...
Reply #5 Top
+ Fixed bug if a ship was on auto-explore and passed into a tile with another ship the “Are you sure you want to declare war” message would keep popping up infinitely


From the 1.2 Beta 2 change log...


I'm using 1.2b and it's still happening
Reply #6 Top
It is only a beta verison. I'd wait until the final release of 1.2 before getting to hasty in sending those error reports. Will just make Stardock aware that this is still popping up, and needs some farther work to be resolved by the next beta release or complete verison of 1.2.
Reply #7 Top
The POINT of a "beta" release is for people to report errors.

That is a highly annoying bug. If it's not been fixed, they need that to be reported.
Reply #8 Top
I'm using 1.2b and it's still happening


Which 1.2 beta? There's a new one out.