bugged
Latest
Mount achievement hotfix very soon
There have been several reports on the forums of a problem with mount achievements, such as Mountain o'Mounts and the newly added We're Going to Need More Saddles. The problem is that they're not doing what every mount collector wants them to do, which is, of course, awarding yet another mount! Naturally there have been quite a few complaints about this, no mount collector likes to be cheated out of a dragonhawk, nor out of an awesome jade kite, or even an albino drake. Blizzard's Community Management team have been swift in reassuring mount collectors that a hotfix is coming, that it's a known issue, and that there should be something in place by Tuesday (if not before). So if you are getting mount achievements, but no rewards, hold on to your hats. They should hopefully mysteriously materialize in your presumably TARDIS-like mount carrying facility before long. As Vrakthis said, it should just happen when you log in, so keep an eye out and you'll be rocking a new ride before you know it. The full blue post after the break.
Loot Reaver gets his revenge
Void Reaver, after 2.4, is apparently, "wrecking fools," according to Korin on the Silver Hand. We all called him Loot Reaver before 2.4 -- if your guild could finish off Karazhan, and survive VR's trash, he was basically a pushover. But a whole combination of factors, including addon problems (with DeadlyBossMods and VoidReaverAlarm) that killed the addons that made it cake, as well as a few bugs and other problems with the fight after the patch, means Loot Reaver is getting his revenge. He's back to being a real challenge in Tempest Keep.The hardest part of the encounter is avoiding these orbs he shoots out at random spots where a guild member is standing. When he shoots one out, everyone in the guild has to move away from that spot and each other, since getting hit with one is instant death. Those addons were meant to tell you when an orb had been fired, as well as let you keep an eye on the proximity of where it was hitting (so you could easily dodge it). But without the addons, people are back to judging where the orbs might land, and guilds that haven't practiced the fight much aren't that great at judging. Not to mention that there are some bugs, apparently -- some of the orbs are invisible, and others may even be moving through walls and underground.The fight is still doable, but apparently Blizzard wasn't happy with how easy it was to waltz in there with some addons and collect your loot. Whether it's bugs or addon changes, Void Reaver is currently back to "wrecking fools."
Onyxia: Bugged at 70
I don't get it. I'm 70, have lots of nice purples, know the game well enough, and have even done Onyxia dozens upon dozens upon dozens of times back in the pre-BC days. But why then does she inevitably present a problem for me and my friends?It's probably because she is bugged. And not just bugged, REALLY bugged.Two groups have now gone in and tried to defeat her. Each time the first attempt was a failure as people relearned not to stand too close to each other (Forsythe run to the center!), run to the side when the rains fire down (<-- 2N, 2N - 1 -->), and all those other small tidbits that make the fight what it is. However when it reached the second attempt, she started acting strange. First, she wouldn't target anyone or let anyone tank her – she just walked around her lair and jerked around a bit. We could still damage her, but that was it. And really it was only the ranged and my crossbow that were able to do any damage (more dots!).
New Flametongue bugged
As predicted, Enhancement Shamans got some nice buffs yesterday, including the addition of a Mortal Strike-like effect of reduced healing to the Flametongue weapon.But the weapon hasn't quite had the desired effect yet on the PTR. In fact, as World of Raids has posted, it actually does exactly the opposite. As you can see above, Flametongue is actually adding to heals on the target of the attack, not halving them as its now meant to. No doubt this will be fixed before long, but a note to whoever's working on the Shaman class on the PTR: you should have used that minus sign in the code there, not the plus one.
Hellgate: London subscriptions temporarily offline
As a whole, it's probably fair to say that MMO players are a tolerant lot. We're generally willing to put up with bugs, unbalanced players classes, and sparse content when we jump into an MMO for the first time. Usually the excitement of being part of a new world overrides the feeling that we're paying money for an unfinished product. What is likely to irk us however, is when we purchase a game, install it, and go to put in our subscription information and ... oops, the subscription system is bugged! Sadly, such is the case with Hellgate: London, with Flagship Studios announcing, " Subscriptions are temporarily unavailable due to technical issues."Now, as we understand it, that doesn't mean that players can't play the game, it just means that nobody yet has access to the subscriber content yet, which is supposed to be such a big feature for hardcore fans. Though I guess if you really look at what the subscriber content is (bells and whistles like new items, character classes, themed events, and the like), it's supposed to be the icing to the rest of the game's cake, and it's highly unlikely that players have already dug through all that cake in the span of a single day. Still, we'll keep you posted on the status of this subscriber bug. Hopefully it doesn't scuttle the launch completely.
Kael'thas bugged, hotfix not incoming
Daelo is saying over on the forums that the Kael'thas event is bugged. After a player reported that the shield (one of the magical weapons that you first have to defeat and then can fight Kael'thas with) has tons more health than expected, Daelo confirmed that if Kael'thas resurrects his advisors while weapons are "alive" their health will be increased, making the fight much harder and throwing most guilds off of their pacing.So if you're headed to Kael'thas this week, beware. Unfortunately, Blizzard says they can't hotfix the issue, which means it'll have to be fixed in a content patch. Fortunately, however, 2.2.2 is due this week, so if Blizzard can sneak it in yet on that one, raiders will be able to take Kael on as of Tuesday. If 2.2.2 is already too far along in the process for the code to be added, however, Blizzard will either have to create a patch just for this fix (2.2.3), or wait until 2.3 releases (which could be a matter of weeks, severly hampering guild progression past Kael).We'll have to wait and see what they do. This is a confirmed bug, so hopefully we'll see a fix for it with 2.2.2, hopefully on Tuesday.
Guards bugged in Silvermoon City
As a sidenote to the Valentine's Day guide from earlier: Don't even bother to try the Love quests in the new cities. As Memory from Scilla notes, the guards there are completely bugged-- in Silvermoon, guards talk about Stormwind (I even, as a Blood Elf, had one try to speak Dwarven to me).Now, Drysc says it's a known problem that has to do with the event itself, so if the problem isn't fixed soon, it'll go away for sure by Thursday, since that's when the Love event ends. And there's no real point to tooling around looking for love in the expansion cities anyway-- Kwee Q. Peddlefeet isn't there at all (because not all players, I suppose, have the expansion, and that would mess up the popularity contest, since all the rewards are city specific). So this isn't exactly the end of the world, even though when you get Heartbroken, it may seem like it.But for the moment, good luck trying to find your way around an expansion city you don't know. I was trying to find the Mage trainer in Silvermoon, and had to just give up and run back to the newbie area to train my new spells.
