Username
Password
Maximum number of Battlegrounds Queues reduced to 2 in 3.2.2
All of the User Interface changes in 3.2.2 to the Battleground queuing system are to help address matches starting with uneven numbers on each team. These changes may not fully address the situation, but in that case we have some other possible solutions we can implement further down the road.
From the 3.2.2 PTR Patch Notes:
•Players may now only queue for no more than two Battlegrounds at a time.
•The dialog box for entering a Battleground match has been changed to reflect the following options: “Enter Battle,” “Leave Queue,” and “Minimize.”
•The time a player has to enter a battle when selected has been reduced to 40 seconds when not already in a Battleground and 20 seconds when in a Battleground.
•Players already in a Battleground can now choose “Enter Battle” for a new Battleground under any circumstance (i.e. while dead, in combat, falling, etc.).
•A new Battleground will not launch until the maximum number of players on each side are in the queue (i.e. 40 players per side for Alterac Valley).
Implementing Tenacity in Battlegrounds
That's highly unlikely. We'd rather exhaust every measure possible -- which we have not as of yet -- to get the matches even rather than just concede that it can't be done and implement something like Tenacity as a result. Tenacity can be controversial and isn't designed for instanced PvP. Besides, I doubt most players would like to see Battlegrounds arbitrarily balanced by a buff rather than by numbers of players on each team.
Next Classes Q&A Series
The timing of BlizzCon next to the priest Q&A made conducting a short follow-up Q&A difficult. With all of the recent announcements coupled with the 3.2.2 testing process, we're looking to start another round of class Q&A's in the near future. We don't have a class order yet, but it shouldn't be the same as the last one. We're in the process of discussing ways of improving the Class Q&A Series, looking at what worked well the first time and what didn't.
Death Knight
Scourge Strike vs. Obliterate in 3.2.2
Scourge Strike does appropriate damage given that it ignores all armor. The problem with Obliterate, we believe, was because so many talents and glyphs propped it up more than Scourge Strike. In a PvP scenario it's pretty unlikely your target will be sundered at all, in which case Scourge Strike will generally beat Obliterate anyway.
