Skip to Content

WoW Insider has the latest on the Mists of Pandaria!

Filed under: Bugs

Rygarius clarifies Draenor's Secret Power hotfix

One of the recent hotfixes was to the Draenor's Secret Power quest. Before the hotfix, players were able to complete the three heroic dungeons and turn in the quest items for the next stage in the legendary quest chain, getting an ilevel 680 ring in the process, because they were not required to complete the 4986 Apexis Crystals requirement first.
Rygarius - Sooo you're letting them keep the rings?
Here to provide additional clarification on the hotfix note that went out yesterday, November 17.

Quests
Draenor's Secret Power: Completion of this quest is now required before being able to move onto the next step of the Legendary quest chain. For characters that skipped this quest, completion of this quest has also been made into a requirement before being eligible for the next upgrade.

This means players that skipped the quest will still have to complete Draenor's Secret Power before being eligible for the next upgrade. That last part wasn't included until now cause I was tunnel visioning on hotfixes and glossed over the supplemental email for the change. Hope this clears any confusion up.


If you have the ring, you'll be keeping it, but people who haven't yet upgraded will have to wait until they have the apexis crystals. Since raids won't be open until December, this is (to my eyes, anyway) a minor advantage for a few players. Going any further in the quest still costs that 4986 Apexis Crystals.


Filed under: Analysis / Opinion, Bugs, Blizzard, Warlords of Draenor

Broken garrisons and other issues on launch day

Bugged garrison

UPDATE: Bashiok posted that Blizzard will be "restarting some Garrison services" to address access and progression issues. He also says that Blizzard has implemented "dozens of hotfixes" over the last few hours.

UPDATE 2: For those experiencing long queue times, this is working as intended. Bashiok has said that Blizzard is reducing realm population caps in order to address latency. Rygarius has posted a list of hotfixes for November 13.

UPDATE 3: Lore tweeted about the issues: "So obviously launch not going as smoothly as we wanted. Will be many discussions in the near future about what could have been done better. Right now, however, we're focusing 100% on just fixing issues so everyone can play. Can worry about what went wrong later."

UPDATE 4: Lore says fixes have been implemented for garrisons, but he recommends walking to your garrison instead of flying there or using a hearthstone.

Despite a mostly smooth launch so far, some realms are now experiencing major problems as more and more players crowd the servers. Garrisons on Argent Dawn, Cenarion Circle, Khadgar, and other realms are currently bugged and not always phasing properly. Twitter user @ikolism posted the image above of players in an unphased Horde garrison. Normally you're only supposed to see the players you've invited to your version of the fortress...

Players can become stuck inside their garrisons, or stuck outside and unable to "zone in." If the entire garrison server crashes when players are inside it, they are reportedly sent back to where their hearthstones are set. For many that means an unexpected trip back to Orgrimmar, Stormwind, or Pandaria.

High population realms, particularly in the EU, have experienced world server lag and crashes.

CM Lore tweeted an update on the problems, but did not provide an ETA:
Earlier, rolling restarts were required to fix Establish Your Garrison for Horde players. A number of hotfixes have already gone out today to fix problems with These Colors Don't Run in Frostfire Ridge and Drudgeboat Salvage quest objects in Shadowmoon Valley. Lore also says a hotfix is "in testing" for Gormaul Tower. Another for Gorgrond NPCs that are reluctant to spawn is "being developed."

Filed under: Bugs, Hotfixes, Warlords of Draenor

Patch 6.0.3 Hotfixes for October 30th

So here we are, friends, the complete list of hotfixes for Patch 6.0.3, as of October 30th. What's happening, you may ask? Well, for starters, all the class tuning hotfixes we mentioned yesterday are in. But of course there's more:
  • Resolved an issue where durations for periodic effects were not always being extended for the full amount when refreshed by another ability.
  • Downfall Wing 4: Resolved an issue where Gnomish Gyrocopters may not be destroying Thresher Turrets for Alliance players.
  • Razorfen Kraul: Groyat, the Blind Hunter's Drain Life ability should no longer damage or heal for an excessive amount.
  • Isle of Conquest: Huge Seaforium Bombs no longer have a level requirement to interact with them.
For the complete list of hotfixes, the official site has the skinny.

Filed under: Analysis / Opinion, Bugs, Blizzard, Hotfixes, Warlords of Draenor

Maintenance extended until 4pm Pacific (updated)

If you're sitting around waiting for the servers to come up, you have a bit longer to wait - the roll out of patch 6.0.3 is continuing apace, and the servers will be down for a while longer.

This is apparently due to last minute issues with the new patch, so it may or may not be the final say in terms of delays. Don't get too overexcited either way - things could end up resolved earlier than expected, or they could be delayed past 1pm Pacific. Just know that currently the call is that maintenance has been extended past the 11am PST point.

Updated - Server Maintenance has been extended until 4pm PST.

Filed under: Events, Bugs, Blizzard, News items

Patch 6.0.3 notes for October 28th

So tomorrow we're getting patch 6.0.3, which hotfixes a lot of issues thus far in patch 6.0.2 and brings the game more in line with what's running on the beta servers. So what issues needed fixing, you ask? Well, there's a host of fixes, so why not let them speak for themselves?
  • In the hilarious words of the patch notes, "Thrall received a reminder that he is currently still on Azeroth."
  • The glitch that was making Undead players' jaws vanish in certain helmets has been fixed.
  • Shamans can rejoice that Flame Shock, Chain Lightning, Lightning Bolt, Frost Shock and Lava Burst have received a discount and now cost 50% less mana to cast.
  • You now can't complete the quest for Warforged Seals if you already have the maximum amount (20) of Warforged Seals.
For the complete list of hotfixes, click the link below! And remember, you are currently still on Azeroth.

Read more →

Filed under: Analysis / Opinion, Bugs, Blizzard, News items, Warlords of Draenor

Is BlizzCon bad for World of Warcraft?

Okay, I'm sure with a headline like "Is BlizzCon bad for World of Warcraft?" you're already thinking this is it. Rossi has finally snapped. But hear me out for a second. We've had BlizzCons since 2005, before The Burning Crusade was even released. While they haven't happened every year (there was no BlizzCon 2006 and no BlizzCon 2012) it's been fairly regular since its introduction. Last year, Warlords of Draenor was previewed at BlizzCon 2013 - for many of us it's the source of pretty much every opinion we have on the expansion.

That, in fact, is exactly what got me thinking that it's possible that BlizzCon itself is bad for the game, for the game community at large, and for the future of the franchise. BlizzCon, by its very nature, is a hype machine. It's where we learn details about the expansion - its name, its features, its setting and goals - before they are even close to being ready for players. People play demos. Developers give talks about the games. In many ways it's very exciting. I've never been myself, but most of my coworkers and a lot of my in-game friends have. So my argument isn't that BlizzCon itself is bad.

But looking over the past year or so, in terms of Warlords of Draenor and player interaction with it, I start to wonder if having the big reveal at the convention does more harm than good, overall. Expectations are set at the convention - looking at the recent player reaction to the news that Karabor and Bladespire wouldn't be capital cities in Draenor, the issue can in part be traced back to the fact that we were told they would be at BlizzCon. Players (like myself) had months to get excited about the idea of Karabor as a capital city. Then, suddenly, we were told (almost as an afterthought) that no, the capitals were moved to Ashran.

Read more →

Filed under: Analysis / Opinion, Bugs, Blizzard, The Burning Crusade, BlizzCon, Wrath of the Lich King, Warlords of Draenor

Why Testing Matters 2: The Beta Tank Bug

I did a post a while back on why beta testing matters. The point was, no matter how we might wish that the game could be finished and rushed out, you have to test this stuff in a controlled environment first. And this particular bug is a perfect example of why that is. Because on the beta servers, tank specs were unkillable gods.

We discovered a teeny tiny little issue with the Battle Fatigue debuff. Turns out, it was set to increase tank damage taken by -25%. Yes, that's an increase of negative 25%... which means that Battle Fatigue was actually reducing the damage tank-specced characters were taking.

This should now be fixed on Beta servers, which should make quite a difference. Let us know how things feel now.

That kind of error is exactly why the beta process is necessary and important, but moreover it's why it's kind of awesome - you see, stuff like this is terrible for game balance, but it's also astonishingly fun to discover and experience a few times. Yes, as a tester you should absolutely report it as soon as possible. But in order to report it reliably (it's hard to know for sure what's actually happening, after all, your combat log doesn't report that you're taking less damage) you need to repeat it. And that's really pretty awesome.

It's better -- far better, in fact -- that we get this stuff found out before it goes live. Even though I'm sure all of us with a tank spec kind of secretly wish it didn't. The feeling of being overpowered wouldn't keep us from the crushing disappointment when they found and fixed it.


Filed under: Analysis / Opinion, Bugs, Warlords of Draenor

Diablo III - Hardcore Crusaders absolutely should not use Shattering Throw or they will die

This isn't me being all hyperbolic.

This is actually what will happen to you if you use the combination Blessed Shield and Shattering Throw. Your character will die, and for hardcore players, that means your character will be dead forever.
Grimiku - PSA: Avoid Blessed Shield - Shattering Throw
Hello, Crusaders

I wanted to help spread the word that there is currently a very ugly bug with Blessed Shield - Shattering Throw that will result in your Crusader instantly dying if you use this skill.

Hardcore players should avoid using this skill for now!

We're working on a hotfix for this issue and we'll update the Patch 2.0.4 Hotfix thread once that happens. Thank you all for your patience and understanding while we work on fixing this as soon as possible!


As my Crusader has both of these and likely would have blown himself up (a mere annoyance for me, but the end of that character if you play on Hardcore) I thought you all should know.

Filed under: Bugs, Blizzard, Diablo 3

Potential new WoW feature caught on video

We're hedging pretty hard on this one, ladies and gentlemen, partly because I'm trying to rein in my excitement that this could actually be a real video of a new feature. Somehow, Aipok managed to leave what looks like an instance of Temple of the Jade Serpent and zone into Stratholme, taking the option to "Teleport to Instance" while still in an instance himself. Not that weird, right? Well this is when things start getting a bit odd.

Because this has been doing the rounds, I was ready for what was coming. Aipok's health suddenly drops to 11.1k. He wades into the skeletons, as you would, with the confidence of a level 90 in a level 40-ish dungeon, and he dies. Only then, looking through his combat log, does he realize that something is awry. On ressing, his health is even lower, at 5.9k. He opens up his character pane, and all his gear has been downscaled to ilvl 43. His character attributes appear to have been downscaled, too.

Now, this has Aipok in a strange position. Has he just happened upon a very specific and weird bug? Is this an accidental hop into an unrevealed new feature for 6.0? Could players entering old content be downscaled to match it? Or, could this all be an elaborate hoax? Personally, I want to believe, so I'm going to choose to. What's more, Blizzard devs have talked before about this tech being completed. As long as this was optional, and perhaps even if it wasn't, I'd love this. It'd refresh old content and make it a challenge again. And, if you could earn upscaled XP while downscaled, a fun way to reuse old content to level.

But again, remember, this is not an official announcement, or an endorsement, or anything from Blizzard. It's one video of one weird dungeon. It could be a hoax, it could be a bug, it could be nothing at all. I'm excited, though. Are you? And what could it reward?

Filed under: Bugs, News items, BlizzCon

Watcher explains Heroic Norushen changes

This week, we saw a bit of discussion on Heroic Norushen, and the means by which guilds were defeating him. This led to the decision to make some adjustments to the fight this week. As you might expect, those guilds that had already defeated the boss using the 'brute force' strategy (basically, paring down the healers brought to the fight to a bare minimum and overwhelming the boss with DPS) weren't happy at the prospect of having to go back in next week and relearn the fight, since their approach was made vastly more difficult by the changes.

Now we have Ion "Watcher" Hazzikostas' explanation of the changes and why they were made, and it's a pretty interesting read if you're into encounter design and its implementation. Just some selected bits of information from the post:
  • Originally on the PTR Heroic Norushen had a 'draw' mechanic that would have prevented the brute-force method, but it was removed because it had bad effects once gear improved, forcing groups to throttle their DPS.
  • The intent isn't to increase encounter difficulty - the problem isn't that the fight is too easy, it's that people are just skipping the mechanics entirely.
  • Going back to reference the Encounter Design Dev Watercooler, Watcher mentions that "a major factor when it comes to deciding whether to make changes to address an unintended strategy is whether the approach actually involves interesting gameplay." - I think it's fair to say that just throwing DPS at it so you can avoid the mechanics isn't all that interesting.
  • The difference between the changes to Thok this week and Norushen in the upcoming reset are profoundly the difference between a bugfix (Thok was always intended to have Acceleration on all difficulties save Raid Finder, it was simply accidentally turned off on all other difficulties as well as Raid Finder) and a decision to change an encounter to close off an approach that was never intended. That's why Thok was hotfixed immediately, but Norushen is being changed with the server reset so it affects all guilds equally.
For more, you can read Watcher's post here on the forums, and we'll reproduce it in full behind the cut as well.

Read more →

Filed under: Analysis / Opinion, Bugs, Blizzard, News items, Raiding, Mists of Pandaria

Conquest cap hotfixed, vendors have returned

Conquest cap hotfixed, vendors will return soon
WoW Insider posted a couple of days back about a bug that caused the removal of the Conquest Vendors, leaving nothing but an empty space and a hole in our hearts where Armsmaster Holinka used to be. But happy news is on the horizon, as Blizzard Community Manager Rygarius reports:
Rygarius
A fix was made to restore the Conquest cap back to the proper level of 2200. A very small number of players were able to purchase more gear than intended, and we will be addressing those on a case-by-case basis.

We're currently working on implementing a hotfix to bring the Conquest vendors back as soon as possible.

And indeed, just an hour after Rygarius posted this, the vendors returned! Blizzard are redefining "Blizzard Soon".

The issue was that, for some reason probably related to the conquest catch-up cap implemented last season, certain players had the full catch-up cap of 28,000 conquest points, instead of the correct cap of 2200. It's hard to be sure exactly what caused some players to have it while some didn't, but from the above those who abused the bug, intentionally or otherwise, are being relieved of their ill-gotten gains. A level playing field will be restored, and hopefully our conquest vendors will return to Pandaria before the reset takes place.

Filed under: Bugs, PvP

Disconnects and latency issues and Patch 5.3

No one likes high latency, least of all someone playing an MMO that can demand reaction time the way World of Warcraft can, especially in raids. But even out in the world, latency can be a killer. So when people started reporting issues with connections to World of Warcraft soon after patch 5.3 launched, it got a lot of players noticing. In a six page forum thread there's been a lot of lively discussion of what's going on - whether it's on Blizzard's end, or somewhere between the computers of the affected players and the Blizzard servers. If you remember the Lagpocalypse post, you know how complicated these issues can get.

MVP forum poster Lissanna posted an interesting walkthrough of her own attempts to find the culprit today, and explained why despite some forum poster dissatisfaction that it is indeed helpful to run a traceroute and pathping and post the results to the tech support forums, since it gives Blizzard an idea of who to talk to about these issues. If they don't know who's being affected, where those people are, and more importantly where the issue is physically located there's not much they can do to help.

So if you're having the same problem, giving Blizzard as much information as possible is definitely helpful in terms of getting this sorted out. I've seen people in my raids disconnect on every single boss so far while I haven't had the issue at all myself, suggesting the problem isn't on Blizzard's end but is out there somewhere in the path the data takes between Blizzard and the players. Hopefully it can be solved soon.

Filed under: Analysis / Opinion, Bugs, Blizzard, News items, Mists of Pandaria

A temporary fix to the gold sellers' spam invitations

A temporary fix to the gold sellers' spam invitations
WoW Insider has received notifications to our tip line, as well as noted a particular problem coming up on the forums. The gold seller spam invitations in our calendars appear to have returned. They were gone, as a forum thread notes, for some time, almost 2 years, and all of a sudden they have returned.

There seems to have been a breakthrough among the gold sellers, allowing their bots to once again spam players' calendars with events advertizing their ill-gotten wares. We're not exactly sure just how they're doing it, but MVP Shammoz and Community Manager Eldtyara have been hard at work notifying the devs of the issue, as well as digging up a couple of solutions.

The first solution, as confirmed by Shammoz, is, rather than right-clicking the event and picking Ignore from the drop down menu, typing /ignore into chat. This appears to remove all the invitations from your calendar, rather than just the one you right-clicked on.

The other option is to run a script, which several players have asserted has solved the problem, as can be seen in the forum thread which shares it. Running a script simply involves pasting it into your chat and hitting enter, and the script itself is below:

Read more →

Filed under: Bugs

Short-lived bug gives windwalker monks huge damage numbers

Windwalker monks' crazy night of huge DPS
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.

Shortlived bug gives windwalker monks huge damage numbersThe 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.


Filed under: Bugs, News items

Powershot repaired for patch 5.2

Powershot repaired for patch 52
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.


Hunters, rejoice! A fix is in, at least preliminarily. Do head over to the PTR and check it out when it's up with the next build.

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.

Filed under: Bugs

Around Azeroth

Around Azeroth

Featured Galleries

It came from the Blog: Occupy Orgrimmar
Midsummer Flamefest 2013
Running of the Orphans 2013
World of Warcraft Tattoos
HearthStone Sample Cards
HearthStone Concept Art
Yaks
It came from the Blog: Lunar Lunacy 2013
Art of Blizzard Gallery Opening

 

Categories

Joystiq

Massively

Engadget