Queue is busted AGAIN

doc_ketamine

self-explanatory. PC NA.

courier

unable to que at this time is the error I'm getting

Get your shitt together ZOS, I got 7 toons left to run.

Slurg

Gee, it’s so sad that everyone can’t keep exploiting the event to port to fungal grotto.

courier

Slurg wrote: »

Gee, it’s so sad that everyone can’t keep exploiting the event to port to fungal grotto.

troll on elsewhere tyro, some of us take the ques we get

Mettaricana

On ps4 right now its not even offering a queue nothing pops regardless of roles

Slurg

courier wrote: »

Slurg wrote: »

Gee, it’s so sad that everyone can’t keep exploiting the event to port to fungal grotto.

troll on elsewhere tyro, some of us take the ques we get

I’m glad you do, that’s increasingly rare today.

coop500

I got 7 more toons to do as well, Jesus Christ....

Evergnar

PC/NA same. Seems to always bug out this time of day.

crazyranger

ZOS ignores the broken event and in a couple of days it will pass. Crown Store has ZERO que time and ZERO downtime.

AzraelKrieg

@ZOS_GinaBruno @ZOS_JessicaFolsom @ZOS_KaiSchober @ZOS_RichLambert In future, do not run an event that requires the dungeon finder to be used when the dungeon finder doesn't work. This is completely ridiculous and unfair to your players.

Haquor

courier wrote: »

unable to que at this time is the error I'm getting

Get your shitt together ZOS, I got 7 toons left to run.

Its a feature.

G1Countdown

Yeah. I had a premade group of 2. I was getting the message 'someone had declined the invitation' BEFORE the game told me it had found 2 more players. How is the game so broken that it declines before I even get the option to click ready.

If ZOS is listening, they should know that this was a very disappointing event. The game in general is very disappointing with the number of bugs and performance issues that have been around for YEARS.

Abigail

First, I feel for y'all; ZOS did plan and hold this event despite the same problem last year and being forewarned it was going to happen again. Shame on them.

But ...

With so many players swapping amongst dozens of alts frequently, with an increased drop load that would likely challenge any configuration, especially an imperfect one, what could possibly go wrong?

ZOS is most definitely to blame for not fixing a preexisting problem and conducting the event anyway, but to a lesser degree everyone with the incessant need to do this event on every alt -- properly equipped, or not -- deserve a piece of the blame, especially since you were warned beforehand it was going to happen.

That is all, b*tch away.

DaveMoeDee

Abigail wrote: »

First, I feel for y'all; ZOS did plan and hold this event despite the same problem last year and being forewarned it was going to happen again. Shame on them.

But ...

With so many players swapping amongst dozens of alts frequently, with an increased drop load that would likely challenge any configuration, especially an imperfect one, what could possibly go wrong?

ZOS is most definitely to blame for not fixing a preexisting problem and conducting the event anyway, but to a lesser degree everyone with the incessant need to do this event on every alt -- properly equipped, or not -- deserve a piece of the blame, especially since you were warned beforehand it was going to happen.

That is all, b*tch away.

No, the players do not deserve any blame for taking part in the event. ZOS is funneling everyone to the group finder. It is on them.

idk

Zos never fixed the queue. They never claimed to fix the queue. They merely made "improvements" to the GF.

What is occurring is the server that handles the grouping for GF is being overloaded. Zos placed some sort of cap to reduce how many groups are processed by that server at any given time. It is why we get the error that we cannot queue at this time.

However, even with that cap the server can get overloaded and we see both the same old issue we have dealt with for over a year in addition to this new error when that occurs.

Hopefully, after a year of ignoring the issue, Zos will work on implementing a fix. iirc, the issue came into play after BGs. If that is the case then it seems the same server is taking care of both BGs and dungeons so separating them would solve the issue. Of course, I do not work for Zos and have not consulted for them so I am guessing based on events and a lot of experience with DB systems getting overloaded with information.

DaveMoeDee

Queue worked really well this evening. I did 4 premade groups and we got in quick each time. I'm on PC/NA.

Abigail

idk wrote: »

Hopefully, after a year of ignoring the issue, Zos will work on implementing a fix.

I am most definitely not disagreeing with you, but the fact ZOS has not yet fixed the queue suggests to me it's not an easy fix. Moreover, I'm guessing at least a part of any solution will involve multiple platforms, and probably fundamental changes in system architecture.

I'll also wager that somewhere in the ZOS bean-counter domain they're arguing whether such a costly revision is worth the investment -- "Can we weather this until we pull the plug on the game?"

NoMoreChillies

and people still give them money, telling them this product is ok.

idk

Abigail wrote: »

idk wrote: »

Hopefully, after a year of ignoring the issue, Zos will work on implementing a fix.

I am most definitely not disagreeing with you, but the fact ZOS has not yet fixed the queue suggests to me it's not an easy fix. Moreover, I'm guessing at least a part of any solution will involve multiple platforms, and probably fundamental changes in system architecture.

I'll also wager that somewhere in the ZOS bean-counter domain they're arguing whether such a costly revision is worth the investment -- "Can we weather this until we pull the plug on the game?"

When this undaunted event started Gina expressed surprise that we were getting the message someone had declined when we queued with a full group and that there were instances that a full group would not get put into a dungeon before it timed out.

Considering the number of times over more than a year it has been noted in the forums the GF had an issue, and even just a few months ago a person named Code noted this with a full group and that the GF ended up timing out after 10 minutes, that there is no reason to think that Zos had chosen to ignore this issue long ago because they did not consider it important, nothing to do with a challenge to fix it. I would bet they never tried.

That brings us to last week and the patch they slapped together quickly seems to suggest the issue is exactly as I stated above. If that is the case the fix could be extremely easy. Have two different servers handle the queueing for BGs and Dungeons. iirc, we did not have this issue before BGs were added to the game.

Regardless, we do know Zos had not taken the GF situation seriously until last week. There is no reason to think they tried until last week.