368th in Queue is BS

This was my experience today. Wanted to play after lunch (EU) Start game, 347th in queue. No biggie, it's a sunday, peak times and all that. Ill wait. 25 minutes later I finally get it. First game I join, some guy asks for a rush. No problem. 5 minutes in, game crashes to desktop. Now my queue is 450.

This is in a nutshell the issue with queues. I don't remember the original d2 or d2:lod EVER crashing.

Jamezdin wrote: 3 years ago

This was my experience today. Wanted to play after lunch (EU) Start game, 347th in queue. No biggie, it's a sunday, peak times and all that. Ill wait. 25 minutes later I finally get it. First game I join, some guy asks for a rush. No problem. 5 minutes in, game crashes to desktop. Now my queue is 450.

This is in a nutshell the issue with queues. I don't remember the original d2 or d2:lod EVER crashing.

Not sure about the time it came out, but playing d2 on a modern computer these past years and i experienced tons of crashes. I agree having to requeue post crash is really aggravating, they could work around that by letting people who crashed rejoin without queuing, but hopefully the whole system will be gone before it really becomes a necessity.

1 thing Blizzard you need to do is fix this damn problem as fast as possible because thousands of ppl paid you 70 or more dollars for this game and cant even play it online a there free time because its servers are completely shit take some of you dam not hard earned cash and make another server or make the other bigger ffs this is getting ridiculous

Waiting in this queue to play for 5 min then crash just to wait in a long ass queue again is amazing service...

300 is bad? queue in asia are around 1500 yesterday