Remove the router from your system and see if that helps performance. If it does then you may need to upgrade the firmware or change the configuration.

The log errors are interesting but what is most interesting is what kind of errors you are having right before you get disconnected. You should open a new support ticket with a client log from when you get booted.

That should be San Juan. We'll fix that.

That said, the guy in San Juan doesn't offer the turning for the Spanish Priest either. We'll fix that too.

Please file a support ticket. Include your latest PotBS log from My Documents\Pirates of the Burning Sea.

There's a (relatively rare) bug in the Windows TCP stack (perhaps limited to particular network cards or their drivers) where one side of a connection has gone away but the other side still thinks it's connected. I've seen this behavior in a number of programs, including tools built into Windows. There are a few things we can do to detect this case, but none of them are particularly good solutions, adversely affecting the more common case where the connection is actually fine. The issue still comes up in conversation every once in a while, but honestly we have not put a high priority on this.

I remember that, it sucked big time! As Frank said, we do have a system that allows reconnecting in this manner; it's a bug if it didn't work for you.

Okay, we found it. There are four prisoners who don't have ransom-for-gold missions:

British Scholar
Dutch Envoy
French Scholar
Spanish Priest

You can turn in these four for faction, but not for gold. We will fix this in a patch soon. The other prisoner types should be ransomable for gold.

So you get the message and can still get into the game? To get more details on the problem I recommend reading the section on wireshark from KB article 36 and submitting the info in a support ticket so we can track it.

FYI, we have found this bug and fixed it. It was a code issue that got the spawn table math wrong in some cases, which would result in incorrect ships being spawned. This issue is solved in v1.1, which is coming shortly after launch.

We have a system that lets you log back into your disconnected character. I've seen a very rare case where a client could not log back in although I could not reproduce it.

Please file a support ticket for this issue with you client log and the time the incident happened. Also, post the incident number here.

We absolutely cannot.

What you're asking for is that we trust the client to tell us when it's okay to start fighting. We never trust the client because the client can be hacked. If we let the client say "Hey, I'm all set!" people will hack the client to not ever say that, so they can keep boarding going forever.

Believe me, if we actually could trust that the client was unhackable, MMO development would be a million times easier.

I've asked our QA people to test boarding combat load times on minspec hardware and see what they find. It's been a while since we looked at that and it may be that we can reduce the 45 second timer.

That said, I don't believe the 45 second timer is that significant of an issue. The ability of players to run in circles around the deck extending combat is much more of a concern for me.

Overall, we consider boarding-to-immobilize to be a valid tactic and we are not going to put a complete stop to it. But that said, we expect boarding combats to proceed as intended: players fight until somebody wins. Exploiting that to prolong the fight by not fighting isn't something we want to support and we are discussing how to resolve this.

Sorry, I misspoke. The 30% ship buff during boarding is damage reduction. That means all damage applied to your ship is reduced by 30%. That's what is currently live in the game.