Quote Originally Posted by Aldora View Post
The thing is even though that you’ve clicked on Commit, if someone else does not click on Commence before the time runs out or clicks on Decline, you will see the same message that the registration was withdrawn.
I was solo queued.

In another instance I was queued in with a friend. We both saw 70/72 players, and the registration was withdrawn. It is nothing other then a bug.

Queues don't work like they do for CT - if some random in another party withdraws - it doesn't depop the queue. In frontlines it enters those that hit confirm, and replaces those that withdrew.

The Duty finder queue consists of several phases: Reserving an Instance, Forming a party, finding missing members for the party and confirming/commencing the duty. etc
This is all irrelevant to the part of my OP that you quoted..

All 3 of us queue up solo and on the same class. The one that queues up first does not always get the pop first.

To test it. When you queue up with your friends, ask what their wait times are. You will most likely hear quite a few different numbers.
As mentioned earlier in this thread (mainly by others), the average wait times are shared across GC's, which is a poor oversight.
I have already "tested" this as you mentioned by doing just that - asking what their wait times are (on the same class) and they are the same. Different on different classes also - despite Frontlines not actually taking role into account.


In my opinion, i would check if the Duty Finder actually matches together groups that do not follow the predetermined party Composition and forms parties consisting of more then 2 healers and no tanks.
Party composition is ignored, as mentioned within this thread.

Perhaps people are able to change their jobs when they enter Frontlines?
Yes, at the spawn point players are freely able to switch to any class. Hence why what job you queue up for is irrelevant.

But, especially the 4 healer party, sounds like a bug and you should keep reporting it with as much Info as possible.
This is very normal, and not exactly a "bad" thing from a strategic point of view. Issue here is that the "wait times" appear as though there is a job priority when there is obviously not, which is partly why I think the queue system is not functioning correctly.

It often feels like there is a job priority when you actually queue, but once the duty finder starts putting the actual parties together it just shoves people in where it can. I could definitely be wrong as no one can really tell what is happening behind that little queue box.