I noticed this too, and thought it was just the quest randomly bugging out. I didn't try it more than once...

(ps. giev miniwing!)

I also had this problem on my warlock alt today. I had to wait, till the bird respawned, after that I tried the quest fot the second time and now it worked properly. If I remember correctly, the bird aggroed and fought the mob at the landing point the first but not the second time, maybe the mob was further away.
I don't know if this bug came into the game with patch 2.3, but the quest didn't bug out when I did it on my paladin main.

That quest was bugging before 2.3 already.

I did it with another person on my mage. When I jumped down the bird would show the described behaviour for me. However, it would still move on my friend's screen and he was able to complete the quest. I had to start it over for myself though.

Fought Void Reaver last night and as a melee I always stand in the poundings, however this week I didn't get hit by a single one and Thro - WWS is the WWS to prove it. I don't think there was a certain spot I was standing that made me not getting hit by it, as there were others standing behind me, on me, in front of me etc and they were all getting hit. For some reason i didn't get hit, which was nice for my healers.

Anyone experience anything like this?

For kael this week - but not last week immediately after 2.3 - he wasn't pyroing as normal.

On our kill:

First shock barrier went up, didn't start casting a pyro. Seemed to turn at random people then target back on to me, but never left me. Melee'd and fireballed a bit.

Second shock barrier went up, used shield to absorb first pyro, we interrupted the second.

We had one or two more shock barriers after, for both of them he didn't start casting a pyro.

This seemed to be the norm on our first few attempts of the night (new people, offtank D/C'd, etc).


Also, last week, I had an enormous, gigantic lead on threat on kael due to all range dps killing capernian / phoenixes for the first minute or so he was up. Decided to run away from him and devastate someone who got MC'd before getting back on him (had done this for weeks). Proceeded to lose aggro, he killed about 10 range dps and healers before getting back on me. I am absolutely certain I had a 50% or greater lead on threat over all the dps that died, meaning the 30% rule coming into play is an impossibility, and he did not switch back to me in melee range after the first few people he killed with fireballs. In addition, I was not disoriented. Clearly some sort of bug.

Speaking of Void Reaver, his orb animation has changed. Instead of traveling directly to the target's location, it kinda arcs up then down. Some people in the raid said it felt like the orbs moved faster too. It cost us a wipe while ranged tried to figure out what to do.

At one point during Maiden on my warrior last night, I wasn't "revived" during repentance despite clearly being within range of her consecrate. I think the repentance ran its full duration before I could move again... but this only happened once during the fight; later the consecrate properly knocked me out of repentance. Maybe some mob AoE abilities are being capped at a certain number of targets... we were certainly melee-heavy for this particular Maiden kill.

Forgive me if this has been brought up before, but I did a quick search and found no mention of snowfall...

I noticed last night that it took exactly one minute less for the alliance to capture Iceblood graveyard than it took me to capture Snowfall. I think that possibly SF was skipped in the change from 5min to 4min cap duration on Graveyards and Towers.

Anyone else noticed this?

It seemed, shortly after the patch, that only the first cap (from neutral) was still 5 minutes, and after one side or the other had taken SF it was 4. That might have been fixed, or I might have imagined it, but yeah.

Yes, the very first cap of SF still seems to be 5 minutes. Once it goes to one side, it's 4 minutes like everything else is now.

Kael'Thas really doesn't cast Pyroblasts during his Shock Barrier now o.O. It was a bit odd :p.

Interesting. We went back and did Kael right after the patch and had very strange issues, but we came here and didn't see any posts about it so chalked it up to us missing something. What we saw was very similar to what you're saying though. Shock barriers with no pyros at all being cast, Kael suddenly deciding to fireball people other than the tank who was way ahead on aggro, lots of strange behavior that made phase 4 feel very random.

Question: Now that season 3 has just started, has there been any speculation on the likelyhood that Blizzard will buff the iLVL of BT/Hyjal weapons like they did with Season2/TK+SSC? Was the ilvl/season2 buff a once off or is it remotely/likely that a similar review will take place for current BT/hyjal weapons too (either now or within a patch or so)

More or less the same thing happened to us on Tuesday - after the shock barrier came down he ran around one-shotting twenty or so DPS and healers. Omen claimed that I had roughly 200% the threat of the nearest DPS. We wrote it off and came back and he did his "usual" bugging at 50% trick. Very frustrating.

Another change (I *believe* it's a 2.3 change) is that you can now swap bags from your inventory into bag slots, even if the bags in the bag slots have items in them - you used to have to empty them out, then put the bag into your inventory, then put the new bag into your bag slot. A small change, but a welcome one for those of us who don't have anything like 18 free spaces at any time.

I think you could always do this, or could for a long while at least. Just make sure that if downgrade a bag, the old bag has enough free space in its last (not first) slots and that it only contains special items if you replace it with a special bag (profession bags).

Also, the new bag must not be in your old bag when you replace it. That's about all it takes I think, I know for sure that I haven't had more than 10 free slots for half a year now ...

Last night we had Mother Shahraz turn around and two-shot our 33/28 warrior for no apparent reason. He wasn't even near close to the threat line (somewhere around 50-70% of MT) and the MT did not move.

Rayijin, maybe this is a similar thing that you observed on Kael? There's certainly something weird happening.

I believe that the issue that people may have run into was trying to move a bag from a bagslot that is inside the bag you are trying to replace. Try moving the bag from your main backpack to a bag slot and you'll never receive an error from it unless you're moving a profession bag to a slot that contains non-profession items.

It's been that way since vanilla.

The Flames of Azzinoth (Illidan encounter adds) are tauntable boss level mobs. Makes sense if Hydross is that way as well (the Hydross adds certainly are).


The Hemo 2.3.2 change was 110% weapon damage and the debuff will be 42 damage and charges will not get reduced by magic damage.

Hydross adds are lv62, not boss level. As far as I remember, Hydross himself was immune, leading to many a wipe due to many a warlock/shadow priest pulling him back over the line. (As a stop-gap, misdirects were often encouraged, though one particular hunter's misdirect literally mis-directed Hydross... onto a holy priest. What?) If he's tauntable, that must have been changed somewhere between the original Patch 2.1 and now.

(p.s. yeah, Illidan flames are tauntable boss-level mobs)

Hydross is (or was, rather) definitely untauntable...our pulling strategy used to have me gathering up the incoming mini-adds that spawn from stage left, and walking back to Hydross, at which point I'd taunt off the single add that had probably aggro'd the Hydross tank. Being a paladin, if Hydross was tauntable he'd have been on me, which never happened.

Thanks for the heads-up for saving me an embarassing wipe for when/if we go back to SSC. I'm guessing this is an intended nerf - the fight is a great deal more controllable if you can taunt at transition.

I'll try to confirm that tomorrow and if true it'd be a stunning change indeed. Hydross is completely trivial dps-wise but for the need to have a little patience. (Yes, yes, with any gear and practice, he's completely trivial regardless... ) If you can taunt him when he crosses the line, you can beat the enrage timer by 5+ minutes.

Well, don't I feel stupid now. He's not tauntable, our two tanks were just talking out of their asses when they claimed that. Somehow we still managed to kill him though.

From an incident last night, it seems that Evocation generates threat as you restore the mana now. Both in the old version and the new version, the initial buff will generate some small amount of threat, but since the old version just modified your threat-less spirit regen, the regen part was threat-free, so you could pop Evo just before a threat wipe and sit safe and happy regenning while you have to wait on the tank to get aggro anyway.

The story to go along with this is that previously, I'd tend to pop Evo just before aggro wipes on Hydross/Leo/Supremus to save my lost time. But last night, that caused Supremus to aggro me right off in a p1. I imagine someone must've healed in the 3-5s before I lost aggro/died, so I guess Evo ticks must generate more or only slightly less threat than small or medium heals?