My wife is new to the game. Wanted the 20+ chest achievement. x3 hours of work and multiple enemy ships sunk we managed to scratch together 12 golden chickens, 20+ gunpowders, and 19 chests (Several were Captain Chests), and a bunch of skulls. Over roughly 10k worth of loot and rep on board. We're on our way to our last chest and BLAM - loading screen - the server crashes...
We lost everything...again. When is this going to get fixed! She is now hanging up her pirate hat for the day if not permanently.
This is not the first time this has happened to us, but it may be the last. (At least for her)
What's going on with the unstable servers?
Is there not a way RARE can set it up so you can get some sort of recovery when there is a disconnect, especially if it is on the server side? I get it, if the disconnection was due to our ISP or network, but when it is the server that faults, we should not be the ones punished for it. There wasn't even a warning broadcasted that the servers were going to go down...
It is not our ISP or local connection. We pay for one of the fastest internet connections available in the public market, and I have a record to prove it. This does not happen to us on any other game. We've had ZERO disconnections with our ISP or packet loss. This is a most definitely a server side issue.
Copy of mass ping test proving stable connection.
"...
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=27ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=22ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=25ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=22ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=22ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=22ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=20ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Ping statistics for 8.8.8.8:
Packets: Sent = 210, Received = 210, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 29ms, Average = 21ms
Control-C
..."