frostbreeze wrote: »So during prime time and when there are hundreds of ppl trying to queue in u can never actually get into a bg.{it says someone declined the invite for 4hours+ while you can see that everyone usually accepts}.This problem goes away in the morning and late at night when there are not that many ppl playing. Excuse me if im wrong but shouldnt it happen the other way around?When hundred ppl want to play they should play faster and when 12 ppl want to play they should wait a bit longer? I think theres a problem with ur server overloading from the insane amount of ppl that want to join bg during prime time.Can your server only support 5 bgs active at the same time or something? Plz do something about this
frostbreeze wrote: »So during prime time and when there are hundreds of ppl trying to queue in u can never actually get into a bg.{it says someone declined the invite for 4hours+ while you can see that everyone usually accepts}.This problem goes away in the morning and late at night when there are not that many ppl playing. Excuse me if im wrong but shouldnt it happen the other way around?When hundred ppl want to play they should play faster and when 12 ppl want to play they should wait a bit longer? I think theres a problem with ur server overloading from the insane amount of ppl that want to join bg during prime time.Can your server only support 5 bgs active at the same time or something? Plz do something about this
Some improvements... great. AKA This will never workLong queue times for Battlegrounds (Fix coming in patch v3.0.6)
You may run into situations where the queue time to load into a Battleground are excessively long. We've been actively working on this issue, and have some fixes scheduled for patch v3.0.6.
More than four players can appear to be on the same team in a Battleground (Improvements coming in patch v3.0.6)
Battlegrounds should only support up to four players per team, and there are some cases where more than four players are appearing on the leaderboard. We have some improvements for this issue coming in patch v3.0.6.