Filed under: Bugs

Hotfixes have already been rolled out to correct this, as noted in the latest hotfix blog, but windwalker monks enjoyed a brief, rather confusing, night of crazy DPS. It should be noted that deliberate use of this bug would most likely have been considered exploiting, hence why WoW Insider isn't in the habit of reporting these things until they've been dealt with.

The bug was ostensibly called by combining two abilities together: Rushing Jade Wind and Spinning Crane Kick. The former gives the latter a multiplier, which is supposed to be around 30%, but appears to have had at least a couple of extra zeros accidentally added to the end. As can be seen from the header image, windwalkers were posting incredibly high DPS when using these two abilities together. This wasn't an isolated issue, there were various reports on the forums, as well as videos. Another example can be seen to the right, from Wowmartiean, in the raid finder.

WoW Insider readers will no doubt recall the previous bug with retribution paladins, where Censure had a similar modifier problem, resulting, again, in some disproportionately high numbers. As we mentioned in our recent patch 5.2 PvP round-up, windwalkers were due some buffs, but this seemed a step too far! Blizzard agreed, and for clarity, this is no longer in the game. It remains to be seen whether any action will be taken against anyone who is considered to have exploited this bug, but it has appeared and been hotfixed so quickly that, with any luck, it will not have had any major impact. As Blizzard noted on twitter, they ran rolling restarts to repair this within a very short time of its occurrence, and PvP Developer Brian Holinka noted that a fix was underway shortly earlier.

The hunter level 90 ability Powershot has been plagued with bugs since its launch. The hunter ability, which has a very long cast time so philosophically a high risk-reward, was first described as a skill-shot, i.e. an ability that's aimed by the player, similar to priests' Divine Star. This was used to explain away its constantly missing, with Lead Systems Designer Greg "Ghostcrawler" Street asserting that the problem was players not quite using it correctly, and that the problem was hard to reproduce.

Players then began testing this on stationary targets, cc-ed targets and the like, and found that Powershot didn't even hit the primary target. Back in November, Taepsilum posted on the EU forums, saying that a bug had been identified, but that unfortunately it couldn't be implemented until a client-side patch could be carried out, so likely patch 5.2 at the very earliest -- no promises.

Fast forward to today, and Taepsilum has posted the following:

Taepsilum

Update:

Both Powershot and Glaive Toss have been rebuilt and should now always hit their primary targets, plus, they should also be much more responsive to secondary targets.

This new implementation of the two abilities isn't on PTR yet but will be as soon as both abilities have been through QA. Once we have a new PTR build go live, feel free to test them and provide us with some feedback, this is when it is most important and when it can dramatically change what ends up going live.

source

It's time for those hotfixes again. This time around, we're looking at fixes mostly aimed at raid issues -- Sigils of Power and Wisdom will be dropping in separate raids, that Amber-Shaper Un'Sok will behave himself in Raid Finder, and at long last people who've been soloing the Twin Emperors in Ahn'Qiraj now have a fair chance to get that pet, as both emperors will be tagged and lootable by anyone.

Patch 5.1 Hotfixes - January 22nd

January 22

Raids, Dungeons, and Scenarios

• Sigils of Power now only drop in Mogu'shan Vaults, and Sigils of Wisdom will only drop in Heart of Fear and Terrace of Endless Spring, with a very small chance to drop in LFR Mogu'shan Vaults. This should ensure that players who had access to Mogu'shan Vaults for a longer period of time are now seeing more Sigils of Wisdom.

Heart of Fear

• Amber-Shaper Un'sok
• Un'sok's Amber Scalpel will now always be awarded to the correct classes in the Raid Finder version of this encounter.

Temple of Ahn'Qiraj

• Emperor Vek'lor and Emperor Vek'nilash in the Twin Emperors encounter will now always award loot properly when slain.

Bug Fixes

• Progress towards the "Test of Valor" quest and achievement will now be saved when a character changes factions.

source

---

Mists of Pandaria is here! The level cap has been raised to 90, many players have returned to Azeroth, and pet battles are taking the world by storm. Keep an eye out for all of the latest news, and check out our comprehensive guide to Mists of Pandaria for everything you'll ever need to know.

---

WoW Insider was contacted via twitter by a concerned WoW player who was having some issues with this Horde hub. Chris dropped us a line with a warning that, if we attempted to test Silvermoon's issues, we should do so with a Horde character that we didn't mind benching for a while.

Characters walking into the city seem to have no particular problems, but those using a portal such as the one in Undercity or in the Pandaria Shrine, appear to be having issues. On attempting to confirm this, the portal from Undercity was used.

I monitored my frame rate across Orgrimmar, onto the Zeppelin, over to Undercity from Brill and out of the portal room in Silvermoon to the scene you see in front of you. You can see the results of this to the right-hand side, the 31 FPS is when I first arrived in Silvermoon, dropping to 10 when I stepped outside the portal room itself, then to four, and then stabilizing at 2FPS, where it remained for 15 minutes until I was unceremoniously disconnected. A second attempt with no addons revealed the same results, though marginally higher frame rates.

Silvermoon is very graphically intensive, and I'd turned my graphics down from their usual Ultra to Good in anticipation of issues like the ones experienced. On logging back in after my disconnect, I had a framerate of zero even with lower graphics settings, so dropped the quality to Low, which gave me a framerate of 6.

UPDATE: Bashiok has clarified to us that this addon was running off of inaccurate information and did not work properly. More importanly, the popup's lack of progress information was intentional. More info here.

We've been getting reports that some people are not able to see how many bosses have been cleared when their Looking For Raid queue finally pops. There have been some posts popping up on the official forums, but there has not been an official blue post yet as to whether this is indeed a bug, or an intended change with the recent 5.1 patch. At this time, we believe that it is a bug as we've also been receiving reports that some players are able to see how many bosses are already killed on their queue pops.

With that in mind, some players have put their noses to the grindstone and written an addon to help you find out how many of those bosses are defeated if you find yourself with the queue pop bug. It's a quick fix, and it works quite well as a solution to a potentially annoying bug.

The addon outputs the boss total to your chat window instead of putting it back into your queue screen, which is actually a really nice work around. The addon is lightweight, and until we hear official word whether or not this is a bug or a feature, this seems to be the way to go. If you find yourself in burning need to know exactly how many bosses are waiting for you in your LFR queue, then you can download this addon over at Curse or WoWInterface. It's quick and easy to install, and requires zero configuration.

A special thanks to Stoppableforce for whipping up this addon quickly for everyone to use.

---

Mists of Pandaria is here! The level cap has been raised to 90, many players have returned to Azeroth, and pet battles are taking the world by storm. Keep an eye out for all of the latest news, and check out our comprehensive guide to Mists of Pandaria for everything you'll ever need to know.

---

If you're in the Mists of Pandaria beta, chances are good that you've encountered a few bugs by now. As a beta tester, it's not just your job to sit there and play through the game. You're also expected to report the bugs you happen upon in your travels through Pandaria. Blizzard has provided beta forums for feedback and bug reporting, so you've got a place to jot those bugs down. Once you've found and identified a bug, you should write up a brief report so Blizzard knows that there's a problem and can fix the problem before release.

Before you scamper off to the beta forums, however, there's a proper way to write these bug reports so that Blizzard knows what you're talking about and can take appropriate action. If you write a bug report incorrectly, you're not helping matters any -- and in some cases, you can even confuse the situation and make it worse. So how do you write a good bug report on the beta forums?

Have you made it into the Mists of Pandaria beta yet? Being a beta tester isn't about simply playing through a free sample of the game. If you're expecting a completed product when you log in, you're in for a surprise. What you are playing is a not-quite-finished version of the game, and it's highly likely you'll run into your fair share of bugs as you're wandering Pandaria's gorgeous hills and valleys. As a beta tester, it's your job to report those bugs you find in game, so that they can be fixed before the game goes live.

However, not every error out there deserves a report. Things like NPCs that are marked with a PC or NYI tag are things the developers already know about -- they're just placeholder models. Music isn't yet implemented into Pandaria yet either, but the developers know about that, too. So what makes a bug a bug, and what kinds of bugs should you report?

The newly revamped Darkmoon Faire returned yesterday for its monthly one-week engagement in Azeroth, but it wasn't a flawless return. Players working on the Darkmoon Defender, Darkmoon Dungeoneer, or Darkmoon Despoiler achievements may have noticed the tally of items turned in has been reset, with few exceptions. Players have also been reporting that these monthly quest turn-ins, which should be resetting, are not, leaving players with dungeon-acquired items that cannot be turned in for another set of tickets. If this has happened to you, don't panic -- Community Manager Kaivax has chimed in on the issue, and although no fix has been put into place yet, Blizzard is aware of the issue and working on a fix.

Kaivax

We are aware of issues affecting the Darkmoon Faire, which began again today, particularly regarding monthly quests and some related achievements.

Our teams are investigating the issue and would like to assure you that we are working hard to solve the issue.

We apologize for any inconvenience this may be causing.

source

Hotfixes for patch 4.2 have been released at a steady pace ever since the patch's release. Though patch 4.2's launch was impressively smooth, it wasn't without its hiccups. Luckily. Blizzard is pretty quick to get errors addressed and fixed as soon as possible, which is why these hotfixes keep coming out at a regular rate.

From tweaks to various class mechanics to the encounters in the Firelands raid, the amount of information regarding these hotfixes has been pretty substantial. Rather than leave you to sift through weeks worth of hotfix posts, we've collected all hotfix information for patch 4.2 in one handy spot. You want a recap of everything that's been adjusted and changed in regards to the latest patch? Follow after the break for a complete compilation of patch 4.2 hotfixes.