I'll let you know next reset - we had the Offhand drop on our first kill

Unity, an Alliance guild on Jaedenar EU had the same thing happen to them. They actually got 4 warglaives (2 sets, so not the same hand item) on their first 5 kills.

First Kill:
Nothing...Last person alive dies to a Shadow Demon right as the "death" scripted event starts, Shaman ankh's but no tag so Illidan despawns with Maeiv and company taking any loot with him. Thought they'd fixed this problem? :| Either way stuck waiting for a GM ticket but seen so many different results for this, regardless he's dead and cant be reset, just a question of if we get the loot or not which is bloody annoying to happen on our first kill as it really ruins the mood of what should be a celebration.

You will get your loot, don't worry. This happened to us a while back and we basically sat around for a couple hours until we finally got in contact with a GM who gave us our loot. If you're interested in details there's some info and screenshots about it and how the GM handled it on our website (lawnpirates.net).

Not sure I'd sit around and wait, it took 3 hours for a GM to get a few pieces of information from me and then tell me I'd hear from someone. Five days later I got an email from a GM listing the loot and asking who got what.
So you will probably get your loot but it may take a while.

It was an encounter bug. The blaze wouldn't spawn on the ground if the tank resisted it, or something along those lines. Also the very first couple iterations of Illidan you could spell reflect blaze to kill them off. This could also be done on the blue flames which got fixed a lot later on (Late September). It was pretty funny when we were learning Illidan, we had someone get 10,000 Black Temple reputation from the tanks killing off blue flames for 20 rep each during phase 2... good times!

We're in the process of learning Illidan and encountered some wierd behavior from the Flames. Everything we've read said that flames only charge targets that were far away, but last night our tanks experienced charges even though they were only 20 yards apart. Here is a video of the P2 learning attempt from last night.

RapidShare: 1-Click Webhosting

The Flame from the right side charges the left side multiple times before finally enraging and wiping the raid. Can anyone shed some insight into this?

I'm at work so I can't get your video, but....

Your distance to the other flame is irrelevant - your distance to the blade on the ground is critical. As mentioned on the first page of this thread, you can be as far away from the Flame as you like as long as you are within the invisible "aura" defined as two circles with their centre points at the blades on the ground. Additionally each Flame cannot be pulled too far from its blade.

Any Shaman totems down? They still charge totems unfortunately.

You need to find the cause of the first charge, any charges after that are likely to be because the Flame is too far away from its blade.

It's been explained earlier in the thread (you might be able to find it by searching this thread for 'charge').

The Flames make a decision to charge based on the distance between the player and the closest Warglaive. If the tanks are 20 yards apart they are probably too far away from their own Warglaives. You can probably find a screenshot with highlights of the "safe zone" if you take a look earlier in the thread.

I don't think this is the case anymore. We've been using totems since our first kill a month ago and never had the flames charge.

It seems your druid tank took his flame too far away from his glaive. Looking at the minimap, he was at northest point, which is too far, he has to stay in "his" semi circle.

Nope, we don't use totems during P2.

Yea, I guess it does seem like he went a little bit too far away from his totem. I'll let him know to not pull that far in the future. Thanks.

I don't recall exactly when they 'fixed' the totem dropping + charge issue, but I can confirm that totems are perfectly fine to have up at the beginning of phase 2 and replant at any time during the phase.

We use totems in phase 2 and have for quite a few kills now with no problems. I believe that issue was fixed or we've been really, really lucky in not experiencing it for months.

On our second night of attempts we actually managed to get our first kill. We were so delighted with this very fact, that it took us over a minute to realise, that Illidan's corpse despawned. Contacting a GM resulted in him telling us, that he would forward the issue to a specialist GM who'd get in touch in with us, and that this would take at least 24 hours. Now, can anyone tell me how things are going to be handled from here? I assume, that we will receive a message concerning what loot we get, but will the person who wrote the ticket have to decide immediately upon the allocation of the items or will we have a day or two to sort that out with the people involved via forum/ingame? Anyone who has been in this situation?

At 1:33 into the video, the druid tank takes his Flame too far along the rim of the circle. It takes another 2 seconds before the other Flame charges him, but that's the point where he went too far. At 0:13 into the video when he initially grabs his Flame, that's the extreme limit of how far around the circle the Flame can go. There's a wonderful diagram in the very first page of this thread that should be burned into your tank's mind, or printed out and plastered all over their walls until they learn it.

Has anyone seen some weird Misdirect/aggro behaviour on transitions in P3/4/5?

We've killed him twice now, but by trial and error it seems that he is very touchy on transition aggro in the phase where he changes from "Demon" back to "Normal" form.

Our Hunters are reporting that they slap a MD on the MT just before he transforms, but if they shoot fractionally too soon all the aggro is acquired by themselves and not transferred to the MT (even though the MD buff counter reduces by the number of shots they have fired. Illidan's behaviour backs up their story - he runs over and slaps them down if they don't manage to Feign Death in time.

Obviously we have amended our strategy slightly so that we now wait until he has actually acquired a target (be that the MT or someone stupid enough to leave a DoT on or throw a heal) before the Hunters actually fire off, but he does seem really touchy on this particular transition.


It would make it a lot easier if he wiped aggro as soon as he starts the emote to change form (as he does when going from "Normal" to "Demon") rather than at the end of that emote.

We experienced something along those lines last night. I usually cast MD on the MT as he's transitioning from his demon phase to "humanoid" phase and fire my shots after he's acquired a target and it has never caused a problem. Last night however, during one of the transitions, he immediately ran towards the warlock. I fired my shots after he acquired the warlock as his target but it didn't sway him. He went over, one-shot the warlock tank and then shifted towards the MT. It was a one-time issue though so it wasn't a big deal for us since the lock was soulstoned and we carried on as usual, but it was a bit annoying to say the least.

The same thing has happened to us, only multiple times, and we don't have a clue what causes it. After our lock gets aggro and runs away for demons, he doesn't do anything for the rest of the demon phase. When Illidan goes back to human form, he beelines for the lock, kills him, and goes to our tank, who has had multiple misdirects loaded onto him.

Yes, he has often headed for our Warlock too despite no residual DoTs running etc.

Looking at what's happening there's a few possibilities:

(1) He doesnt always wipe his threat when he is supposed to (unlikely as he would go around killing all the dps classes before the MT could get him back and we arent seeing that)

(2) The threat wipe is not a complete wipe, but a fixed dump (very unlikely)

(3) There is some sort of lag in starting the new threat list even once he is back in "normal" form. This would show up as what we are seeing i.e. Shots Misdirected before he starts the new list are ignored and he often heads for the Warlock.
This explanation would also account for the one try we had where he went for the Warlock and a Paladin cast BoP on him at which point Illidan headed for a Mage who used Ice Block. Illidan then one-shot a Shadow Priest before we got him back under control. I didn't look at the time but the probability is that the Shadow Priest and Mage were number 2 and 3 on threat after the Warlock.

So - it looks probable that the new threat list doesnt start on time and the only workaround will be to have your Paladins ready with BoP for the Warlock and/or your Warlock soulstoned so that you can keep him alive until the new threat list starts.

It's not impossible to work around but a truely annoying bug.

Another question regarding the blazes...
We've killed him once now, having solid phase 2's, but as a flame tank, there's one thing that keeps bugging me.

How exactly do the blazes spread?
On a movie I saw, it seems like the tank only took a few steps back, I generally have to move quite a bit backwards to get out of the blaze, I'd say my "rotation" before I turn is 4-6 stops, depending on blue beams and stuff.
Sometimes it seems like they cast the blaze, I move back, then it seems to kind of come after me.

Do they "piss on the floor" so to speak, all the time while the casting animation is up? I guess that would explain it.
I meant to experiment a bit more with that, but then Illidan died, so I had to push that back for a lockout

Not really a big deal since all it does is make my job a wee more uncomfortable, but like with a bed, even a tiny little bit more comfort can make you sleep of so much better

As far as I understand it, every time the mob spews flames out, it spawns one circle directly underneath the position you were. This circle is much easier to see at certain spell detail levels (my slider is slightly below half for Illidan).

The best gauge for me was/is moving right to the edge and seeing when SCT stops spewing out purple messages. Five spots sounds just about right before turning around for the backward track. I start with five on the outside, then four on the inside, sometimes truncating to minimize blue blaze damage should the area be riddled with blue blazes. If I'm not mistaken, the blazes last either six or seven "spots" before disappearing, so five on the outside is already more than enough to make sure you aren't standing in the tail end of your own blaze trail.