CT queue fills, one guy withdraws, CT queue suddenly back to emtpy

How is this possible?

23 other people hit accept on the queue pop. A single player withdraws. Yet, I'm starting again alone in the queue upon reentry from the withdraw.

It's been like this all week. Join CT queue, pops 10-15mins later, one guy withdraws, pops another 10-15mins later, one guy withdraws, rinse and repeat until I've been in queue for 3 hours and it's popped 7 or 8 times with one guys withdrawing each time.

How does this make sense?

Its too bad SE doesn't make it where you can still queue into the dungeon with missing players. The missing players can be fill whenever, especially since you dont need 3 full alliance for any of the towers.

DF has been a bit weird for me a while ago because I had queues that where almost empty and then suddenly popp (I doubt that like 6 people just simultaneously joined every time) and then as you describe almost empty again if someone withdraws. It also took about a minute to even see if anyone is waiting with me. But recently I think it's gotten better.

Quote:

---

Originally Posted by Kai_Lee

Its too bad SE doesn't make it where you can still queue into the dungeon with missing players. The missing players can be fill whenever, especially since you dont need 3 full alliance for any of the towers.

---

I believe certain pvp instances can begin like this iirc, so I don't see why they don't do it for older 24man content setting a min player req, as is usually 1 person not accepting

Would love to hear the dev's word on this.

After a failed queue - the Duty Status may revert to show only yourself in queue. Usually this is just a temporary thing while the DF recalculates available roles. Sometimes you get shafted ><

Some assumptions:
1. Preformed partial Parties: Either they have multiple raids selected and get in to a different CT than the one you've queued for. A party member misses the queue causing that party to drop out. (This happens WAYYY to often when I try to run CT with a group of friends <_< Disbanding when someone got Locked out. I think this has changed now...) The way CT fills three distinct parties - you may be bypassed by another player that queued with the needed role. (This happened to me MULTIPLE times back when CT was going through one of it's dry spells. Literally 300+ minute queues... :x We must remain Committed!)

2. Catching the Wave: There is a CT wave. If you catch it, you'll have 15-20 minute queues after each consecutive run. :3


Just a reminder, the Reddit forums started a Community Event: CT sundays. They encourage players to solo queue for all CTs to help new players try out the content. This was great a couple months back when it started, but it's definitely slowed down.