Yesterday I've noticed a bug with Flame Leviathan, most of the time when thrown off a catapult I would land on the Leviathan with 1 hp (taking a hit for exactly my max hp-1 while mid air). Thanks to mana shield/fireshield and a healthstone it was manageable but I wondered if someone faced the same problem?

I'm fairly sure this is a UI issue, your frames will show one value but you still have all your HP, happens to me all the time on FL for other players(its prob an issue from QuickHealth mods) I end up just turning on friendly name plates which always show the correct value.

We didn't have this bug in our 25 man, but guilds working on him a couple hours after we killed him experienced it. If the fix to the phase 4 P3Wx2 Laser Barrage was a hotfix this bug could have been introduced at the same time, allowing guilds that pulled him early in the night to kill him normally while later raids would have the heat wave bug.

This is an xperl issue if you haven't updated to the most recent one, same guy with this problem in our raid kept freaking out over the same tank dying almost every boss fight, but only in his raid frames.

Can someone give a *rough* idea what kind of a kill time we should be looking at for 10-man flame leviathan with 0 towers, given that every char is dressed in 75-100% naxx10 gear? (the balance being a roughly equal mix of pre-naxx gear and naxx25 gear, plus the handful of ulduar10 epics we've collected)

I ask because we're getting 0-tower kills nice and reproducibly, and this is enough for most of the raiders, but we're taking roughly ~5 Minutes to do so, by which time both bikes are destroyed, and the demolishers are broken or severely bashed around. This... is fine for progressing deeper into Ulduar, but pretty much means we needn't bother with the hard modes, which at least I would like to do, and I'm sure I'll be able to interest some of the others for it if I can convince them that we can do it.

Assuming, as I do, that we're failing at DPS (rather than at something entirely different - EG staying alive), it would be great if someone could also give a rough idea of how much damage should be coming from which source? EG: We've barely used the pyrite attack of the demolishers at all - after personally trying it a little yesterday, it seemed to be a very substantial damage source. Alternatively/additionally, one of our MTs believes we're not getting the oil patches lit consistently and this is a major problem.

Finally, we've been having trouble collecting the pyrite barrels... they seem to disappear almost immediately upon landing on the ground after we shoot them down. Could we be doing something stupid here? (maybe they can be grabbed out of the air? Or we're using the wrong attack to bring them down?)

I realise this is a lot of stuff I could experiment with myself or in a small group, but given we start the raid on the wednesday (EU reset day), and I don't have a non-sucktastically-equipped level 80 alt, I currently don't have a window to do so. And WoWWebStats boss listings for Ulduar10 don't seem to work at the moment

Our last 10-man easy mode FL kill took almost exactly half that time. Since WWS currently fails at parsing Flame Leviathan kills, I can't really tell you the damage breakdown, but I do know that not using pyrite attacks is a bad thing. I always have our demolisher drivers unload their pyrite whenever the turret killers finish their job.

I don't think that's the best way to do it. Pyrite stacks, and the DoT lasts for 10 seconds. Just unloading it all during shutdown will only net ~20 seconds of the DoT ticking, and for most of shutdown the ticks will only be for the lower amount of stacks. However, if you start stacking pyrite right from the beginning, and try to space it to refresh every 7-9 seconds depending on how much of a safety buffer you want, you can get almost a minute's worth of DoT ticks, and by the time shutdown occurs it'll already be ticking for near the full amount. I'm not sure how high the stacks can go; I was a demolisher driver for the first time this week and the passenger never bothered to pick up more pyrite during the fight so I only had the initial 10 charges, giving me 10 stacks but still easily shooting me to the top of the recount chart (if that's at all accurate).

So, we verified a rumor last night, that tanking XT-002 right in between two of the trash piles on the east side (probably west too) results in zero adds spawning from those piles. It must be his proximity to a spawn point that results in nothing spawning there, but I can't for the life of me figure out why Blizzard would code XT so that he nullifies spawn points if he is near them.

It is like they designed him to push towards this strategy, but honestly it guts the whole fight because not only do you only get adds spawning from way the hell across the room, but you seem to get less spawns overall.

Actually, you do still get elite robots spawning from the nearby piles, but not that scrapbots or bomb bots.

I don't have a good sense of what an ideal % damage from each source is, but I can verify that stunning him in a lit tar patch is HUGE. I'm generally a Chopper driver, and if it's my tar patches that he gets stunned in almost every time, I've ended the fight higher on damage (Recount, possibly take with a grain of salt) than one of the Demolishers, mostly from the huge burning tar ticks during a stun.

Every little bit of extra damage really adds up on FL. If they're not already, have your Chopper drivers spamming their frontal blast on him when their tar is on cooldown and they're not running down a parachuting turret killer. Gunners can do damage to him when they don't see any Pyrite, etc. Some people seem to think that the only time they can do meaningful damage to him is while he's stunned, but it's better to think of it like Curator, where you certainly want to unload during the stun/evocate, but that doesn't mean you shouldn't keep hitting him the rest of the time, so long as the important parts are still being taken care of.

For what it's worth, you can get this information out of WWS in a rather round about way, thusly:

- Select the flame leviathan fight of your choice
- Select a _character_ that took damage from the flame leviathan (as far as I can tell, the catapulted people will always take a little damage, no matter how good your picker-uppers are).
- Go to breakdowns and select the flame leviathan from the "damage in" sources (Now you have the damage in/out for flame leviathan)
- Go to breakdowns again and you'll see what vehicles etc the damage came from. These vehicles can again be clicked to see how they did their damage (don't forget to choose "view all" to see _all_the vehicles of each type, rather than just the single one WWS seems to arbitrarily pick).
Note, sometimes WWS seems to lose track of which fight it's tracking and fall back on "all fights"

Roundabout and fairly fiddly, admittedly, but potentially instructive.

In making this post I studied our results a lot more closely (previously I'd just looked where I expected to see the highlights, and not seen anything totally glaring), and some extreme discrepancies turned up (one of our siege engine gunners did roughly one tenth of the damage of the other?!), so either take a WWS analysis by this method with a grain of salt, or I've found some major issues we can definitely work on :P I'll manually parse the results to hopefully confirm or deny WWS dodginess and report back later [1]. If someone is interested in our apparently very bad breakdown, PM me - I don't really want to clutter up the thread with those excrutiating details.

EDIT: regarding [1] The huge difference between our siege engine canoneers, is that one did an average of 11.563 damage per hit, the other an average of 76.544 damage per hit - with roughly equal numbers of hits. I presume this is because, as mentioned eg on Flame Leviathan - WoWWiki, the precision of the hit matters for the canon. Presumably one of our canoneers thought "I just need to hit", not realising this detail. This will be fixed for next time ,-)
I'm still interested in other people's damage break downs of course - the discrepancies I've seen explain a fair bit, but I'm sure there's a lot more potential damage we could have dealt by other means

While we are by no means expert vehicle drivers, looking back at the logs for our last two Flame Leviathan kills it appears that 60% of our total damage came from Salvaged Demolishers, with about 85% of their damage coming from Blue Pyrite. Our best Demolisher did 20% of the total boss health using only Blue Pyrite, so I would say stacking that DOT is the key to killing him quickly.

Incidentally, the next major contributor in our kills have been Siege Engine Turrets, doing about 25% of the total damage. The choppers and their tar patches have only accounted for about 4% damage on each of our last two kills. I'm not sure if that is a normal result or if we are just not using the tar effectively (I'm guessing the latter).

I've editted my previous post to include my assumed explanation; I'm fairly sure the room isn't large enough for combat log range to be an issue (paticularly since I believe the default range was substantially increased some patches ago?). In any case the total damage I see in our fight is just over 23 million, which is right on target for the (10-mann) Leviathan's total "health".

Has anybody been faced with the problem of a fusion punch cast and a rune of power landing right on him at the exact same time? Last night we had several wipes because of this. Is this just bad luck or is this just something the encounter is supposed to do? It seemed almost impossible to pull him out and the tank was one shotted everytime.

Yes, I've had this happen a few times while tanking him (in 10s). I usually just use cooldowns and hope that the dispel comes quickly. If the dispeller is quick enough the tank can avoid the ticks of the dot. I've had them dispel so fast that I don't even see the debuff come up on my UI!

If you're talking about 25s, the fusion punch does 35000 plus the 50% from the rune of power which is 52500. Subtract the tanking damage reductions and you're in the 45k area which is survivable if the tank uses a cooldown and the dispel is instant.

If you're watching Runemaster's cast bar, you can see rune casts before they actually happen. (He even targets the friendly if he's going to cast it on one of his allies, although he bugs out for a second before targeting himself if it's under him.) Have the Steelbreaker tank running with him before the Rune is even cast, and it might be easier to avoid.

Its also possible that that player was naked. In 10s we had one player naked in a demolisher and he had a massive fraction of normal hit points. I want to say he had 130k while we normally have around 850k. I've seen people try this to avoid repair costs from death.

Just as a side note for achievement hunters, the text for Disarmed is poorly worded:
"Destroy both of Kologarns arms within 12 seconds and then defeat Kologarn on Normal Difficulty."

This text seems to indicate that all you have to do is kill both arms quickly during a successful kill attempt--much like the "Shattered" achievement for Ignis. However, when we did this, both arms respawned before we finished Kologarn off, and we did not get an achievement. It's likely that both arms must still be dead when Kologarn dies in order to get this one.

I can confirm that this works wonders. The Rune of Power is a ground targeted effect, not NPC targeted, so it pop up wherever the boss was when Molgeim starts casting the Rune. Our MT got annihilated by a Fusion Punch as he was trying to move Steelbreaker out of a Rune on an early attempt, but after setting his focus to Molgeim it never happened again. Similarly, I vaguely remember DBM having an announcement when Rune of Power starts casting, which should do the same thing, though perhaps with a fraction of a second more lag.

We've done this two weeks in a row now. Hit it pretty easy just working on the right and letting the AoE abilities that are part of players normal DPS rotations (Living Bomb, Divine Storm, etc) work down the left arm as well. Seems like on the 3rd right arm we have Koolgan low enough that 2 arm deaths, but not 1, would kill him so once the Right gets even with the left we split the ranged/melee and finish them off at the same time, while its lined up well for us we had the plan of DPSing out on the body once its below the level it would take for two arms being destroyed to kill him to avoid the risk we'd got him to the point 1 arm would kill him.

Heat wave has supposedly been hotfixed, for those who had trouble on Mimiron last night.

I can confirm this. You must kill him along with both arms within the time window to get the achievement.

We got this one the other week - when we did it, we popped both arms to kill him, and he died the moment the second arm died. Assuming no other bugs interfere, I would guess that your surmise is correct - it should be worded as 'Defeat both of Kologarn's Arms within 12 seconds and then defeat Kologarn before the arms regrow', or 'Defeat both of Kologarn's Arms and Kologarn within 12 seconds'

Happened to us last two times we killed her as well. Second time we had wiped once before and the defender DID spawn during that wipe. Didn't spawn the next attempt and she died. Seems fairly random. It apparently happened to another guild on our realm as well so its unlikely to be that rare.