Crewmember?

[Nosie_old]

[attachmentid=829]
<img src="style_emoticons/<#EMO_DIR#>/hi.gif" style="vertical-align:middle" emoid=":gday" border="0" alt="hi.gif" /> Pirates,
This one is a real beauity and I have not expirienced this one before!
What you see in this picture is the french Battlefleet in Greenfort Harbor.
After the capture off Oxbay Harbor I used the 'sail to" icon and after arrival
I used the 'moore" icon. The Battlescreen came up, you know where the crewmember
cries ship ahoy, get ready for Battle. But I did not have time to click anything and that's
the Crewmember you're looking at, instead of my trusted Blaze (Nathaniel).
The Screen is partly frozen, everything moves except that Crewmember and I had to get
back to the Desktop! I'll bet, you can't top that one! <img src="style_emoticons/<#EMO_DIR#>/whistling.gif" style="vertical-align:middle" emoid="" border="0" alt="whistling.gif" /> <img src="style_emoticons/<#EMO_DIR#>/dunno.gif" style="vertical-align:middle" emoid="" border="0" alt="dunno.gif" />

 

[Lorati]

That already happened at me once. A little bit weird.

When I sailed to FdF with 'Sail to' option. I got that SailHo screen, but I already started to moore before, and I didn't click anything. And when I was in the port, that character was my first mate.

 

[Thomas the Terror]

I think that was part of a mod of somebody made. In the oxbay quest your first mate, is send, because you are too welknown? I am not sure.

 

[Nosie_old]

<img src="style_emoticons/<#EMO_DIR#>/poet.gif" style="vertical-align:middle" emoid=":hmm" border="0" alt="poet.gif" /> I played the same again and it did not happen.
There are a lot of bugs with the ships ahoy screen and in
my oppinion should be taken out, since it only creates
problems!!!! The dialog is crappy too and was reported by me
earlier. There used to be lots of freezes etc. <img src="style_emoticons/<#EMO_DIR#>/whistling.gif" style="vertical-align:middle" emoid="" border="0" alt="whistling.gif" />

 

[Pieter Boelen]

I encountered this bug as well. Several times, actually. There is a delay between the moment when the player gives the "anchor" command and the time the anchoring is actually done. If a Direct Sail update is triggered during this delay, this bug occurs. I think there is an idea to make Direct Sail updates only occur far from islands, so that should solve this particular problem.