Quite a few raiders, including some of our own here at WoW Insider, noticed one more big change to a raid boss that that came in with patch 2.4.3: Anetheron, the second boss of Mount Hyjal, was not dropping Towering Infernals on random players as usual. This made the battle pretty trivial for most raids by making it more or less a run of the mill tank and spank.

Unfortunately -- or fortunately, depending on how challenging you like your raids -- this was not an actual intended change. Vaneras and Bornakk are both reporting that Anetheron has been hotfixed and should start dropping infernals again. Sorry guys, no more free loot. Well, no more freer loot, at least.

While surfing the forums this morning, I came across a little gem of a thread protesting against Blizzard for the following:

1. Breaking "our" addons and mods.
2. Incorporating features from popular addons into the default User Interface, and thus breaking addons and mods. There's also a sentiment that Blizzard is "stealing" these ideas rather than being innovators.
   
3. Fixing "their" bugs which in turn breaks "our" addons and mods. The suggestion is that they don't care, or could take steps to prevent this.
   

As you can imagine, all sorts of responses cropped up, including the usual people who get into arguments with other posters, players in agreement, joking and sarcastic responses, and of course, an awesome string of blue responses.

Brad Justice (let me say that again, Brad Justice!) sent us a valuable tip about Titan Panel, and it's easily confirmed by a casual look over at the official forums. Let me explain. No, there is too much -- let me sum up.

If you use Titan Panel, you may see an unexplainable GM ticket open in the upper right corner of your screen. You may open that empty ticket, and then Abandon it. Your attempt will fail. But don't worry -- it's not your fault. It's Titan Panel. That ticket will linger there like some kind of horrific nightmare. But there's hope.

You can either simply disable the AddOn until they get the problem sorted out or attempt a "full UI reset." (A full UI reset is the process by which you basically delete the WTF folder, Cache, and Interface folders and more or less start all over again.) I personally went for the slightly less-intense "disable" option.

Anyway, good luck fixing it -- we just wanted to let you know this is what's up, since Titan Panel's pretty popular.

Edit: With a ninja-like quickness, Titan Panel has released an update which should help clear this up.

My friends and I discovered a nice little "bug" the other day. We were sitting around Ironforge with nothing to do other than to give a friendly ribbing to our Shadow Priest friend over that fact that she didn't have her Amani War Bear yet. We had our Mojo's out hopping around the feet of our Bears, trying not to get squished. We found out that if we blew them a kiss, we turned into a frog and our mounts grew quite a bit.

Obviously this is some kind of flaw in the model coding that allows this, but it's a fun enough and harmless enough bug that I can't stop myself from doing it every chance I get. More so, drink some Winterfall Firewater and pop Heroism for a real big frog on a bear mount.

This is definitely hilarious enough that I suggest everyone goes out and tries it at least once. Just leave my Mojo alone. He's spoken for.

When you decide to roleplay, a whole new world of imagination opens up to you -- soon you realize that all the World of Warcraft is a stage, and all the orcs and humans merely players.

Blizzard definitely cares about roleplayers. They listen to us and there's a special place for us in their hearts -- which is natural, because in many ways, their whole world has its own story and background which means a lot to them, and while all players get to see that story unfolding through their activities in the game, roleplayers are the ones who participate in that story by making their own stories within it.

The problem is that Blizzard and its roleplayers are on pretty different wavelengths when it comes to what roleplayers want to receive and what Blizzard wants to provide. Blizzard wants to give us more neat toys and perfect places to enjoy, with lots of lore and story behind them -- and while this is all very interesting and everyone enjoys it, most roleplayers are wishing they had more sandbox-like tools, spaces and items they can easily bend or shape in their own ways, to use for their own purposes.

Blizzard may care, but do they really understand? Read on for insights Blizzard may be missing.

Servers are coming back up, but it seems there's a bit of oddity about the end of season awards from Season 3. We've received reports that folks who should not have retained previous titles (Challenger, Rival, Gladiator, etc.) still have the honorary available. In theory, these titles were supposed to reset, and if you didn't re-earn the title in Season 3, you'd lose what you had from Season 2. That seems not to have happened.

We don't know if this is a bug or a surprise gift from Blizzard, but it's probably a safe bet that it's a bug they'll be squishing. It seems cruel to the hopefuls who may think they have a title, only to lose it if this gets corrected. But, we'll see what Blizzard does. At least Season 4 has started, and everyone will have the opportunity to try again.

Edit: While we realize that, per posting from Eyonix, new titles wouldn't be granted until next week, it had previously seemed that the title stripping would still happen at the end of Season 3.

Like Bigfoot, it's so elusive that photographs are rare, but some WoW players have caught a glimpse of what may be an upcoming PvP reward from Wrath. Or maybe it's just a bug. Or -- and I have a nickel bet on this one -- it's a nice little prank Blizzard's playing on us in return for our snooping around for information on the expansion. Whatever it is, though, it has left at least one footprint. We've gotten a few tips that upon inspecting a player's Tabard of Summer Flames, the Horde side reward from the Shards of Ahune quest, the tabard's tooltip describes a very different item called Tabard of the Victor. Even though the tabard's design matched the Midsummer quest reward, the description was quite different.

First of all, the Tabard of the Victor requires Level 80, which was our first clue that it was probably not meant for pre-Wrath eyes. The tabard binds on pick-up, provides 250 Armor, +20 Stamina, +10 to All Resistances. Upon equipping it, your resilience rating improves by 15 and it increases movement speed and life regeneration rate. The funniest part -- and what makes me think this could be a prank by our dear game designers -- is the tabard's use is described as: "Use: Show how heroic you are! (55 Secs Cooldown)" and the bottom line description is, "The Mark of a True Hero." It seems that perhaps the glitch was caused by an error in the cache because when it was cleared the tabard's description correctly matched the Summer Flames tabard.

[Thanks, Jagoex and James Vertovec!]

I've found recently in my raiding of the Sunwell Plateau (here after and forever more referred to as SPLAT) that there are a few places folks shouldn't go.

Kalecgos is one of them, that boss should just be wiped off the map. He's just that annoying. But baring that, there are these lovely little hedges placed around the instance. Don't go on those. If you do, you might just make your raid leader and Warlocks scream at you.

If you get on one of these hedges and step the right way, you'll find yourself stuck behind them (click the image above for a high resolution version), unable to get out. The only way to get out is for you to hearth, for a Mage portal to be placed behind the hedge, or for a Warlock to summon you out. All the while you've taken up a good couple minutes of raid time.

Mania wants to know (and so do we): can you train the bears in Zul'Aman or not? We at WoW Insider also heard a rumor over the weekend that the bears in Zul'Aman were trainable again (we heard that when the trolls riding bears split up, you had a short period of time to pick up the bear as a Hunter pet). But alas, all reports since then tell us that's not the case -- even if bears were trainable for a short period of time, they aren't now.

Which isn't too surprising -- Hunters have a relationship to wild animals, not trained ones, so the fact that you can't steal bears from the trolls falls in line with Hunter lore (although, if you wanted to make the case that the bears were actually pre-trained and that it would make them easier to train, you probably could, even if Blizzard didn't listen). And it's not like there aren't other bears to get in the game. Blizzard should definitely have some fun pets to get like this (as long as there's no huge gameplay bonus to be gained), but apparently Zul'Aman bears aren't one of them.

Of course, you can always go get your bear mount -- we've got a guide that tells you exactly how to do it. And hurry -- even those won't be available forever.

For some reason, the first evade bug moment I remember happened in Zul'Farrak. We were clearing the basilisk pulls before attempting Antu'sul (why is it that the optional bosses always have a couple of sweet warrior drops?) and the mage in the group wanted to skip the whole thing. Impatient, he decided to start nuking away from atop one of the hills surrounding the area and managed to pull aggro, but the basilisk couldn't path up to him (and to be honest I'm not sure how he got up there) and promptly went evade. He wouldn't come down because he rightly knew the mob would hit him, and so it took us a solid ten minutes of arguing before he finally came into the monster's reach so that I could taunt it.

I'm thinking about this because of the Isle of Quel'Danas dailies, specifically the quest Crush the Dawnblade. For some reason whenever I do this quest I run into Dawnblade Summoners who are evading. This puzzles me because I can't understand why a ranged mob is evading: it doesn't have to path to anything to hit it, just get into range. Is there some way a hunter or some other ranged class can shoot them but stay out of their range?

A couple of people have posted about the Shattered Sun Peacekeepers slacking off on their jobs lately, quite possibly thanks to something Blizzard fed them in Patch 2.4.2. In their reports, they complain about Peacekeepers attacking them for no reason, sometimes not even in retaliation for attacking (or defending yourself against) a member of the opposing faction. I can actually empathize with this as I encountered the ill-placed wrath of the Peacekeepers myself when I rezzed my wife's toon in front of the Staging Area. Without having done anything other than rezz, the Peacekeepers promptly charged and made short work of me.

In my experience, I have found that the Peacekeepers around the Shattered Sun Staging Area have been slacking off. In fact, my wife's toon was ganked right in front of the building and the so-called Peacekeepers did absolutely nothing. Sensing a bug, my wife wrote a ticket and got a somewhat rude e-mail response saying that -- you guessed it -- it was working as intended. An Alliance guild on my server seemed to be aware of the fact and exploited it to full effect, killing solo players who could seek no refuge under the apathetic -- or even hostile -- Peacekeepers.

According to reports, it's a known bug -- one player even made a video to document it -- but so far Blizzard has turned a blind eye to it. I got a more sympathetic response from my GM who at least mentioned he'd look into the situation. An in-game GM even reset the Peacekeepers in order to see if it would change anything (it didn't). I don't mind gankage... it's part of being on a PvP server. But when an area is supposedly a sanctuary, you don't expect to go through the hassle of a fight. Even worse, you shouldn't have the Peacekeepers tossing your butt around when you're being peaceful yourself. If things keep going the way they are, The Shattered Sun Offensive should probably downsize or hire some more useful temps.

I love hotfixes. They're like patches you don't have to wait for. Just posted by Daelo, WoW's lead encounter designer (who I've been seeing a lot of lately, but don't remember seeing much before) is a brief account of hotfixes to Archimonde and the Eredar Twins. For Archie:

We just implemented a hotfix for all realms that makes Archimonde's doomfires no longer be able to move right through him after they spawn. Their movement should now be much more consistent with the previous patch's behavior, and melee should have a bit easier time dodging the doomfires as a result of the change.

He goes on to note that any other problems people might have noticed have been un-reproduceable at Blizz HQ, but they're still keeping an eye on them. As for the Eredar Twins, they "hotfixed a bug in the Eredar Twins encounter that prevent a Hunter's Feign Death ability from working if Lady Sacrolash was alive." Nuff said there. These fixes should, as far as I can tell, be live now on the US and the EU realms.

Before I start this post, I should warn you that every single post we do about the size of something ingame must, by contractual obligations, contain a risqué double entendre somewhere within. Be warned.

Reader Veras was nice enough to point out to us that as of the 2.4.2 release, Tauren two-hand weapons have returned to normal size as planned. It seems to me that this got fixed fairly quicker than other size issues that Blizzard has had. We still have no idea how their code works (and what they're changing that causes all of these weird issues), but at least they're getting better at fixing things.

Of course, as any Tauren Fury Warrior will tell you, it's not the size of your two-hand weapon -- it's how you use it. Contract fulfilled.

Well, you have voted, and the votes have been counted. (Note to Michigan and Florida residents: Your votes have not been counted because you tried to move your primary up too early. Sorry.) This blood elf with an undead face, courtesy of Rhodarr of <no way out> on Nera'thor-EU, is the winner of the first Glitchstravaganza. Rhodarr barely squeaked by Gnatt of <Vanquished> on Dath'Remar's glitched graphics card, winning by a plurality of 27.1% to 26.4%. Sorry, Gnatt -- there'll be no recount here. A pat on the back goes to Guydebord of <Suicidal Tendencies> on Gnomeregan, who somehow managed to place below "None" in the voting.

Welcome to the gallery, Rhodarr, and proudly proclaim yourself the victor!

Do you have any unusual World of Warcraft images that are just collecting dust in your screenshots folder? We'd love to see it on Around Azeroth! Sharing your screenshot is as simple as e-mailing aroundazeroth@wowinsider.com with a copy of your shot and a brief explanation of the scene. You could be featured here next!

Remember to include your player name, server and/or guild if you want it mentioned. We prefer full screen shots without the UI showing. Thanks for participating in Glitchstravaganza, everyone!

As you may recall, during yesterday's Around Azeroth, I requested submissions for today's Glitchstravaganza -- a celebration of all things glitchy in WoW. The response was so good that it was difficult picking out the top five. I gave consideration to UI placement, uniqueness of the bug, and overall visual impact of the picture. I cropped a couple, as we had some technical difficulties with the gallery on this one and had to rely on the smaller shots instead.

Finally, we had five photos that dealt with five different bugs. An honorable mention goes to Fulminate of Dragonmaw-US, who sent in the sixth-best bug: the arakkoa to the right of us, who appears to have mated with a member of the Consortium and gone into a sort of half-existence.

Ready to move on to the top five? Read on past the jump for the contenders, and the final poll, where you can pick your favorite of the featured glitches (including the first one.) Polling continues until April 24; the winner will be honored next Friday.