An issue occurred while communicating with the game servers. Please check that you are connected to the internet and try again.
So… What’s the deal?
7 Likes
Had that issue as well i just closed game waited few mins restarted it worked ok
There seems to be a restriction blizz just added with time between joining/exiting games. The annoying part is if you even fail to join a game it triggers it…
2 Likes
Seems to be that creating a game too fast can now result in that message. Waiting a few seconds seems to resolve it.
Unknown is that is a timer they put in to limit games per/time period for stability or what.
it’s hardcoded countdown for button press, once you press it - it’s 60s
even if you don’t join the game because whatever reason, or create game with symbols, duplicate names, whatever - it’s always 60s cooldown till you be able to create / join another one
i guess it’s the “leave like that for today” solution from new IT guy ;]
Always 60secs - i did measure it: Diablo 2 Resurrected New 60s Queue - YouTube
2 Likes
Welcome to your new timer overlord. It’s Blizzard Band-Aid to rapid game creation. Kill pindle and wanna make a new game? You have to wait. Try to join a full game? You have to wait, at failure mind you. Want to swap to a character , drop something in shared and pick it up on an alt? Yeah you’re gonna be waiting. Money well spent.
2 Likes
I do appreciate that you timed it.
I also appreciate they did not use the D2 (2000) solution which was to suspend players for making games too fast.
Not just a timer, they outright suspended them - and anyone on their IP address.
See above. This is not new, and is a lot nicer than the old system they are using on D2 (2000).
Here is that system - it is VERY extensive and is not just a timer, it is a full out suspension. A VPN or business IP gets you 2 weeks.
Well it is new (to d2r) when you consider that we didn’t have this yesterday…
I just don’t understand why they need this all of the sudden.
3 Likes
I’m aware of the old system. I’m also aware that this is D2R released in 2021 where technology has had two decades of progression.
2 Likes
Ok, I can agree with you there 
Server stability I would guess. Pindle runs force rapid game creation which can use a lot of server resources - and it seems that for now they are trying to see if a game creation timer helps stabilize things.
The servers have hard crashed for 3-4 hours a day 4 days in a row now. In addition people were rolled back and lost items. That is NOT fun gameplay at all.
If the timer works, great. If not, they will keep trying things. I realize it is an inconvenience, but less of an inconvenience than server down and items lost.
Hopefully it helps.
To pretty much sum it up, Blizzard is aware of the issues but if you talk to their technical support and say you are having a problem with your connection to Blizzards server, they will primarily say these two things:
- It’s due to your Internet and to contact your ISP.
- Unplug your modem, wait 15 seconds, and then plug it in to solve the server issues.
This use to be called Realm Down…I wish Blizz would just use the old terms so we know what is going on.
I really don’t think the server crashes had anything to do with people hosting games to run pindle. There was clearly some other weird stuff going on with that whole situation (whether it was people somehow crashing servers to dupe or mass ddos).
Edit: Could also be from people spam creating games to try to dclone hunt. (Which would be avoidable if blizz would just rework the dated pandemonium event requiring hot ips)
i’d just hoped they’d implement queue timer after joining the game instead of pressing the button whether you join it or not
will see, for now it looks like temporary solution
unfortunately it’s sad that we all have to figure out what blizzard/vicarious are actually doing to the game instead of reading that in patchnotes 
This dupe theory is the biggest copium on this forum. Blizzards Official WoW servers are out performed by unofficial servers being hosted by some randoms in Russia with 10k pop. They’re a joke.
2 Likes
You can’t call Tech support so no, that won’t happen.
No, not that… Crashing the whole globe and getting everyone rolled back a few hours is not helpful in duping. Esp when you can’t target the rollback period or rollback region.
But it was related to traffic/server load. Beyond that I don’t know more.
Blizzard communications leave a lot to be desired and this has been the case across games for YEARS.
It’s duct tape and a strap on dillydo being used to patch a water leak.
These devs aren’t even devs. They are just twchnical analysts using software created by other devs to mend things they are incompetent to fix.
They need to outsource some competence for the rest of the game, not just the graphical overhaul.
Modernize it. Resurrect it.
Right now it’s a lifeless corpse being shocked over and over again but dies, over and over again.
This is still in beta. Blizzard wants people to beta test games AFTER they release them.
Meaning- they release incomplete products.
3 Likes
60 seconds isn’t a big deal really. By the time you join the game, kill Pindle, pick up stuff (if anything), ID/stash, then leave it should be fine for almost everybody. It won’t kill people to slow down a few seconds.
Okay now try and join a Baal game, oh it’s full? Guess you’re waiting, better luck next time. Nobody said it would kill them, it’s about not inconveniencing your player base.
it’s not about pindle
- join a full game - 60s cd (it’s all about pressing the button, not joining anything)
- create a trade name, like “O zakarum N ist” if there is a game named like that already - 60s cd
- error (that one common popping all the time) while joining a game - 60s cd