Wintergrasp disabled
by Adam Holisky 
May 19th 2009 at 8:50PM
We noted an error earlier this evening which was causing the Lake Wintergrasp PvP zone to be reset prematurely. Since ending epic battles early is a bad thing, Blizzard has gone ahead and "shut off Wintergrasp" completely for the time being.This change is affecting all realms.
There is no word when a fix will come through, but we're hopeful it will happen sometime soon. Disabling an entire part of the game is a big thing, and an error that usually is corrected quickly.
Some speculation points to the change in daily (now weekly) quests that just went in, however there is no evidence to support this.
Filed under: Bugs, News items
Reader Comments (Page 1 of 3)
Gemski May 19th 2009 8:54PM
Wonder if I'll lose all those marks and honor...
Stomy May 19th 2009 9:30PM
Poor WG it's been a pain in blizzard's side since they launched WotLK, for once i think blizz was a little to ambiguous.
epic May 19th 2009 9:32PM
we didn;t last time...but who knows...i converted it to gear then shards then gold b4 the server went down
Amaxe May 19th 2009 9:56PM
I suspect the problem is that it is pvp sharing the same server as pve as opposed to battleground servers is causing it to be hard to control. Wintergrasp tends to be the only pvp I like, and I might actually miss it at times, but perhaps they need to rethink it?
nick May 19th 2009 8:55PM
AQ picture = ?
Veg May 19th 2009 8:59PM
AQ picture = BUGS
Sumanai May 19th 2009 8:57PM
Bugs? :P
Ancro May 19th 2009 9:11PM
The Qiraji have infiltrated Wintergrasp? Nobody tell the night elves, they get touchy about that kind of thing.
Rofllol May 19th 2009 9:11PM
AQ picture is to represent the bugs in wintergrasp. lol nice one
Adam Holisky May 19th 2009 9:12PM
Some people get it ;)
Adam Holisky May 19th 2009 8:56PM
"First" posts are not appreciated here. Continued "first" posts will result in being banned.
Thanks.
Luisette May 19th 2009 8:58PM
As much as I grieve for the loss of a raid and Stone Keeper's Shards, let me be one of the first to celebrate the lag reduction.
/cheer
Ada May 19th 2009 9:00PM
"This is change is affecting all realms."
Extra is, just to let you know
epic May 19th 2009 9:29PM
wg just restarted on my realm proodmoore everything seemd fine ...'cept for the tanks seem to do less dmg now...and i;m in all 213+ with 3 219s and 226 ...i thought we were supposed to do more dmg based on ilvl
Fennrier May 19th 2009 9:14PM
Sorry
DY357LX May 19th 2009 9:03PM
"Disabling an entire part of the game is a big thing, and an error that usually is correctly quickly."
Correctly quickly?
Is that LOLCat?
Doobs May 19th 2009 9:05PM
Luisette, well right now, the WG buff is stuck on alliance. meaning they can collect a ton of Stone Keeper Shards if they want (provided Blizz doesnt roll the tables back).
I have to say though, with the shorter times, WG was a lot more fun than normal. tons more fun. In the end, on the server which I play, alliance actually worked TOGETHER. It was a beautiful thing to see. A rarity.
I wish the WG battle occurred more often in the day. I hate logging in at night only to see I missed it by 10 minutes and I need to log in 2 hours. :c/
Luisette May 19th 2009 9:09PM
@Doobs:
I haven't logged in yet today, so I was unaware that the buff would still persist even through disabling WG. From a rational train of thought, I can almost guarantee they'll do roll-backs on the shards collected... because otherwise, there's going to be hell from the losing faction on every server affected.
But then again, this is Blizzard, and sometimes what's "rational" isn't always "implemented". God love ya Blizz, but sometimes you blow my mind.
epic May 19th 2009 9:37PM
i wouldn't guarantee anything...the alliance one had wg for three days after a wg freeze during i think the 3.0.8 "hey lets give everyone in the northrend the essence of WG buff at the same time... that won't cause problems" bug...there was qq, but no shard claw backs
Zeplar May 19th 2009 9:04PM
It just restarted on my server.