There will be extended maintenance today, April 1st, on all the realms from 3:00 a.m. PDT until 11:00 a.m. PDT. Hopefully this will fix many of the issues appearing over the past week – and just give the servers some breathing room. There have been many bugs reported, some of which you can read about in the various hotfixes that have been pushed onto the servers in the past week.
Also, this downtime is not an April Fool's joke. It has been expected.
Be alert, hunters: Growl isn't casting first anymore, and it's making aggro touchy. Mania, that hunter maven and proprietor of Mania's Arcania, breaks the news. It's unclear (especially to me, since I don't have a hunter past level 26) if this is actually new or just a consequence of the new combat log system that rolled out in patch 2.4 but if it is new, it could be a nasty surprise for you hunters out soloing.
Mania goes over the list of reports, some arguing for better pet aggro, some worse, and specifically singles out boars as possibly suffering the most since growl scales with pet AP and the boar's charge ability adds AP to the pet's next attack. If that attack is growl, yay, more aggro! If that attack is not, boo, less aggro.
About a week and a half ago I reported on an experience I had in Mount Hyjal while fighting Azgalor. While the fight went fine and we did him in one try, I wasn't on Azgalor's threat list and thus did not get any loot. I wasn't on the threat table because I had to tank some spawned demons up and away from the rest of the raid. It was a rather nice conflict of game mechanics.
This all happened on Tuesday, March 18th. By Saturday, March 22nd, I had the two shiny pieces of loot that were coming to me: Glory of the Defender and Onslaught Handguards. Specialist Game Master Skelend had sent me the items, along with a form letter apologizing for the issues we experienced in game. I was quite happy to see this resolved. I was even more pleased that it was resolved quickly and did not take a few weeks; as many people, both those of you who left comments and friends of mine that I talked to, said it would.
So what are we doing to make sure this never happens again? Well for one thing, all the melee is hitting the boss now with a ranged weapon after the tank gets a couple hits in. That's pretty much all we can do to assure this problem doesn't pop up again for us. Despite a few enquires I've made, there is no word from Blizzard if they've fixed this. I suspect that one day it'll just be hotfixed without much fanfare.
All in all, not a terrible experience when something went wrong. Quick and quality support from Blizzard.
For those of you who do not frequent the forums, you might not know that since patch 2.4, there has been a Tauren outcry.
It seems that cows everywhere are logging in to find that their weapons are roughly 50% smaller than they were previously. Should you take your weapon out to get a better look at it, you'll get to watch it grow back to pre-patch size.
Unfortunately, this is not a bug. Hortus has confirmed that it was an intentional change because certain weapons would clip the ground while sheathed.
While the Tauren have been getting some support on the forums, some players seem unsure of why this is such a big issue. Let's take a deeper look into why players are upset, including the fact that cows will seemingly be the brunt of even more jokes. Not innocent jokes either; not like "steak! It's what's for dinner!"
Drysc is keeping a post up-to-date of all the latest hotfixes that are happening. Patch 2.4 went live without too much trouble this last Tuesday, yet there is a slow but steady stream of issues popping up in the game. Each morning for the next few days we'll let you know about all the hotfixes that have come out the previous day.
Yesterday's hotfixes include:
Increased Felbound Initiate respawn rate. These are the guys you need in the "Blood for Blood" quest.
You can no longer accept thequests given by Magistrix Seyla up in Hellfire Penisula without first compleating "The Missing Magistrix."
Thanks to rolling restarts last night, you will now see your server name correctly displayed in battlegrounds.
Of course, if something major comes up, expect to see it covered right away on WoW Insider. Enjoy your patch 2.4 fun!
There is a mechanic in game that we are all aware of, and one that exists for a good reason: when we attack a mob, we get the mob's loot. That's the mechanic. If you're solo grinding mobs out in Shadowmoon Valley for some Primal Fire, you want to be sure you're the only one that can get the loot. The same goes for groups – if you're grouping and killing Murmur in Shadow Labs, you want to be sure that everyone is going to get his pretty blues.
But what if the mechanics of the boss fight dictate that you won't hit the boss? In fact, what if successfully killing the boss means that you have to stand on the opposite end of the playing field the whole time? You don't hit the boss, you don't get the loot – but you've done everything right. In this, the game mechanic does not represent fair play, nor does it encourage success. In fact, the mechanics are a complete contradiction of each other.
I've recently encountered this problem, and it's a real pain. Read on after the break for what happened, and what can be done to solve it. It's rather long, but this is a serious problem that Blizzard needs to fix, and all the facts need to be laid out completely and in a way that is full of thruthiness.
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!).
Are you one of those folks who just absolutely can't live without the cute and cuddly non-combat pets? Well, this morning has turned up news of a surprising new non-combat pet, but we're not convinced that "cute" fits here. The pet is Mojo, the frog long claimed to be obtainable in Zul'Aman via the Amani Hex-sticks. While we're not entirely sure if it was intended or not, it would appear that Mojo is currently available by going to the small camp just outside and slightly to the south of Zul'Aman. I have tested this quest and was actually able to get Mojo on my level 70 Rogue as well as my level 27 Hunter, so one would think that it is likely attainable on most characters.
Of course, the down-side of this particular variant of Mojo is that he doesn't seem to be quite right. Well, that is to say, his texture map looks very low-res/unfinished compared to other frogs in game, and his in-game icon is a grey doll with a blue nimbus around him as opposed to being a frog. However, should you want a Mojo of your own, check out the how-to after the jump!
[UPDATED] - It would appear that this is no longer working and was, in fact, a bug that was hot-fixed today. Blizzard has not issued a statement as yet about whether or not the NPC-given Mojos will remain. If they do say one way or the other, we'll let you know.
This is the best bug I've heard about in the game yet so far-- Drysc has confirmed that there is a known bug in the Blade's Edge plateau area which will cause everyone, when someone starts up the Bombing Run quest, to stop eating and drinking and stand up. It's a respect thing, you know? Stand up for the cause!
No, it's just a really, really weird bug, and a fix is on the way in an upcoming patch (I'm a little surprised they don't aim to fix it earlier, but apparently all that will be lost is the food anyone sits down to eat at the wrong time in Blade's Edge). Once again, I am dumbfounded at trying to figure out just how Blizzard's code works-- seems like they have the absolute weirdest bugs happen to them sometimes.
A fairly lengthy thread on the official Bug Report forum today led to the discovery of a problem related to two Rogue skills. Cloak of Shadows and Vanish were both reported by players as simply not working. For whatever reason, rogues were unable to escape the attacks of their opponents in PvP when using these skills.
Reports of problems with Vanish often plague the forums. Most often these issues are caused by client/server latency, as Hortus reminds us, but this time they've identified a separate problem. While not disclosing the nature of the bug, Hortus has informed the rogues in the thread that their feedback has resulted in the discovery of a problem with these two skills and they're currently investigating the issue in hopes of finding a fix.
It's nice to see that players are able to help contribute to fixing the game. If you've had any problems with these skills recently, I'd suggest that you read over the thread and see if your experience adds anything to the discussion.
For a very long time now, druids have been bemoaning the "feral range bug," which makes it so that feral special attacks sometimes don't work, even though the regular auto attacks are fine. I've always thought this bug caused special attacks to have a shorter range than auto attacks (and I wasn't alone), but some videos demonstrate that the bug (as shown above, and also here) has to do more with positioning than the actual range between the druid and the target.
I play a feral druid, and I can't say that I've noticed this bug very much, but I tend to shy away from PvP situations where it would be likely to show up most -- mainly because I find feral druid PvP to be very difficult (though I keep trying now and then). Perhaps this bug is one of the reasons for that, but everything is just too fast-paced for me to see?
In any case, Vaneras on the European WoW forums responded to a poster in order to let us know that the developers are indeed aware of this "concern," and they ... well... that's it. They're just aware. Nobody knows if they'll actually fix it or not, though I would assume they will at some point.
In addition, Vaneras says the developers are aware of the some graphical imperfections in some druid feral forms, and they also "like the idea of new graphics and models for the Druid forms, however there are no plans for such in the immediate future." The key word here is "immediate," which implies that the not-so-distant future might be quite different! Is there hope for feral druid graphical updates in Wrath of the Lich King, perhaps?
[Update] I just got back from testing this in PvP, and sure enough I found my special abilities weren't landing, even though I was on top of my enemy. Click on the link below to see a video of this bug in a PvP situation.
A lot of surprises came with the awesome Patch 2.3. Shamans, in particular, have been getting a lot of unintended love. The recent three-hour server maintenance found a lot of Shamans on the WoW forums talking about getting free re-specs, after a bug in the recent patch gave some Shamans an additional Talent Point to spend in creatively undesirable ways. Reports have trickled in that some players' Shamans got their Talents wiped clean while others, such as WoW Insider's Mike Schramm, did not. The irony is that a lot of Shamans had already paid their hard-earned Gold to re-spec thanks to the buff-flavored goodness of 2.3 only to find that they had their Talent Points refunded a day later.
What about you guys who play Shamans? Did you get your Talent Points refunded? If yes, did you use the free re-spec to choose a new build or take the same Talents you've known and loved? Were you among the over-eager mobs who spent for a re-spec as soon as the servers came back on last Tuesday?
Weird things are afoot. According to this post over at the PvP forums, this 3v3 Arena Alliance team got a helping hand during one of their rated matches when they found themselves with a fourth member -- a Horde Paladin! Much to their surprise, and to the chagrin of the opposing team who happened to be Horde, the Paladin went on to heal the Alliance team on to an 18 point win. This is an interesting glitch on a couple of levels... it's interesting enough to have a fourth member on a 3v3 match, but this is one of the rare times that Horde and Alliance are even in the same party. It's even more interesting that the Horde Paladin got to heal his strange bedfellows. There's only one screenshot linked in the forums and the quality's not very good; but if it's an elaborate Photoshop hoax, it's a pretty thorough one.
Arenas pit same-faction members against each other, but having Alliance and Horde on the same team seems just ridiculous. What do you guys think? Have you ever seen a glitch like this? Have you ever found yourselves with an unexpected helping hand, particularly in Arenas? Since Arenas allow members of the same faction to duke it out, is it too much of a stretch to team up with sworn enemies?
It's the end of the day (or nearly there) and, if you've logged on at all, you've patched WoW up to the latest version. Oftentimes, patch days are fraught with server instability and all sorts of other issues in game. On top of those problems, UI mods get thrown out of whack and usually must be updated in order to avoid screens filled with annoying error messages.
Personally, this patch day was one of the smoothest I can recall in recent memory. Once the servers came back up, I was able to log on right away with no queue and no apparent latency. As the afternoon wore on into evening, there were a few rough patches of lag, but they smoothed out after a little while, never to return. My most important mods were already updated and I can live without the rest for a couple of days. I purposefully try to avoid a reliance on UI mods, which is always helpful on patch days, so I'm not sure that my experience was shared by many other WoW players. Even so, my guildmates who rely on mods more than I do also seemed pretty happy with the transition to the new patch, so hopefully things went well for the majority of WoW fans. How did the patch treat you today? Did you bother logging on at all? If you did, have you had a good experience thus far?
Slorkuz, Mr. Blue Poster over on the European WoW forums, gave us a few hotfixes that have been pushed through this week:
There will be extended maintenance today, April 1st, on all the realms from 3:00 a.m. PDT until 11:00 a.m. PDT. Hopefully this will fix many of the issues appearing over the past week – and just give the servers some breathing room. There have been many bugs reported, some of which you can read about in the various hotfixes that have been pushed onto the servers in the past week.
About a week and a half ago I reported on an experience I had in Mount Hyjal while fighting Azgalor. While the fight went fine and we did him in one try, I wasn't on Azgalor's threat list and thus did not get any loot. I wasn't on the threat table because I had to tank some spawned demons up and away from the rest of the raid. It was a rather nice conflict of game mechanics.
There is a mechanic in game that we are all aware of, and one that exists for a good reason: when we attack a mob, we get the mob's loot. That's the mechanic. If you're solo grinding mobs out in Shadowmoon Valley for some Primal Fire, you want to be sure you're the only one that can get the loot. The same goes for groups – if you're grouping and killing Murmur in Shadow Labs, you want to be sure that everyone is going to get his pretty blues.
This is the best bug I've heard about in the game yet so far-- Drysc has confirmed that there is a known bug in the Blade's Edge plateau area which will cause everyone, when someone starts up the Bombing Run quest, to stop eating and drinking and stand up. It's a respect thing, you know? Stand up for the cause!
A fairly lengthy thread on the official Bug Report forum today led to the discovery of a problem related to two Rogue skills. Cloak of Shadows and Vanish were both reported by players as simply not working. For whatever reason, rogues were unable to escape the attacks of their opponents in PvP when using these skills.
A lot of surprises came with the awesome Patch 2.3. Shamans, in particular, have been getting a lot of unintended love. The recent three-hour server maintenance found a lot of Shamans on the WoW forums talking about getting free re-specs, after a bug in the recent patch gave some Shamans an additional Talent Point to spend in creatively undesirable ways. Reports have trickled in that some players' Shamans got their Talents wiped clean while others, such as WoW Insider's Mike Schramm, did not. The irony is that a lot of Shamans had already paid their hard-earned Gold to re-spec thanks to the buff-flavored goodness of 2.3 only to find that they had their Talent Points refunded a day later.
Weird things are afoot. According to this post over at the PvP forums, this 3v3 Arena Alliance team got a helping hand during one of their rated matches when they found themselves with a fourth member -- a Horde Paladin! Much to their surprise, and to the chagrin of the opposing team who happened to be Horde, the Paladin went on to heal the Alliance team on to an 18 point win. This is an interesting glitch on a couple of levels... it's interesting enough to have a fourth member on a 3v3 match, but this is one of the rare times that Horde and Alliance are even in the same party. It's even more interesting that the Horde Paladin got to heal his strange bedfellows. There's only one screenshot linked in the forums and the quality's not very good; but if it's an elaborate Photoshop hoax, it's a pretty thorough one. 
It's the end of the day (or nearly there) and, if you've logged on at all, you've patched WoW up to the latest version. Oftentimes, patch days are fraught with server instability and all sorts of other issues in game. On top of those problems, UI mods get thrown out of whack and usually must be updated in order to avoid screens filled with annoying error messages.
Subscribe
