Patch 3.2 gives Wintergrasp a queue
Here's a change that will probably be by turns amusing, exasperating, or a relief, depending on who you are and how you play: In a new section recently slipped into the official 3.2 PTR patch notes, Blizzard revealed that they plan to add a queue to Wintergrasp in Patch 3.2. In short, you can queue up by visiting a Battlemaster or entering the zone within 15 minutes of the game start. Only 100 people will be allowed to fight on each side of the battle, to be chosen randomly from the battlemaster and from the zone, with level 80s receiving highest priority.
When Wintergrasp was first introduced, even people who otherwise disliked PvP found it fun, and some old-timers found it be about the closest thing to the fabled world PvP battles of old in Hillsbrad, Ashenvale, and other such places.
Unfortunately, Wintergrasp has found itself the victim of far too much popularity. The fun factor aside, it's also one of the easiest way to grind honor, heirlooms, and epic gear you'll find in game, and it got so overcrowded that it would often destabilize whole servers when a battle was active. Blizzard tried numerous ways to combat these problems, including preventing lowbies from afking in zone to gather free honor and reducing the daily quests to weekly quests.
Apparently, none of these measures have worked to their satisfaction, and instead, they've simply placed a hard cap on the whole zone, arguably turning it into just another battleground that happens to occupy the same space as a PvE farming zone. While Wintergrasp may have been first meant to be a break from battlegrounds or an attempt to give people back the epic World PvP they remembered from the old Hillsbrad days, it seems Blizzard's found the whole concept a bit too overwhelming.
On one hand, it's a bit disappointing to see these changes. It's a lot of fun to get into a good chaotic PvP melee and do some damage. That may be one of the reasons the old hours long version of Alterac Valley was one of my favorites battlegrounds. On the other hand, if it means less lag overall for everyone, it may just be a sacrifice worth making, even if it will suck when one is not chosen for the battle.
Besides, 100 people is still an awful lot, more than, for example, those old 40- person AV days I was waxing nostalgic over a few sentences back. It'll be interesting to see how balance works out on this change, mostly. Will 100 vs. 100 show any glaring flaws on the offense or defense? If nothing else, it'll be a handy excuse to use when you lose, I'm sure.
For your convenience, here's the notes on the system as they appear in the most recent official patch 3.2 PTR notes:
Wintergrasp
To provide players with a more transparent notification of when Wintergrasp battles occur, as well as better control zone population and stability, several changes have been made.
- Players now have the option to queue for Wintergrasp from a Wintergrasp Battlemaster in any capital city or by simply entering the Wintergrasp zone.
- Queuing will begin 15 minutes before each battle. If chosen, you will automatically be teleported to the zone. Any players in the zone who have not been chosen from the queue will be teleported out when the battle begins.
- The queue system remains active for the entire battle. As soon as a player leaves, a new one will be chosen from the queue.
- Trying to enter Wintergrasp during an active battle for which you have not been chosen will teleport you out. Please note that, as you are now able to fly over Wintergrasp, you will only be teleported out if you try to land and join the battle.
- Level 80 players get higher priority in the queue than lower level players. In addition, a random selection of queued players will be taken from both the Battlemasters and the zone itself.
- The queue will accept up to 100 players from each faction, resulting in a maximum battle of 200 players at a time.
Patch 3.2 will bring about a new 5, 10, and 25 man instance to WoW, and usher in a new 40-man battleground called the Isle of Conquest. WoW.com will have you covered every step of the way, from extensive PTR coverage through the official live release. Check out WoW.com's Guide to Patch 3.2 for all the latest!Filed under: Patches, Analysis / Opinion, News items, PvP, Battlegrounds
Patch 5.3 interview with Ghostcrawler
Mystery of the Unborn Val'kyr
The latest patch 5.3 news
All of the latest Mists of Pandaria news





Reader Comments (Page 3 of 7)
Termdeath Jun 20th 2009 12:12PM
If they're going to implement a queue, why not ensure that not only is it hard capped at 100, but that each side is balanced. At least on my realm tenacity still doesn't do @#$% to balance the fight.
Jetstream Jun 20th 2009 12:12PM
Okay, I'm so sick of people crying about stuff like this.
Get a CLUE folks. The server hardware to allow for a fully open battle like that to happen efficiently does not exist. Would you guys prefer that they left it like it is, still crashing realms and lagging them all over the place? They have to put restrictions on it, it's the only way they can have their game remain playable.
Warhammer tried to make this work. It doesn't. I don't even know why Blizzard tried it. It should've been a battleground from the start, but they wanted to do something awesome... But something UNTENABLE.
theRaptor Jun 20th 2009 12:37PM
So EvE:Online doesn't have multi-hundred per side battles happen nearly every day? /roll eyes.
Blizzards problem is that they won't pay for the hardware to do this (the EvE cluster features in the list of the worlds most powerful supercomputers) and won't put in simple stuff like an option to default everyone to a single design per race/class combo. In a big PVP battle like WG I really couldn't be bothered noticing whether the DK that is killing me is wearing T7 or Ulduar Hardmode gear.
God I wish they would do this just so that Dalaran wouldn't bring my computer to its knees. Why MMO designers don't have a "replace all models with grey boxes" option when they know they will never eliminate all engine based lag is beyond me.
Taladan Jun 20th 2009 6:32PM
@theRaptor: Blizzard said, more than once, that they have top notch hardware, so I guess the problem is not the hardware.
Chat works flawlessly during the highest lag, so it's not a network problem.
There is just one piece nobody mentioned that it's probably the cause of the problem and, just for the fun, I'll leave it to the reader to find out (tip: I'm a software developer.)
Verit Jun 21st 2009 12:22AM
There's a lot of things eve does that wow doesn't. 64 bit software on their servers, stackless i/o - which allows nodes to talk with other nodes without going through the OS, and they use ram-san's to speed up database i/o. Yes I've played eve and been in systems where there are thousands of people and it works really quite well - CCP solved this issue, and they are a 20th the size of Blizzard.
The big problem with fitting more than a hundred players in one area is getting and distributing information rapidly - in otherwords, if you have a Ferrari you can't drive very fast with shopping cart wheels. To a certain extent - putting more cpu/memory at the issue is waste of money if the software can't use it.
Volaro Jun 20th 2009 12:15PM
Ugh, Blizz slowly killing Wintergrasp
Kikr Jun 20th 2009 12:15PM
:(
Zumacrume Jun 20th 2009 12:16PM
Pretty terrible fix.
Avan Jun 20th 2009 12:20PM
Bad, bad decision. I'm going to enjoy farming eternals, fish, herbs, and minerals now. That way, I'll just love it when I'm teleported away before I can finish looting everything.
Horrible decision.
Avan Jun 20th 2009 4:15PM
Try farming WG for 4 hours at a time.
Meg Jun 20th 2009 5:46PM
Agreed entirely. This change is pretty shitty for those of us who like to lurk in WG just to farm, whether there's a battle going on or not.
T Jun 20th 2009 12:23PM
I hate to hear that news, especially the random chance the queue provides. It sounds more like a lottery.
However, WG is unplayable more often than not, especially in cases like last night, where 200+ Horde were present. Who knows how many Alliance were there, and I'm not on a high population server. In short, I understand Blizz is between a rock and a hard place. I'd rather take my chances with a lottery/queue setup. Hopefully the lessons learned here can be applied in the next expansion.
It is too bad that they can't run multiple instances of the zone at once. I don't know if they don't have the server capacity, or if the code limits them. City of Heroes could make multiple versions of a zone if it got too crowded, and it seems a similar feature would make Wintergrasp far more playable.
Then again, given that it can take 15+ minutes to enter a 5-man instance these days (Additional instances cannot be launched), I suspect Blizzard may be having some server capacity issues that they aren't willing to talk about.
Sengir Jun 20th 2009 12:24PM
This is absolute crap.
pietrex Jun 20th 2009 12:27PM
I don't do Wintergrasp, but I dislike this change as well. It will irritate many people. What about farming people and fishermen? It makes no sense. I know they want to fix the lag, but there must be other ways to do this.
Valt Jun 20th 2009 2:00PM
You dont fish during war. You fight during the war. This change is FOR BATTLE not for whole area itself. I see no problem farming after the battle is over.
woodworthemail Jun 20th 2009 12:37PM
Are they going to also fix it so both sides have a similar starting point? Having a ton of people waiting nearby to cap a point at the very start of battle or dropping in on the fortress is pretty lame as well.
Daraia Jun 20th 2009 12:43PM
While I don't care for this it IS one way to deal with an exploit we see a lot on our server where players log out just before the battle concludes with full rank then log back in just as the battle begins and start popping out siege engines.
Over all I don't think Blizzard would have ANY chance of making EVERYONE happy with any changes they make to Wintergrasp. You either Love it or hate it.
Panduh Jun 20th 2009 12:43PM
two things i see about this change....
1. on my server (Khaz Modan), we get about 2- 2.5raids on ally side and about 1 -1.5 raids horde side (sux for horde i know) which brings that to about the cap they are mentioning here, and gets rid of lowbies farming honor by mooching off of 80s and puts 80's first.
2. people will just start complaining on forums and eventually blizz will cave, the way i see it, i had 512 MB of ram on my comp and completely hated WG with a passion, cuz i would either get DCed, enter the fortress and then my screen would freeze, only to reappear 5 mins later at a GY fully rezzed and almost logged out by afking. then i got (recommended by blizzard for this game mind you) a 1 gig of ram card for my comp, i am now beautifully allowed to take quiet strolls (well not so quiet, and more like panicked sprints) thru the middle of WG Fortress with about 80v 80 going on, and maybe casting a couple fears, CoA, or Death Coils here and there followed by a mad cackle. the point of # 2 in my post being, get more ram ppl itll help ALOT (i couldve maqde the ram thing a 3rd thing on my post huh? lawl)
Kole Jun 20th 2009 1:17PM
I have 4gb of RAM and I was STILL dc'd constantly (usually only once we were all storming the keep.) RAM is not the be all end all solution. It helps for sure but it isn't everything.
Panduh Jun 20th 2009 2:35PM
then something is terribly wrong my friend, 4gigs of ram u should be able to stand in the middle of WG with all horde and ally stacked on top of each other, vehicles inckuded shooting off every aoe and colorful spell this game has to offer, with all details spiked up to best performance, unless ur other comp prefrences (motherboard, vid card etc) are total crap