Server crashes have become too usual

Since 1 month, aprox. it has become something normal.

And no, it doesn’t happens only to me.

Is sad to:

  • Starting a mission, disconnected after minutes. Starting another one, disconnected also after minutes.

  • Being disconnected just minutes before finishing a very difficult mission, feeling proud and liking the teammates…. but nope, you can’t enjoy the win.

  • Havoc missions… de-ranked sometimes, just because of server crashing. Sad.

  • Etc.

3 Likes

the one guy who cleans the cache is in a sauna somewhere

2 Likes

Yeah my last mission today aborted, because of the 2014 error. Few weeks back we had a day our Havoc missions would constantly crash all game clients with 2001 and 2014 errors. We were still able to reconnect, and only lost 1 rank as a result.

Arbitrator launched poorly balanced and with multiple buggy talents. That update also brought some new server side stability issues. A great way to sell a 2 years old game to new and returning players.

2 Likes

I also have anecdotal evidence of an increase in server-side crashes in recent days.

1 Like

I’ve gotten more server errors in the last week of playing than, probably, in the last two years, excluding last week.

I’m not kidding, it happens several times per session now instead of… well, I’d put something here to quantify time but it was so rare before, I can’t even come up with the proper time frame to quantify it.

1 Like

Yeah.

Now is like… “Oh yes, another server crash, well I guess I have to start ALL mission again”.

”Ah… well another time….”

”3rd time?… I close the game, and go to play other thing”.

That is me basically.

1 Like

There are two different bugs causing these.

One of them makes certain mission crash / disconnect in the same spots. So these missions you can repeat as many times as you want, they will always crash when you get to the same location in that map.

Then there is another one where (and this is just my guess, no actual proof that it works this way) the mission disconnects you if you’ve first started it “too long” ago. And this timer seems to persist through several attempts. You could’ve started a mission (example numbers) 89min ago, failed it 3 times since then and are now on your 4th attempt but then when the instance of the mission dies, your 4th run gets cut short and you disconnect.

If someone knows how either of these actually work, please correct me. I’d love to know myself.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.