Resetting queue when someone doesn't join is simply mind-boggling.

I cannot begin to fathom the thought process behind putting a duty finder group at the back of the instance queue when a random member fails to accept the queue. It is unbelievable.

Players A, B, C and D (from different servers, who don't know each other) join the queue, get formed into an instance group and wait 10 minutes for an instance to become free.

Player D goes afk, falls asleep.

Players A, B and C are now sitting in a queue that is GUARANTEED to fail when it pops, because player D will not accept the group. When this occurs, a new player (usually DPS, since they have the longest queue), gets placed randomly in the queue, and the timer resets for taking an instance.

Repeat the process; if one of the players now goes afk (which is more likely given that the three remaining players have now been waiting 10 minutes for a failed queue), that player gets replaced and the process repeats.

I don't know about others, but eventually it gets to a point where I just throw my hands in the air, say "screw this" and go and do something else. I may or may not remember to click the withdraw button through my exacerbation, which may or may not guarantee the remaining members a requeue when the next queue pops.

This is... unbelievable. It defies logic.

How it should work, and how it works in every other iteration of a duty finder in every other mmo:

Players A, B, C and D queue for a dungeon.
Player D falls asleep.
The queue pops, players A, B and C click accept, and player D does not.
The queue fails. The dungeon finder takes the next-in-priority DPS from whatever group they are in, places them in the group, and re-pops the instance. Players A, B and C get their "average" queue time pop, plus a little bit extra for the failed player D, instead of potentially 4 to 5 times the "average" queue timer depending on their luck.

End result: The average queue time potentially gets _SLIGHTLY_ higher, but becomes an ACTUAL representation of the average queue time, rather than a time that sits somewhere between "yay everyone accepted first time" groups and "omg I've been in the queue for an hour and a half and 5 people have failed to accept" queues. Furthermore, the queue is actually a QUEUE, meaning that the person who queued first gets in first.

Quote:

---

Players A, B, C and D queue for a dungeon.
Player D falls asleep.
The queue pops, players A, B and C click accept, and player D does not.
The queue fails. The dungeon finder takes the next-in-priority DPS from whatever group they are in, places them in the group, and re-pops the instance. Players A, B and C get their "average" queue time pop, plus a little bit extra for the failed player D, instead of potentially 4 to 5 times the "average" queue timer depending on their luck.

---

this is how it works already

That does sound like the most logical system.

I think once free subs run out, the 'reserving an instance' issue won't be as big. It may even cease to exist entirely. I think that's what SE is waiting for really, to see what kind of stable numbers of subs they will have. I figure it will get fixed about a month after all free trials have run out if it is still an issue at that point. They'll probably add more duty finder servers.

I know that doesn't make anyone feel any better about it right now, but it is something to look forward to.

Quote:

---

Originally Posted by MisaCeliousa

this is how it works already

---

No, it isn't. My queue popped at 11 minutes. Someone (a dps) failed to accept it.
My queue popped again at 24 minutes. The Healer failed to accept it.
I am now sitting at 39 minutes, with an average queue time of 14 minutes.
I am a tank - this group has been "full" since the second that I clicked join.

http://i41.tinypic.com/24q651t.jpg

Quote:

---

Originally Posted by MisaCeliousa

this is how it works already

---

No quite. I think what the OP is saying, and I also think this is the case, is that if you're not actually queuing to form a group but are infact waiting to be assigned an INSTANCE (i.e. AK) for your group, then when the instance is finally assigned should someone in the group fail to accept you'll be put to the back of the reserving instance queue.

I've only had this happen once to me, but i'm sure this was the case.

thats because the "reserved instanced" , windows pop to enter 1 doesnt enter , and u go back to "reserving instance"

Quote:

---

Originally Posted by Warlyx

thats because the "reserved instanced" , windows pop to enter 1 doesnt enter , and u go back to "reserving instance"

---

I know. You go to the back of the queue, when you should go to the front of the queue.

Quote:

---

Originally Posted by Furious

No, it isn't. My queue popped at 11 minutes. Someone (a dps) failed to accept it.
My queue popped again at 24 minutes. The Healer failed to accept it.
I am now sitting at 39 minutes, with an average queue time of 14 minutes.
I am a tank - this group has been "full" since the second that I clicked join.

http://i41.tinypic.com/24q651t.jpg

---

Then it is a bug concerning "Reserving instance" and then losing a player in the process. Please check if it has been posted yet in the appropiate bug forum and if not make one to help your fellow players.

This has annoyed and puzzled me since I first discovered it.

Quote:

---

Originally Posted by skiwi

Then it is a bug concerning "Reserving instance" and then losing a player in the process. Please check if it has been posted yet in the appropiate bug forum and if not make one to help your fellow players.

---

It isn't a bug; it's a design choice. When you lose a member (because they failed to accept queue or because they withdraw), your group is considered a new group and is placed at the back of the queue. This isn't something done "by accident".