Instances Full + An Idiot Queued Who's AFK = RAGE!

[Blaize]

So yea I can understand (Barely) that SE are having issues grasping the idea around Duty Finder and fixing the fact that Instances become full at certain times, especially for Ampador.
But then when waiting 25mins for the instance to free up and pop, you get shafted with a person queued whos AFK, ok no deal you'll get next person avail? No no...you get shafted to the back of the queue and have to wait another 25mins for a free instance!! Oh Joy! And what happens if you're lucky enough for another AFK person?! Yep back of the line short stuff!

Now I'm not a nay-sayer at all, but C'mon, SE please, where is your Common Sense?! Putting people who had an AFK in the queue to the back of the line?! really?! Not enough Ampador Instances?! The only level 50 Instance worthwhile to run?!

I have a feeling unless that proverbial finger is pulled out soon, a good number of people will give up on this title yet again

[CrashingWaves]

What are you talking about? If your party is ready but one AFKs, it keeps the ones who accepted as a group. While not technically in a party yet, these "mostly made" groups waiting for one more are given priority; second only to fully made groups if the instance server is full.

[Blaize]

snip.

Reading comprehension goes along way

Basically, Queue up for Ampador as Tank+2DPS Need a healer, get given a healer but instances are full so need to wait up on an instance to become free, which takes 25mins-ish.
Finally Instance is free and pops the accept button, but that Random healer you was given is AFK and doesnt hit Accept, So it dumps the 3 already grouped to the back of the line, it doesnt hold that instance free for them and the next INSTANTLY available healer.
So Boom you got another Healer in your DF waiting on a free instance but yet again you gotta wait another 25mins-ish before you can enter the dungeon due to instances being full. Thats a needless almost 1hour wait.

Why should it throw the 3 people who accepted the DF to the back of the queue because of some random who was AFK in the DF System?!

[CrashingWaves]

-snip-

Was the dig at me really necessary? Your further explanation does help me understand a little better. You're upset because if your group isn't ready to go, then priority is given to the next group in line that supposedly is. I can see this becoming a non-issue if the people who are AFK are forced to log out, which -is- something they are looking into. Also, the population slump after people have to "OMG pay?!" for subscription will free up the server load too.

[Celestine]

Blaize i know what you mean. This happened to me today. For the people having trouble understanding...even if you have a full group, 1 healer 1 tank and 2 dps... u cannot join an instance immediately. You have to wait for an instance server to open up. Lets say you queue by yourself. Youve been matched with 3 other people and are now waiting for the instance server. After 20 min of waiting, the queue pops but one of the people withdraw. You now have to wait for an open instance server all over again. This is really only an issue on weekends where there are not enough open instance servers.

[rwyan]

Blaize i know what you mean. This happened to me today. For the people having trouble understanding...even if you have a full group, 1 healer 1 tank and 2 dps... u cannot join an instance immediately. You have to wait for an instance server to open up. Lets say you queue by yourself. Youve been matched with 3 other people and are now waiting for the instance server. After 20 min of waiting, the queue pops but one of the people withdraw. You now have to wait for an open instance server all over again. This is really only an issue on weekends where there are not enough open instance servers.

I don't know how accurate this is. In my experience today (first time using duty finder as a solo player), I got grouped, but a player dropped, got re-grouped immediately, and another player apparently dropped (rinse repeat for about 5-10 minutes), and finally the whole group commenced without anyone withdrawing.

[Blaize]

I don't know how accurate this is. In my experience today (first time using duty finder as a solo player), I got grouped, but a player dropped, got re-grouped immediately, and another player apparently dropped (rinse repeat for about 5-10 minutes), and finally the whole group commenced without anyone withdrawing.

Was this for Ampador?!

[XyleHarkyn]

I'm having issues getting into it as well. Got a full party with no open instances to run.

[Celestine]

I don't know how accurate this is. In my experience today (first time using duty finder as a solo player), I got grouped, but a player dropped, got re-grouped immediately, and another player apparently dropped (rinse repeat for about 5-10 minutes), and finally the whole group commenced without anyone withdrawing.

Yep and i garuntee this wasnt for amdapor. If the instance servers arent full for that particular dungeon then it doesnt matter. However for something like Amdapor keep, if someone withdraws, you will have to wait for a free instance server all over again.

[Nystai]

The issue isn't with DF's create-party queue. Each instance/dungeon has say only 10 slots for 10 separate groups. So even if you have a full 4/4 party but your group #11 in a dungeon of only 10 slots your group must wait til one of the 10 slots opens up. This is never encountered on almost any dungeons accept AK because no other dungeon is as popular as AK is atm.

Then when your group finally does get an open slot if someone in the DF group does not click accept on the DF commence window it will kick the rest of the group back into the queue of waiting for an open slot again, even if it replaces that afk party member right away.