Every day, I come back home from work and I have to wait in a queue. Can’t you kick players for inactivity? I know many players that just turn on d2r and go to work and come back playing it.
1 Like
No live with it or quit. Queue is a lot shorter than a few weeks ago. I guess many people quit
1 Like
I believe the strategy is in line with activisions values. Takes your money, then influence you to leave. That way, they save money by not having to upgrade servers.
2 Likes
Yes, I think it’s going away eventually just a question of when. Maybe a month or so
dam long queue at 11 am est time on a monday in the US. Love “global” servers…
It’ll be gone once enough people quit. I think that’s Activision’s plan tbh.
1 Like
“As we mentioned in our last update, character saves have been occurring on the global database. Next week, our internal teams will begin testing a significant change by having saves occur more often on the regional end, rather than global, in hopes of alleviating some database stress. Once our internal load testing is complete, we will put up a PTR server with this fix to get some real-world testing before rolling out to the live game.” ~Pezradar~
I think this will help a bit, we shall see.
If the load is taken off the servers database, maybe it will eliminate the need for a Queue.
Will the queue ever go away?
Nah man. They don’t even develop things for D2R the game anymore. All their dev time is now spent just improving and optimizing the queue itself instead of working on getting rid of it.
Queue is love. Queue is life.
I mean it is the most probable desired outcome. They have shown no interest in keeping us informed, most likely it’s too complex of an issue and they just won’t fix it, along with all other known bugs.
While the queue is annoying as heck, I’m more frustrated by waiting in the queue and starting a game, only to lag out or whatever the issue is and “lose connection”, then get dumped back to the end of the queue again. A simple time-out check would be most helpful here. Once a session is started (after the client was queued) and a game instance created, that session remains open for x minutes as a fault-tolerance safety. If the client reconnects within that window, the session is still active. The game they were in can be either kept or recycled, though I’d recommend keeping it active to prevent exploit attempts (break the game-creation limiting). I’d much rather recover my body or have to repair my stuff than have to get thrown to the back of a 100+ queue because of some phantom disconnect. This has happened to me three times in the past few days, so it can’t be happenstance.
/endrant()
3 Likes
They want to keep us informed on Twitter, the enemy of free speech and conservatism. The land of the ‘‘woke’’.
1 Like
Nov 4th, Korean big game franchise Lineage will have a new mobile game and it should draw away a large crowd.
1 Like
That is the most annoying aspect of the queue for sure. 
I call it “The Pretty Hate Machine”
I had very long queues this weekend, clearly feels like Blizz is waiting fore the population to die down rather than fixing their mess, shame.
Gotta love that queue, not very long now, but 1st attempt get in and crash before actually in my first game (new record), 2th attempt almost in and redirected to offline, 3th attempt attempt almost in and redirected to offline, 4th attempt is going on atm but the queue hasn’t moved in a while…and each time I retry the queue is longer…such a great company.
If I could refund my whole Blizz account right now, I would pack it up uninstall everything blizzard (except old blizzard north real D2) and don’t look back.
Ask for a refund. They gave me one for complaining about the queue
1 Like
Such a stupid way, I don’t mind them doing it on Twitter but they should do it on their OWN forums as well.
2 Likes
I wonder, how difficult it is to work on the servers with near 24hr uptime?
Remember the first few weekends? They would tweet like 5h after the outtages, I guess they inform us of what we’re already informed about. And then the same copy pasta everytime, probably a bot tbh.