No improvements

[Mykhel]

I'm trying to stay calm about this, but I'm really losing my patience. I was excited to hear the backup servers were coming online today and we would have some relief. I get home after working all day to a 2400 queue. Not too bad, right? Right. I wait a painful 2 hours to get down to 700ish of surprisingly no interrupts. Then BAM! Error 2002. I'm like ok... well, maybe if I get back in fast, I'll keep my spot in line? It's been less than 60 seconds...

Not a chance.

3700+ now. Given that it refreshes about 7+ times before decreasing at all, I will go ANOTHER day without being able to play... as I need to sleep in less than 3 hours... a game I paid 60$ for... The "7 days of free play" is only 2 days now as I haven't been able to play since Sunday when I was off work. These errors have ruined my first dungeon, ruined the questing experience (so much time goes by I forget what I was doing and already have done... and everyday that goes by I risk running into MSQ spoilers on Youtube and Rumble. I already had a piece spoiled for me with a single video thumbnail yesterday and wish I could forget it... but that's not how life works.

I've said it before and I'll say it again. They should've known this would happen. They delayed the game and got extra time to deal with this... but they didn't. Backup servers should've been default for the expansion early access. I have faith in this company and I don't want it to waiver... but this does not help. Rant over.

Finally, I don't give a crap if you "are tired of seeing posts like this." Some of us are very frustrated and have limited time to play every day. If anything, this is a way to vent frustration. Don't like it? Leave.

[Wiglac]

Yeah, the 4 hr downtime has changed nothing. Still getting 2002 error. and the crazy thing is was in-game and then it kicked me out. Queued again for 30 min.. 2002 error. So back to queuing. Really was this just a pretend patch.. to make us think they were doing something?

Now up to 4 2002 errors... last 3 before could choose character.

[Macleod]

The maintenance actually ended early, maybe they should've taken the whole 4 hours to...you know...ACTUALLY DO SOMETHING?

[NorthernLadMSP]

I hear ya. Have gotten disconnected with 2002 three times in the last hour. Each time, the queue gets larger (4,333 the first time, 4,857 the second and 5,130 the last). I give up.

[Mykhel]

Yup. In the 6 days I've had "access" to the game and the 30+ times I've been dropped from queue... my spot has been saved a total of 1 time. It still took 2.5 hours to login and I had to log off within 45 minutes of when I got in.

[Hasrat]

In all fairness, they were pretty clear about the fact that they may not have found the cause of and resolved the source of all the errors.

They're bailing a sinking boat. And they patched the hole. Turns out, there was more than one hole.

It sucks. But, having never experienced server loads like this in their entire history, can you blame them for not knowing about every leak that might spring up?

Everything has a breaking point. We just haven't ever gotten this close before. At least not for a while.

[Darthgummibear]

I'm actually worse off now than I was before the maintenance. Now when I get 2002 errors, instead of getting back into the queue where I was, the queue gets larger...so until this is fixed I won't be able to play at all.

[NorthernLadMSP]

I'm actually worse off now than I was before the maintenance. Now when I get 2002 errors, instead of getting back into the queue where I was, the queue gets larger...so until this is fixed I won't be able to play at all.

Yep, it is worse now. Before, I was also able to keep my spot. Now, it puts you at the end of the line.

[Lordes]

Yea guys we waited through multiple delays just to have more issues, like what exactly did this team do in all the delayed release times

[Mykhel]

In all fairness, they were pretty clear about the fact that they may not have found the cause of and resolved the source of all the errors.

They're bailing a sinking boat. And they patched the hole. Turns out, there was more than one hole.

It sucks. But, having never experienced server loads like this in their entire history, can you blame them for not knowing about every leak that might spring up?

Everything has a breaking point. We just haven't ever gotten this close before. At least not for a while.

I get this. I really do. But having seen stress tests done on servers before... this should've been identified. WAY earlier.