- Hunger for Blood will increase damage by 10% instead of 15%. Assassination rogues needed damage, but they got too much, and this will bring them back. Sorry rogues -- the tooltip, we're also told, might not change right away.
- Scourge Strike will crit only once, not on the shadow portion of the damage. "This change just proved to be too bursty in PvP and provide too much sustained damage in raids." He also gives lots more explanation of the change on the forums -- this one will be discussed quite a bit.
- Rolling Corruptions will no longer use the initial haste value indefinitely. More of a bugfix than a change, says GC -- the haste value should drop out to normal after a few ticks of the spell.
Posts with tag bugs
Some of the issues have been addressed, some haven't.
Blizzard has released the first part of the list of known issues with patch 3.3. It will be expanding in the future, so don't get too upset when you don't see a bug on it. Remember that it typically takes a couple days for a patch to get all its kinks worked out. Just hang tight, enjoy some some lore and trailer action, and things will be fixed before you know it.
The full list of known issues after the break.
We've been sitting on this one for a few days now to let people have their fun before we draw a little too much attention to it, but there's a rather interesting bug in the patch 3.2.2 client: you can glitch out the model being loaded for your character upon login, and switch it with that of another character. We don't know how long it's been around or how long it will stay, but watch the video above (which is pretty large, our apologies) for a demonstration.
The WoW.com staff has confirmed it works, though the timing required is very precise. You need to be quick, but being too fast hitting one or the other is just as bad as being too slow. A few of us found that we had to slow down our fingers to do it properly, because "fast" to a hardcore FPS gamer is very different than "fast" to a casual MMO gamer. Click first, hit enter second. Not the other way around.
Whether this falls into exploit territory or not, we don't really know. What we do know is that the model 'swap' is only visible for you on your client, nobody else sees it, so nobody else should be impacted by it. It's also only graphical, no benefits carry over from one character to the next. You might see your epic iLevel 258 shield on your level 1 rogue, but you won't have the stats. You can't be a Horde draenei to anybody but yourself, so no screwing with people in battlegrounds. You can't be a unique snowflake like an undead paladin to anybody but yourself.
It's a whole lot of fun to see what a draenei rogue would look like, or a gnome druid. Check out the gallery below to see what came out of WoW.com's experimentation, and a few from our friends, too.
Gallery: Patch 3.2.2: Model swap bug
Unfortunately, the issue that originally got the app pulled off the store hasn't actually been fixed: the official blurb is now saying that you should definitely remove the authenticator from your account before you upgrade, and then re-apply it again to your account after you've upgraded (and presumably gotten a new key installed). If you install this new version of the app and then try to access your account, it won't work (and you'll have to call Blizzard support at 1-949-955-1382 to help them remove the old authenticator).
Small hassle to go through, however, to have an account protected against hacking. If you have an iPhone or an iPod touch and haven't picked up this application yet, now's the time to do so for sure.
[Thanks to everyone who sent this in, especially Eric!]
And if you've heard something you'd like to respond to on the show, feel free to drop us a note via email -- the address is firstname.lastname@example.org. We'll see you next Saturday as usual, thanks for listening!
Get the podcast:
[iTunes] Subscribe to the WoW Insider Show directly in iTunes.
[RSS] Add the WoW Insider Show to your RSS aggregator.
[MP3] Download the MP3 directly.
Listen here on the page:
I've talked here before about just how wacky Blizzard's coding is -- they are obviously great programmers (even with all of the 180,000 bugs), but man, when things go wrong in this game, they go wrong in the weirdest, strangest ways. Take the bug above, spotted in patch 3.2.2 by xella over on Livejournal: the female dreanei /train emote is bugged like crazy, but instead of not playing or playing a random sound like you might expect it to do as a software bug, it instead plays a cacophony of the strangest sounds, including a slice of the original sound and then a female blood elf /chicken noise instead. This will surely be fixed soon (and as a few people in the comments over there say, it's probably a bit of file corruption on Blizzard's part), but what a weird bug.
Fortunately, as granular and strange as Blizzard's bugs are, their fixes are just as minute: tree druids will be happy to see that, since patch 3.2, their treeform now actually moves correctly after Levitate is cast on it. It's a small change, sure, but every little bit helps with immersion. Maybe someday we'll see mounts do it, too.
One of the more stunning things to come out of the keynote, which we'll have fully written up for you later today, is the fact that there are just under 180k bugs Blizzard is tracking in WoW. That means their bug database has 180,000 entries which are in some stage of being fixed (have been fixed, have not been fixed, or being worked on).
To me this number seems very large for a video game. I can understand an operating system like Windows 7 having an unreasonably large number of bugs in it like this, but for a video game -- even one as complex as WoW -- that number is quite astounding.
It does raise the inevitable question: what is Blizzard doing to fix all these? And how does this relate to the extremely long wait times for GM contact in game? We also learned that Blizzard only employs 2500 worldwide in Customer Service. That includes things like phone bank operators, GMs, forum mods, etc...
Of particular note with this patch is fixing of the "dump macros" that were being used by numerous rogues. Ghostcrawler hinted earlier in the day that there would be a fix for this soon, but it's surprising to see it solved so quickly.
There are also some graphic fixes in the game that many people should be pleased about. In particular for Mac users.
The full announcement, including patch notes, after the break.
Unfortunately, there's no fix yet -- Blizzard says the issue is known and reproducible, and they're working to put a fix in "the next patch" (originally they say it'll be in a PTR patch 3.2.2 build, but a hint at the end of the thread suggests we may see it even sooner than that). So if your Mac has one of those graphics cards installed and you're having this issue, just sit tight -- Blizzard is working as fast as they can to get a fix out to you.
And of course we'll answer your email as well -- you can send us whatever you'd like us to read or talk about at email@example.com. It all kicks off at August 8, 2009 3:30 PM EDT over on our Ustream page, or, as always, you can find the embedded stream below. Be sure to stop by this afternoon and give us a listen live -- you'll enjoy it, or your money back*!
Note: As the podcast is free to listen to, you will not be receiving any money back. But you will enjoy the show. If not, you can blame the Ret Monkey. That's what we do.
This laundry list of issues comes after yesterday's first round of in-game hot fixes. Based on previous patches, I wouldn't be surprised to see another round of hot fixes released tonight.
Some of the more major bugs in patch 3.2 that are on Dresorull's list include:
- People are getting stuck in the portals to the Argent Coliseum raids.
- The Flying Carpet requires 410 tailoring to craft when only 375 is attainable at level 60.
- A number of items are displaying different textures in 3.2.0 from how they looked in 3.1.3.
- Master's Inscription of the Crag has not had its MP5 value increased.
- Some Stormjewels are still unique-equip.
The full list of known issues after the break.
Blizzard's statement today clearly informs us that all the extended maintenance we've been seeing is directly due Blizzard implementing fixes for the problems server-side. While the statement comes from an EU source, once can assume rather easily that it applies to the US as well.
While no timeframe is given as to exactly when this will be done for all realms, it is very good to know that stuff is getting done behind the scenes. And this look at exactly what Blizzard is doing to their servers represents a rare glimpse into their inner workings. Usually Blizzard is pretty tight lipped about what exactly is happening with their hardware.
The full statement after the break.
Speaking of achievements, while we have our guide to the Achievements of Midsummer, you might not be able to make a significant dent in them today if you made rounds with the flames last year. None of the quests seem to have reset from last year, so getting your hands on the holiday currency to buy the items you need is going to be difficult, to say the least. By difficult, I may or may not mean borderline impossible.
I don't expect this to be a permanent issue, we'll probably see a hotfix sometime in the near future since the problem is already being checked out. Of course, that's assuming the issue is something that can be hotfixed. If not, I don't doubt we'll see a fix of another flavor down the road. I don't foresee Blizzard keeping What a Long, Strange Trip It's Been out of players' hands because of something like this. In the meantime, at least you can still take a crack at Lord Ahune.
Gallery: Midsummer Fire Festival 2008
Such things will be determined largely via polls right here on the front page of WoW.com, where I'll be giving weekly updates on my progress along with what I've learned about the class and the world and any other observations I might have. If you want a little more detail on the process such as where I'm going, what I've done, and any other little notes I make via the Adventurer's Note feature, you can follow that on my profile. If you don't dig our profiles portion of the site, hey, no problem. You'll still get weekly updates right here on the blog until I'm level 80.
There are two polls: Race and Class. I will play whichever choices are the most popular. If the chosen race can't actually be the chosen class, I'm going to go with whatever is the most popular class that I can actually play as that race. The polls are below, and there's a little more information behind the cut underneath them.
Update: Polls will remain open so those who voted can still see the results, but as of May 22nd, Gnome Warlock won the polls and the adventures have begun.
|Blood Elf||1880 (10.7%)|
|Night Elf||1485 (8.4%)|
If this is how you try to lower the lag Wintergrasp causes on servers, I think the quote "ur doin it wrong" applies. In all seriousness, I'm kidding about that and this is obviously not working as intended. Considering the Mark and Honor gains people are getting from this, I wouldn't be surprised if we see some emergency maintenance and rollbacks soon. I wouldn't get too attached to your gains this afternoon.
Filed under: Bugs