Cluster Queue Abuse and Proposed Solution

    • Cluster Queue Abuse and Proposed Solution

      Today was the worst cluster queue experience I have ever had. Conflict joined a fight in Avalanche Incline fight with ~55 people.
      When we joined the zone, the cluster queue was not active and our allies came in behind us before cluster queue was activated. We went to the territory to fight with Take Care/Last Warn.
      Cluster queue started not long after the fight actually got started. We had a small skirmish with minimal casualties on all sides and ARCH joined the zone triggering an adjustment.
      When they zoned in, we lost about half of our force. Putting us around 25-30 people. We continued fighting.
      Then, POE joined the cluster queue. Once this adjustment took place, we were now at ~15 people in the zone.
      Our force of 55 was reduced to 15 in about 5-10 mins.
      Unfortunately, the fight was SQUAD versus the world with us getting pincered between ARCH and TC/Last Warn (therefore obviously working together).
      Due to the cluster queue adjustments, the whole SQUAD force of about 200ish was reduced to 60 people in zone. We were killed before POE could even join the fight.

      Therefore, I would request to add a backoff to the cluster queue adjustment timer.
      This means the cluster queue timer would be adjusted to a longer duration based on the number of people attempting to join the zone.
      This would attack groups attempting to bring numbers just to force more people out of the zone. Every 50 people over the cluster maximum should add 2 minutes to the queue adjustment timer.

      For the following examples I will use a cluster queue maximum of 200.

      This means that in a 100(Group A) v 100(Group B) fight where 100(Group C) people show up, Group A and B will be allowed to fight for 4 minutes before Group C is allowed to zone in.
      This means there is an incentive to deploying your forces to the zone you care about because if enemies take the field first, you may lose objectives because you need to wait out the cluster queue timer.
      Say an additional group of 50 people (Group D) show up after Groups A, B, and C are in the zone (67 each inside the zone and 33 each in the cluster queue). They would need to wait (200 - 350)/50 = 3 * 2 = 6 minutes before they can zone in the adjusted part of their force.

      If you are willing to commit 500 people to a single zone(200 in zone and 300 in queue) and someone wants that fight, they would be forced to wait 12 minutes to get into the zone.
      Most importantly, if the smaller force is winning, your reinforcements would be forced to wait 12 mins after people started dying before they can help. So committing that many people to the fight is discouraged.

      This also attacks the "Run until you have allies" strategy that we have seen in large scale lately.
      This strategy encompasses deploying large numbers to a zone so enemies will commit to that zone. Then when a similar sized blob joins, the large force will leave until they can get more allies for the fight.
      In this case, when 200 (Group A) hold a zone and 200 (Group B) join the queue, it will be a 10 minute timer for Group B to zone in.
      If Group A chooses to leave the zone and come back with 400, they will be forced to wait 16 minutes for the cluster to adjust again and they may lose their objective as a result. So basically running is giving up rather than a stretching strategy.

      The last case would be when people are streaming into the zone. Say there is Zone X that is already at its cluster queue ize of 200 and it is in the middle of Zones Y and Z.
      Inside the zone, there are Group A (100) and Group B (100).
      Group A has 50 people that just showed up from Zone Y triggering the cluster queue timer of 2 minutes.
      1 minute later Group C shows up with 100 people from Zone Z.
      At this point, there are 200 people in the zone fighting and 150 people waiting to join.
      Therefore, the join timer is extended from 1 minute remaining to 5 minutes remaining since 1 minute has already elapsed and the timer has been adjusted to a 6 minute timer.

      These numbers aren't perfect but I wanted to give some numbers to ensure I could have examples for support.
    • can you pls fix your problem am always playingvevery day and every min im dc. You know whats the worst thing is when you go back to your account all gone because of fucking lag and disconnected i was been afk free to kill to everyone. I hope im not the only one here. Its just heart breaking your doing your best but only lag and disconnection will ruin your game play.
      :sleeping: clap
    • FrozenIce wrote:

      KickinMACHINE wrote:

      POE is using the queue the same way as squad was doing so. So classic "no, u" happening here. We should all go solo guilds season 9 to prevent such problems in future.
      Please share your video of SQUAD zoning in and out of a zone with large numbers to force people to zone out.
      You guys were literally practicing all the mechanics to stretch them as far as they would go when the cluster que was announced. You guys had so much of an advantage at the time because your numbers were large. Now you come in crying about these mechanics when you no longer have the numbers while all the other guilds just want you guys removed so a new alliance/guild can take over. It's the way of the Albion life.

      PoE and OOPs were once in your position.You and your guild was on the side that outnumbered them to death at that time, nothing was done to help them "even" the playing field. In fact, they were actually punished during those times because SBI introduced the cluster GvG timers as well as the one character per GvG per day in a certain radius as far as zones go.

      So based on past standards of teaming up to get rid of someone, they should be NERFING you, not offering help to you.
    • KingJokerz wrote:

      FrozenIce wrote:

      KickinMACHINE wrote:

      POE is using the queue the same way as squad was doing so. So classic "no, u" happening here. We should all go solo guilds season 9 to prevent such problems in future.
      Please share your video of SQUAD zoning in and out of a zone with large numbers to force people to zone out.
      You guys were literally practicing all the mechanics to stretch them as far as they would go when the cluster que was announced. You guys had so much of an advantage at the time because your numbers were large. Now you come in crying about these mechanics when you no longer have the numbers while all the other guilds just want you guys removed so a new alliance/guild can take over. It's the way of the Albion life.
      PoE and OOPs were once in your position.You and your guild was on the side that outnumbered them to death at that time, nothing was done to help them "even" the playing field. In fact, they were actually punished during those times because SBI introduced the cluster GvG timers as well as the one character per GvG per day in a certain radius as far as zones go.

      So based on past standards of teaming up to get rid of someone, they should be NERFING you, not offering help to you.
      Still true.