Page 1 of 1
blockade bug
Posted: Thu May 07, 2009 8:03 pm
by ndrose
I know this has come up before, but can't remember whether it's a known, open bug or one that was supposed to have been resolved:
A blockaded AI fleet sails past the blockade without engaging it. Not only that, it happens during the land phase....
RE: blockade bug
Posted: Fri May 08, 2009 11:03 am
by MarshallEllis
Was this in the 1.06 BETA?
RE: blockade bug
Posted: Fri May 08, 2009 11:44 am
by ndrose
ORIGINAL: Marshall Ellis
Was this in the 1.06 BETA?
Yes, new game started 1.06, Grand Campaign France vs. AI.
RE: blockade bug
Posted: Sun May 10, 2009 3:28 pm
by Dancing Bear
This type of bug was reported before, but turned out not to be a bug after all. I recall that in the previous example, the fleet was booted out of a blockaded port, but the evacuated fleet was able to defeat the blockading force and procede to a second harbour, all during the land phase. Is this what happened here?
RE: blockade bug
Posted: Sun May 10, 2009 10:54 pm
by ndrose
No, it can't have been an evacuation. In this case, the French fleet was blockading London. There were no French land forces anywhere in Britain, and no reason for the fleet to have to evacuate. Also, there was no naval battle reported and no losses on either side. And the French fleet stayed where it was, in blockade. I think part of the GB fleet stayed in London while the rest went on its adventure. They are also able to move back into London freely. All those things are inconsistent with a port evacuation.
This is an old bug, and I'm pretty sure it had been fixed for a while; but it's back.
RE: blockade bug
Posted: Mon May 11, 2009 11:24 am
by MarshallEllis
Do you have that game?
RE: blockade bug
Posted: Mon May 11, 2009 11:32 am
by ndrose
I didn't save it at the time, as I thought it might be a known open bug. But I think I can recreate it, and will post it when I do.
RE: blockade bug
Posted: Mon May 11, 2009 2:23 pm
by ndrose
In the meantime, I can see that this looks to be the same as bug 325, which was indeed fixed a few versions ago. Something would seem to have undone the fix.