Please fix the queue for Crystal Tower and other future alliance content.

This is unacceptable.

http://images.mmorpg.com//images/gal...8a7dfc7f28.jpg

One person can completely botch the queue for 23 other people. If someone drops out, a group should be created with slots open to the equivalent of the amount of dunderheads that didn't accept the queue. The next people in line for CT should automatically be bumped into those slots.

This is the only game I've played where if less than half of the group fails to accept a queue the entire thing is cancelled. Please fix this extremely frustrating issue.

Thanks.

Update: It took 18 minutes of people ditching the queue to get into Crystal Tower. Wow.

while this is annoying, auto starting the raid will cause people to afk at the start even more so then they do now. I don't have a solution I just don't think that is the right one.

or allow pre made alliances to tag CT together, so multiples PT dont have to cancel in order to play with their FC.

Quote:

---

Originally Posted by Badger

It took 18 minutes of people ditching the queue to get into Crystal Tower. Wow.

---

Still a faster queue time than queuing as a DD for four-man content. ^^

But I agree though. Terribly frustrating, especially if you have spent time organising a group for this.

Showing "dungeon progress" is a stupid idea in the first place, not showing it anymore when a dungeon pops would stop 99% of this stuff.

No need for lockout timers, etc. Just make it so you can't tell dungeon progress. Allow larger FC's to multi-queue, and then you've effectively eliminated all of the duty finder abuse.

Quote:

---

Originally Posted by iggi

while this is annoying, auto starting the raid will cause people to afk at the start even more so then they do now. I don't have a solution I just don't think that is the right one.

---

Maybe, but it would move the queue along faster. if you're afk for more than 10 minutes inside the instance you are kicked and someone with in progress ticked could enter in their stead. Another solution would be to auto start the raid but add confirmation button while inside, before the starting barrier goes down. This would allow replacements to enter real time and would likely streamline queue times.

The whole queue isn't nixed as long as it isn't someone in YOUR party that didn't hit Commence. Whichever party had the "dunderhead" who afked or didn't click or whatever gets dropped out of the queue and the remaining two parties get rolled a new third group. Or if the dunderhead was a solo queuer then no one gets screwed as it just rolls a new person for that one last slot in the 4-man group. What's happening in the screenshot is just this. A person or perhaps a whole party are hitting withdraw/not clicking commence and so DF is rolling a replacement person/party for you and whichever other team didn't withdraw. If someone in your party didn't Commence it would then cancel your DF and you'd start from the end of the queue line again when you reapplied.