No not melee leeway, but disconnection leeway.
After waiting for about 3 hours in queue (went to go make dinner, eat dinner, hang with the family) and finally got in. Was able to play for an hour and then got unceremoniously dced. I log back in and I'm at the back of a queue for another 3 hours.
I thought there was some leeway mechanic to stop this kind of thing from happening.
Has anyone else had this problem?
Nope and it’s pretty messed up. Had the same happen to me and people I know.
A couple minutes holding your spot if you DC would more than make up for their server issues.
You think you do, but you don’t
Yea I was really expecting something like this to exist... I remember on Light's Hope launch they had this, and even on Kronos they had this in place. But not blizzard :(
I only had this problem on launch day. I played all day yesterday without a problem, however I have friends and talked to a few other people on my realm that had that issue which is really annoying. I'm surprised Blizzard is having so many issues still. Seems they really didn't prepare for this.
As far as I know, there should be a grace period when logging off or getting dc:ed. But for some reason it doesn't seem to work when you get dc:ed. It does however seem to work when logging off.
I guess I just got supremely unlucky then.
I have gotten DC'd a couple of times and also exited game to put on some addons, each time got in without having to que while 9k ques were rolling around, There is a dc prevention system and heard its about 5 mins.
There is some queue 'leeway', and I was fighting it yesterday actually. I'm not sure if this applies to getting disconnected once you're in though.
I was using TeamViewer to log into the server with my home computer while I was at work. The goal was to time a remote login so the queue would pop right after I got home from work. My first attempt was too soon and it was quickly becoming obvious that the queue would be up like 45 minutes before I'd get home, resulting in a disconnect followed by being stuck right back at the end of the queue, defeating the entire purpose in the first place. At that point I decided that I needed to go back to the end of the queue. I wanted to leave the queue and go back to the end because doing so would give me a better chance of the queue coming up after I got home from work, not before.
It took me like 5 different attempts to get out of the damn queue. I was at position ~2000. I changed to a different server, and then changed back to Fairbanks. My position in queue went to 5,000, and then immediately dropped me back to 2,000. Son of a bitch. My next idea was to quit the game and log back in. Same thing, I started at the back of the queue and after a second it dropped me back where I was, around ~2,000. But my placeholder was still moving, and I was closer to 0 than when I left in the first place... I tried quitting the game on my home computer with TeamViewer and then logged in on a 2nd computer here at the office, and when I did that I was STILL ahead of the queue, right back where I was before.
So not only does quitting the game and re-starting it not lose your position in queue, quitting the game and starting it up a minute later on a different computer 20 miles away doesn't drop your position in queue either.
The only way I was able to get pushed back to the end of the queue was logging out and waiting 5 minutes. I don't know if 5 minutes is the cutoff, but that's how long I waited.
This is entirely antecdotal from me, but I felt that the grace period was non-existent when a layer crashes. If you d/c due to your own internet connection, then the server knows to give you X amount of time to get back in. But if the layer goes down entirely... then nothing remembers anymore. This is what it seems like after being d/c'ed the Gehennas Discord goes into an absolute uproar.
No DC's for me. Playing since it launched. Only 1 of many friends had a DC once.