non-instanced
Latest
Wintergrasp lag a big issue after patch 3.1
Zarhym has got some answers to the widespread problem of lag in Wintergrasp after patch 3.1 the other week. He says Blizzard figures the problem is simply population based -- there are many more people playing in the battleground than there were before the patch. For that reason, they're having trouble coming up with good solutions: the battleground is designed to be non-instanced, and that's why a lot of people like it, so putting a limit on the amount of people in there is not the way to go. Hardware isn't a solution either -- Blizzard's hardware is already top-of-the-line, and not only would upgrading it take a while anyway, but my guess is that most of the lag issues come not from Blizzard's side, but from the connections between players and them, which they may not have any control over anyway.So yes, we're more or less out of luck -- as long as Wintergrasp is extremely popular (and even Zarhym remembers the naysayers before the release with a smirk), there will always be a certain amount of lag in there. There are a few good suggestions floating around the comments thread -- one is that Wintergrasp should always be conquerable, which seems like it would keep down on the flood of people, though of course there'd be other issues if that were implemented.At this point, Wintergrasp lag may just be something we have to live with. Eventually, you have to think the population will drop back down, and then those of us still in there will enjoy lag-free battles again. But Blizzard has taken on quite a goal trying to do non-instanced PvP full of vehicles and towers without any lag at all.
Trying out the new Wintergrasp
The new Wintergrasp, I am here to tell you, is a lot like the old Wintergrasp. Which isn't a bad thing -- though Blizzard has made a few significant tweaks to the game's big non-instanced battleground, it's still the same match it's been (and a good match it is, if you ask me). The main difference is that all of the workshops outside the keep are now up for grabs, so the defending team can now not only take out the southern towers to knock some time off the clock, but also lock down the workshops to create a vehicle shutout. That's tough to do, in my experience, though -- even if you grab the two lower workshops, it leaves the top two open for attack, and odds are that the lower two workshops will really only be taken if all of the towers are down and the vehicle drives down south need something to do.So the gameplay hasn't been changed that much, but it is nice that the requirements for the daily quest have been lowered -- we now only need 10 kills of the other side, and there are more NPCs around to count for those kills, so I actually finished both the kill and vehicle quests without even trying. It would be nice for Blizzard to somehow streamline the raid invite/share quests process that happens everytime WG begins, but they're leery of that, given how honor farming was such a problem in the auto-invite AV. And I have one personal request: Blizzard, can you please have me auto-dismount when I try to pick up an RP-GG? I'm fine with not mounting while I have one, but every single time I try to pick one up I get that error message, when all you need to do is auto-dismount me like any other object I use while mounted.The biggest WG change isn't even in the battleground, it turns out -- most of the players I've talked to are just thrilled that you can now fly over Wintergrasp on the way from Dalaran to Sholazar Basin (and it figured 3.1 would drop a week after I finished the Oracle rep grind). I've even heard you can get credit for winning the BG if you're in the air when your side wins. Though a fix for that will probably have to come during the next round of WG improvements, whenever that will be.
