seriously, 90 min wait is crazy and it's been this way for a while now.

instead of the daily crashes for hours, now it's this.

why haven't they added it? or are they trying to code it to make it less stress it? hardware could be overnighted? idk how any of thhis works.

its not that, it's a code thing/logistics of the whole thing. they have a post/blog about the specific issues.

got an eta on a company like blizz to fix it? i know you don't know the exact but whats an estimate in your opinion?

no one knows, depends what issue you're talking about anyway. like actually converting the legacy services on the backend could take 2 years. the rate limit queue to get in the game? probably months to a year but I have to make an assumption about how many players there will be in X time which makes it really just a guess that you shouldn't take to heart.

it only que's from 6 am - 10 am is the worst, up to 400+ but usually at 200-250, rare to get up to 400

after is like 50-100

any other time, no que or under 15

This post was edited by Brock55 on Oct 23 2021 11:38am

It's actually quite difficult to just add servers

It's not just plugging an extra computer into your home router

are you saying blizzards 4 port router is filled up with other games

https://kotaku.com/fixing-the-diablo-ii-resurrected-servers-sounds-like-a-1847871074/amp

here's a nice article on the situation.

Sir this is a Wendy's

Syncing/backing up databases over state lines is a well known challenge in the Tech industry. Blizzard is trying to do this cross-country.

Intel was trying sync their data over 1000 miles and they went over budget like 10x because they had to actually lay some dedicated fiber for it. Latency is everything.

It's likely that they need a network solution, not a server solution.