Frequent Server Crashes - RARE Please Fix ASAP!

  • 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
    ..."

  • 17
    Beiträge
    18.6k
    Aufrufe
  • Me and a friend only had about two hours to play the other night so we got right to it. We started one GH voyage, which gave us 5 islands. Between the actual voyage maps, a couple sunken ships we came across, some random chests found on islands, we had a lot of stuff on board, some 18 chests (although not a single captains chest, even being around level 30 each) 5 skulls, two of which villainous, and a handful of powderkegs and tea/silks and c**p. Once we finished the 5th island in the voyage, we hightailed it towards the nearest outpost, damaging and escaping another crew along the way. It's now 1am, our ship is heading full clip towards Golden Sands, I furl the sails, my friend cranks the wheel hard right, and we slide right up to the dock. One of the best parking jobs I've seen so far. We both run and grab the two villainous skulls, and the moment we had them in our hands, BLOOP. Loading screen. Message pops up, you've lost connection the the server. Guess we just go to bed then?

  • I've always felt a recovery from disconnect should be allowed. The window may be brief to avoid abuse, there may be other tools which could be applied to also prevent abuse. But having lost time to a server disconnect before when solo.... is infuriating.

  • This is by far my biggest issue with the game, and it’s a full stop on my enjoyment. Period!

    Rare, fix this.

  • This used to happen a lot when I played rainbow six Siege. For a while, if not playing in a squad, and you get server disconnected, when you relaunched you had to join a new server. Eventually they made changes though, and made it so if you get disconnected, your spot is held for a short period of time. I think it was like 5 or ten minutes, and when you relaunched, you rejoined into your old spot. I feel like this change would be hugely beneficial to this game, with the added side effect of inconveniencing server hoppers.

  • just out of curiousity, what are the errors you get? I know servers crash sometimes, but sometimes the problem can be fixed on your side.

  • @sir-lotus said in Frequent Server Crashes - RARE Please Fix ASAP!:

    just out of curiousity, what are the errors you get? I know servers crash sometimes, but sometimes the problem can be fixed on your side.

    It's a typical disconnection pop-up. The same one that always comes up when a server crashes. Everyone in our party got booted, from multiple locations.

  • @shackelfourd said in Frequent Server Crashes - RARE Please Fix ASAP!:

    @sir-lotus said in Frequent Server Crashes - RARE Please Fix ASAP!:

    just out of curiousity, what are the errors you get? I know servers crash sometimes, but sometimes the problem can be fixed on your side.

    It's a typical disconnection pop-up. The same one that always comes up when a server crashes. Everyone in our party got booted, from multiple locations.

    The one I’ve been getting just says disconnected, but won’t let me get back in game for a while, along with everyone else in my party...

  • @shackelfourd Yep. I don't get why rare doesn't address this. Perhaps one of the people who thinks that they are some transparent company that is more than willing to communicate with us can explain that to me? All they ever say is...open a ticket...

  • @shackelfourd @StormagedonGirl
    oh, that's really a server issue then. Sorry this happend to you guys. I'd probably suggest reporting it. It might not be necessary, as i'm sure there are automated reports Rare gets when a server crashes. In that case it would only waste time of people handling reports. On the other hand, there's always a possibility of a bug having only your crew disconnected and they might not be aware of that. I guess it's up to you.

  • @sir-lotus said in Frequent Server Crashes - RARE Please Fix ASAP!:

    @shackelfourd @StormagedonGirl
    oh, that's really a server issue then. Sorry this happend to you guys. I'd probably suggest reporting it. It might not be necessary, as i'm sure there are automated reports Rare gets when a server crashes. In that case it would only waste time of people handling reports. On the other hand, there's always a possibility of a bug having only your crew disconnected and they might not be aware of that. I guess it's up to you.

    Yup...

    Pretty lame.

  • @Shackelfourd
    Would a reconnect to last session feature help fix the issue, in your opinion op?

  • Here is an idea for loot recovery due to server crash...
    Have the game keep inventory of what a crew has on board their ship and also being carried by crew members. Have the client also keep the current party locked together unless said members choose to leave the crew or logout altogether. Having the inventory in crews memory upon crash force auto server migration. Auto feed voyage to wherever for the recovery of said loot.
    It could even be a location not on maps perhaps a landmass that rises from the sea when only said crew is there. But would have to be on their ships map and perhaps a diff color for ease of locating...

  • @urihamrayne said in Frequent Server Crashes - RARE Please Fix ASAP!:

    @Shackelfourd
    Would a reconnect to last session feature help fix the issue, in your opinion op?

    Absolutely!!

  • @shackelfourd

    well you see I'm putting together a team...

    https://www.seaofthieves.com/forum/topic/55254/reconnect-feature/2

  • Got nasty almondbeard last week. Had to change router settings, no more issues after though.

  • I don't get an error message game just freezes then boots me randomly

17
Beiträge
18.6k
Aufrufe
1 von 17