Frontlines queue is broken.

[Altena]

After waiting this long, the queue finally popped.
I hit confirm - and noticed it was a 24-man campaign.
After the time expired, a red message appeared on my screen saying "Your registration was withdrawn." This happened despite ensuring I hit the confirm button. (I am 100% positive I did not miss this queue as I saw the number of players xx/24).


This has happened on multiple occasions, in both solo queue and while in a party.

Frontlines queues need some serious attention.

- The queue occasionally withdraws, despite all of the party members hitting the "Confirm" button.

- Myself, and 2 FC friends queued up separately 5-10 mins apart on many occasions. Often the person that queued up first, ends up getting a spot last. To test if this was job priority in action (even though it doesn't match parties by jobs/classes, and you can change inside anyway), we all queued up on the same job, and got similar results.

A good portion of the time, the person who queued up first gets a spot after a person who queued up after them.

- In many instances, the estimated wait time displays less than 20 mins, however myself, and some fellow players (even while solo queued) wait in excess of 40 minutes for a spot. Often we attempt to cancel this queue and retry it (which would in theory put us at the back of the line), yet we get a spot in under 10 minutes.

- After attempting to "Join in Progress" while a friend's game had 6+ empty slots, I was unable to do so as a BRD, DRG, PLD, MRD, however when I queued as a SCH I got into this game instantly. After entering, I noticed the party I joined already had 3 healers and no tanks. If there is some form of job priority, it is also not functioning correctly.

This is also obvious when we join games that happen to have 4x healers in one party, and no healers in another.

What on earth is going on at the back line? Because whatever priority queue that is being used is not functioning correctly at all. It is glitchy, the wait time is extremely inaccurate and any form of job priority (since it appears that there is "meant" to be one) is not functioning.

While I know queues will naturally take longer during off-peak hours for our data centres, however it seems as if the queue is constantly trying to match people based on job priority. If this is the case, then remove it entirely - as it's not working at all, given that parties can be filled with DPS and Tanks. All it is doing is drawing out the queue times to a much longer wait time then they could be.

If rank priority is also used, then remove it. I am pretty certain a majority of the players would rather see much shorter queue times then a more evenly distributed rank match.

I posted a similar post to his on the bug forum (while including as much of the "template" that was relevant to this issue) yet it was moved to insufficient information. Hopefully one of the comm reps notice this BUG, as that is what this actually is.

I love Frontlines, but these queues are stupid.

[MageBlack]

I love frontlines too but the queues are pretty bad. I'll set myself up to join then I'll get my son to sit by my computer while he plays his DS and call me when the queue pops. He's gotten pretty good at it and this frees me up to do things around the house.

[Altena]

I love frontlines too but the queues are pretty bad. I'll set myself up to join then I'll get my son to sit by my computer while he plays his DS and call me when the queue pops. He's gotten pretty good at it and this frees me up to do things around the house.

It's not just the times that are bad, the system is literally broken. I would be perfectly fine with a 20 min queue if I knew that I would end up in a match at the end of it - however when an estimated time is 15 mins and I am still in queue after 40, then there is something seriously wrong.

[Felis]

It works like with DPS roles in dungeon duty.
If you are a member in a overused GC, you have a long queue time, because you compete with all the other members of the GC for a party-slot.

You can fix it with joining the Twin Adders ^^

[Tupsi]

Nothing broke about it, welcome to DPS queues.

[Altena]

It works like with DPS roles in dungeon duty.
If you are a member in a overused GC, you have a long queue time, because you compete with all the other members of the GC for a party-slot.

You can fix it with joining the Twin Adders ^^

Job priority does not work at all.
Pretty much every campaign starts with at least one party that doesn't have a single healer in it (until people switch), while another party has 4 healers, 2 tanks and 2 DPS.. The party matching system does NOT work at all. You don't see this kind of result in ST.

Another example (if you refer to my OP), was 3 different players all on the same DPS class. We queued up roughly 5 mins apart. The person that signed up first, actually got a spot LAST.

Nothing broke about it, welcome to DPS queues.

Did you not read my OP at all?

[Barboron]

After waiting this long, the queue finally popped...

<Only taking this first bit as a quote to direct my response to this post as a whole. I didn't want to fill up the post with everything.>

Half your argument is just invalid, wrong, or misinforming.

Sure, pressing commence and having your registration withdrawn does happen, it happened to me also. This isn't happening exclusively with Frontlines though.

As for wait times displaying 20 minutes and the actual time taking 40 minutes, you're obviously failing to pay attention to where it says "Average Wait Time", 'Average' being the key word here. Just because the queue doesn't pop on exactly 20 minutes, does not mean that anything about the queue is "broken". If it's average, some will have a longer queue, some shorter.

As for the joining in progress, this could have been mere coincidence. Another player in the data centre may have had that space and not have pressed commence in the time you were trying. That would be why you had the chance to change jobs several times before actually getting in.

It's not just the times that are bad, the system is literally broken. I would be perfectly fine with a 20 min queue if I knew that I would end up in a match at the end of it - however when an estimated time is 15 mins and I am still in queue after 40, then there is something seriously wrong.

the system is literally broken

literally broken

literally

No, just no. And again...

when an estimated time is 15 mins and I am still in queue after 40, then there is something seriously wrong.

[Altena]

Half your argument is just invalid, wrong, or misinforming.

We have literally spent days testing what is posted in my OP.

Sure, pressing commence and having your registration withdrawn does happen, it happened to me also. This isn't happening exclusively with Frontlines though.

While true, it is still a bug that needs addressing.

As for wait times displaying 20 minutes and the actual time taking 40 minutes, you're obviously failing to pay attention to where it says "Average Wait Time", 'Average' being the key word here.

As mentioned, "average wait time" may be 20 mins, but when 3 people are sitting there for 40+ (even closer to 60 on some occasions), then the "average" wait time is not very average is it?

Just because the queue doesn't pop on exactly 20 minutes, does not mean that anything about the queue is "broken". If it's average, some will have a longer queue, some shorter.

As above, I don't expect the time to tick over to 20:00 and the queue to pop. I am not stupid. However when the "average wait time" over the course of 2-3 hours sits around 15-20mins with queue times of 40+, it is not average at all.

As for the joining in progress, this could have been mere coincidence. Another player in the data centre may have had that space and not have pressed commence in the time you were trying. That would be why you had the chance to change jobs several times before actually getting in.

This was tested on multiple accounts (admittedly I only cycled jobs and got in with SCH once), however when the game was running for 5+ mins (yes I did actually attempt to do this over a 5 min span, waiting a minute or so on each class), then after finally getting in on SCH, there were still an additional 3 slots unfilled.

I find it extremely hard to believe that it took 5 mins of constant withdraws for the queue to finally hit me.


However since you are so sure that there is nothing wrong, please explain why someone who queues into Frontlines BEFORE someone on the same class, actually ends up getting a pop AFTER. The priority system is poor at best.

[Codek]

The average time tracker doesn't take consideration on what GC your joining as (it was originally built for a jobs based comparison). For every 1 Immortal Flame 1 hour queue, there is 4 Twin Adder 15 minute queue's. Average wait time for all players = 24 minutes.

This oversight is becoming more clear and skewed each passing week as more players jump ship from TA...

[Felis]

Job priority does not work at all.
Pretty much every campaign starts with at least one party that doesn't have a single healer in it (until people switch), while another party has 4 healers, 2 tanks and 2 DPS.. The party matching system does NOT work at all. You don't see this kind of result in ST.

Another example (if you refer to my OP), was 3 different players all on the same DPS class. We queued up roughly 5 mins apart. The person that signed up first, actually got a spot LAST.



Did you not read my OP at all?

Amount of GC members, not job. It only match enough people of the same GC together, regardless of their job (job matching is turned off for Frontline)

Example:

Amount of people who want to start Frontline at the same time
Twin Adder = 72 members
Immortal Flames = 100 members
Maelstrom = 500 members

Everyone in Twin Adder have instant access (in the example) while the ones in Maelstrom can have the longest queue time.