That is how we ended up killing him because people were failing at eye beams.
The problem is the 8 second silence. But your tanks can blow cooldowns if your healers catch it.

I'm not sure I buy the range preference theory. We had a good number of eye beams on Melee, or people closer than 15 yards. We always had many many people outside 15 yards.

Your melee is either standing too far away(taurens can max range it, or they could be dpsing arms from other sides). If people aren't lazy I might be able to get a video up soon, but go ahead and try it this reset. We seriously had all but a hunter and a shadow priest kite every lazer, and none came to us in melee.

The range restriction does exist in our experience.

We tried a setup where the majority of the raid stood near the tank and a few people at range. This worked ok (other than healers getting locked out frequently) until one of the designated kiters died. As soon as the beam target person dies the beam will randomly choose anyone new in the raid to follow. Since the majority of the raid was bunched up in melee it almost always went there.

In the end it was more trouble than it was worth and we went back to all healers/casters being spread out in the room. People will eventually get used to responding to the beam and if you can have someone focused on calling out the beam targets name it should become trivial.

Also, a holy priest with the talent Body and Soul (60% movement speed inc for 4) can also help out the slow people in the raid.

Can confirm that the beams seem to target anyone farther than 15 yards from the center of his torso. We were doing a tank swap where I'd tank until the right arm was almost dead, then the Warrior would taunt off and I'd handle the adds. I held the adds underneath his destroyed right arm and was the target of Eye Beam a couple of times. We also had melees be targeted with the beam if they were too far back in Kologarn's hitbox, as well as having the instawipe breath hit us while several people were meleeing him. The lesson is basically that our hitbox to melee him is far larger than his hitbox to melee us, and people that are intending to be in melee range need to hug his torso.

Also, note that the Kolo-bridge is NOT as wide as it looks. We had a few people fall to their deaths through his shoulder on our right-hand side. It was highly reminiscent of the Crack of Doom in SSC.

Quick, trivial question: XT-002 and Flame Leviathan are "engineerable", and of course Freya's Gift drops that Alchemist's Cache. Is Razorscale skinnable? We skipped her last week, so just curious before we do her this week.

While I haven't done it myself, I've heard reports of the Disk dropping off of Runemaster last.

Anyone figured out how to avoid Mimiron P4 weirdness in terms of tanking and the glare ability?

In today's patch they have claimed to fix the P4 shock + glare timers so they don't overlap.

I've been wondering myself. We tried various things last night in a few hours of attempts, but the best thing I've read so far is to have your tank blow cooldowns and stay in during the blast. Most of our attempts last night were flawless tell phase 4 then we would inevitably have glare flipping killing a few people.

I assume you mean if he points the glare at your tank and the tank tries to avoid it and it drags the barrage?

The tank should slide counter clockwise ASAP, and maybe get a pain suppression or Guardian Spirit in case he takes a few shots of the laser. A tank should be able to take 2 hits. 3 if it's a bear with a glyphed survival instincts.

Also, don't use the baby spice trick to make it easier for melee to see rocket landing zones. That makes it very difficult for the tank to accomplish anything in regards to laser barrage movement.

I believe our easiest solution was going to be a tank behind the laser barrage taunting. Apparently the base was taunt immune in P4.


If you mean the Shock Blast near barrage problem, then you need Garudian Spirit or Shield Wall+Last Stand or Pain Suppression + HoS/Bubble or Glyphed Survival Instincts+Barksin+Pain Suppression etc. etc. etc. So your tank doesn't move.

It's not taunt immune. You must have taunted it too much and had diminishing returns.

The data disk drops off Runemaster, we did Runemaster last our first kill and got one.

It is most definitely not immune to normal taunts. We had thought up a countermeasure for P4 where we were going to have a hunter pet tank it for a while since it can live through a shock blast with no cooldowns, but the base IS immune to pet taunt.

I thought this might be the case.

We had been having our tanks taunt a lot to try and keep him stable. This was before we came up with the angel wings/cooldowns rotation.

So, that is the simple answer to Barrage pointing right at your Tank. Have a tank behind the barrage taunt so the first tank can run away.

According to MMO-Champion:

Update - Algalon seems to despawn after one hour of fight. This is most likely the same mechanics as Vaelastrasz allowing raids to try it only one hour each day.

Ah the "fun" mechanic has returned.

Once you reach Agalon you can get to him any time after FL and XT right? You don't need to clear the instance first?

Valnoth on the WoW forums:

World of Warcraft - English (NA) Forums -> Algalon only allows 1 hour of attempts

Says the respawn on Algalon is one hour per week.
So 1 hour of attempts in a raid id. Blizzard really doesnt want anyone to kill this guy.

Wasn't this mechanic in place for Nefarian when BWL was first released? It seems like a pretty silly pacing mechanism but it's a brilliant way of leveling the playing field between hardcore and casual guilds.

You're thinking Vaelastrasz.

Nefarian had a bug resetting that forced you to need to soft reset the instance to get him to show up again. Vael was simply gone.

Personally the Agalorn mechanic doesn't bother me. We've had discussions about artificial progress chokepoints before, and I think the consensus is really that they're not such a bad thing.. definitely preferable to having guilds play 24/7 for a kill and then having nothing to do for the next six months.

Nonetheless, it does look like Blizz is conceding that they can't design another 4HM - a boss that challenges top guilds for months without being ridiculously unfair. (Well, I guess there were the taunt resist issues back then..) At least it makes sense that he leaves lore-wise, however.

The fight looks pretty awesome, though. I love bosses with a "cosmic" theme in general.

The main delay in downing 4HM was that it wasn't until the encounter was experienced, was it discovered that you had to have an unusual number of geared tanks to have a chance of completing it. Therefore those tanks were geared after that progression block was hit, requiring several weeks of farm time.

If the same encounter was initially released today, with hybrids galore and dual specialization, it would not take nearly as long to kill.

4/8 T3 wasn't crucial, but most raids only had 4 tanks geared for raids at this point, if that.

Eh, maybe, it's not my impression that DnT just rolled over them because they got 4/8 T3 on 8 tanks.

In any case, then, if 4HM are excluded, I think the longest time up for any single boss (without being nerfed) would be M'uru, who was considered to be incredibly hard (to the point where many Top 1000 guilds were demanding a nerf), but who still lasted for less than a week.

Maybe they should've just tuned Ulduar to be incredibly difficult and then built in a mechanic that would lower the damage and health of all the mobs by 5% every two weeks. That seems like the best way to please the masses.