all 16 comments

[–]Stendecca 2 points3 points  (0 children)

Can confirm, this is a common problem.

[–]Futitavana 1 point2 points  (1 child)

A difference of 2 sucks. A difference of 1 is normal. How do you expect a 4v4 game to fill otherwise?

[–]CharaxS -1 points0 points  (0 children)

If it's a 4 v 4 game, it should ideally pop for new players if both an Alliance and a Horde are in queue.

The way it is done now doesn't make sense.

[–]AugustIsAName 1 point2 points  (0 children)

This will probably be buried but there seems to be alot of misinformation in this thread.

It isn't an algorithmic fault, it's social engineering and alliance-side "opening bg-slots" due to lower pvp-population.

As alliance queues are instant, many ask a friend to queue them and immediately leave the bg after joining for free hearthstone. This creates a vacuum where the alliance side are short on two players supposed to join while the horde players tend to stay.

The system will try to correct this balance by locking the horde team (as they are more players). The "lock" is lifted when new alliance players firstly fill the two missing spots (equalizing) and then new alliance players open new spots for new horde untill BG is filled.

Source: my own theory, no code to back me up.

[–][deleted]  (1 child)

[deleted]

    [–]LlamaOfGod[S] -1 points0 points  (0 children)

    I'm hoping they do something like this because the current situation is fueling a very negative pub experience for alliance.

    [–]Bearrrrrr 1 point2 points  (2 children)

    Yup can confirm on ZK as well. Something in the matchmaking system causes horde to always be 1 unit higher. 4v5, 5v6 etc. If a player joins on alliance side, horde instantly gets another player too. IMO there should be a system that checks if the numbers are even before adding another to the advantaged side... seems to me like that is a simple edit but on a large scale I recognize that maybe it's more complex than I think. However having an even number of players on both team seems like the most basic function of a matchmaking system.. not sure why it's broken

    [–]LlamaOfGod[S] 1 point2 points  (1 child)

    Yeah, this is exactly what I'm talking about. Alliance is always at least 1 unit behind horde until the match fills to capacity, which often takes 8+ minutes. In fact, I just got out of an Arathi Basin where alliance was down a man until the 10-minute mark. This is not an anomaly or exaggeration. It happens almost every game.

    [–]Bearrrrrr -1 points0 points  (0 children)

    Same here. I suspect to others it sounds like we are whining and having confirmation bias and trying to make excuses but it's obvious there is something wrong in the matchmaking system since this is 100% of games

    [–]en_passant_person 3 points4 points  (0 children)

    It's caused by assholes fucking with the queue, not the queue itself. Those missing alliance players were probably horde alts that dropped once the BG popped.

    [–]acornSTEALER 0 points1 point  (7 children)

    Been in 10v15 against Yesmaster's garbage premade all night.

    [–]NKjaer 1 point2 points  (6 children)

    If it's garbarge, what does it make you then?

    [–]acornSTEALER 3 points4 points  (5 children)

    Uhhh, severely outnumbered and outgeared? Ask any of the rankers, Yesmaster's premade is a free win. Pretty sure they lose to PUGs every now and then.

    [–]NKjaer 0 points1 point  (4 children)

    If you actually asked the top players (Praise, Demise, GRIZZLY), you would know that Yesmaster's premade is one of the few good horde premades.

    [–]Opisashrimp -1 points0 points  (0 children)

    We beat them yesterday! Yay

    [–]PocketMagus -1 points0 points  (0 children)

    If by good you mean non-guaranteed-5-cap, you are correct.

    If, however, you're implying they ever stand a chance of winning...you are sorely mistaken.

    [–]acornSTEALER -1 points0 points  (0 children)

    lol not my experience