Why can't we kill Magtheridon? - Page 16

Rinced · 06/09/07, 7:50 AM

Originally Posted by sp00n

The spell details settings were the first one I set to minimum right when they introduced it.
It really upped my FPS if I remember correctly, and the only time I moved the slider again was when we began to try Ouro.

Will have to see if it has any effect on our next try, but whatsoever, cave-in on Gruul is perfectly visible for me.
Maybe it's just Magtheridon filling my screen too much, distracting me, and I should scroll out a bit for that fight.

I thinks its better to work with debuffs - get a nice buff mod to sperate buffs and debuffs and turn the debuff scale up.
Thats the way i do it for Nightbane / Gruul / Magtheridon.

Cesar2000 · 06/09/07, 7:54 AM

The falling debris is hardly a problem tbh... We've had many kills and I can't remember anyone ever dying to it, and probably 50%+ of our raid doesn't even know it exists. He will die very fast after 30% and if somehow a clicker manages to get gibbed, its easy to do a quick rez, or use the back-up.

Dayone · 06/09/07, 3:06 PM

Originally Posted by Schnappi

Wait 3-4 seconds before using Shield Slam when he releases. He seems to be somewhat immune at the moment he releases, resulting in a Shield Slam doing no damage. Just spam heroics and sunder at release, followed by a Slam after a few seconds.

Can anyone else confirm this? For the past 2 days, I've been opening with shield slam and Mag would chase a healer until I land a few sunders and heroic strikes. We are still learning the fight but didn't have this problem last week.

Originally Posted by subscience

Just have folks stop healing for a moment while Magtheridon breaks free. You can also advise people to click off HoT buffs.

Is that what you guys actually do?

DeeNogger · 06/09/07, 3:28 PM

We just have the MT pick up Magtheridon with miss direction and whatever typical snap-aggro attacks he uses (I assume heroic + sheild slam). Having healers stop healing when Mag first breaks free sounds really risky to me. The first few moments of mag free and the 4th or 5th add up is when healing is by far the hardest. Stopping to heal even for a moment might result in the loss of a tank.

AndrewCarr · 06/09/07, 4:14 PM

In our early attempts we had Mag killing healers, so it's understandable that people might want to cut healing. But the issue can be solved by using MD/Tank abilities smartly.

Once I remembered that I'd heard about Mag's aggro being odd(first 3s of the fight, from counting in my head) and timed my misdirects better, and once the MT realized this, we didn't lose healers.

Our initial problem with aggro on Mag was that we wasted everything(MD + tank's rage), then he seemed to reset aggro after 3s and switch to another target, kill them, and go back to the MT. Our MT was also tanking Add 1, and then helping with interrupts on Add 2, so his rage bar probably wasn't full either.

[Edit:] Dayone, I'd say my experiences with it also confirm that Mag's aggro is odd for about the first 3s.

Jassamoris · 06/26/07, 7:09 AM

I have a quick question : we've been having solid progress on Mag, but we keep failing at one or two specific cube transitions (when he's usually at around 40-50 percent). It seems that a few cube calls in, his quake seems to coincide with the blast wave, first right before it (and we usually manage to interrupt it after mass chaos), and secondly, when the wave is directly cast during the quake, giving many of our clickers exhaustion and messing everything up pretty bad, causing a wipe.

One of my fellow officers suggested that we might have to eat a few ticks of the blast wave, in order that our clickers can click freely. What have other guilds done about this specific transition(s)? Are we just doing something wrong here

, or does there need to be a specific plan of action involving when to click?

Thanks in advance.

Quigon · 06/26/07, 7:15 AM

Once a cube click is over the next 5 people should get to their cube immediately. Don't wait, just get there and sit there with a dumb look on your face for up to 60 seconds. Even if you get flung, its not that far for a run back to click again... you'll be closer when the quakes happen - and hopefully wedged into a wall nearby. Yes, sometimes you have to move 5 yards and then click - its part of the encounter.

sp00n · 06/26/07, 7:15 AM

The quake stops when he begins to cast his blast wave.
Your cube clickers have to position themselves so that they don't get kicked too far away from the cube (I think it was already mentioned how somewhere in this thread).

You have his cast time + 1 or maybe even 2 blast waves time to click the cube. Just don't click too early, or you will be bounced away while channeling and therefore receive the debuff.

Zamaar · 06/26/07, 7:16 AM

Originally Posted by Dayone

Can anyone else confirm this? For the past 2 days, I've been opening with shield slam and Mag would chase a healer until I land a few sunders and heroic strikes. We are still learning the fight but didn't have this problem last week.

Is that what you guys actually do?

It's 100% true, I had problems picking him up (even with misdirections as the hunter was, like me, firing the instant maggy was released), just wait in his belly (so you can hit him a sec or 2 after he moves no matter where) and when he starts moving, NOT BEFORE, shield slam and the hunter should shoot, works 100% of the time.

vorda · 06/26/07, 7:17 AM

The wave is never cast directly during the quake. This is how Blast wave goes:

1.5 sec cast timer
8 (?) second channeling timer with damage ticks every 2 seconds.

Once he starts the cast timer, he stops earthquake, so this gives your clickers 3.5 seconds (-server lag) to get close to their cube and click.

The timer bossmods show is when the blast wave cooldown is over. You do not click when that timer runs out, you start clicking when magtheridon starts casting (the emote). And when he starts casting, he never does anything but that.

• Chicken · 06/26/07, 8:32 AM

Originally Posted by vorda

You do not click when that timer runs out, you start clicking when magtheridon starts casting (the emote). And when he starts casting, he never does anything but that.

This is really something you need to nail into people's minds. It's the most frequent mistake I see new clickers make; they click immediately when their boss mods Blast Wave timer is up, but if Magtheridon is slow on using his Blast Wave, you have an issue.

We usually work around this by having an experienced clicker keep an eye on the new guy for the first few clicks he does during the encounter, this way even if the new clicker messes up, you should have someone else nearby to help out. Also helps if the experienced clicker gives the advice about when to click during the encounter itself if it does go right with an early click (E.G. "Okay, it went alright now, but as you saw the other clickers clicked later than you did. When you should be clicking is when Magtheridon emotes he's casting Blast Wave, not earlier"). It connects in people's minds faster when these things get explained during the encounter.

nataku · 06/26/07, 10:40 AM

We just make sure people look for Magtheridon's actual emote of 'Magtheridon begins to cast Blast Nova' before they click, instead of paying attention to the boss mod warning that the Blast Nova cool down was over. This confused a lot of people in the beginning, but now everyone knows the mod is only a warning that Nova could be cast at any time. Also helps when someone experienced in the fight sees the emote and starts yelling 'click click click click' on vent (though not necessarily clicking multiple times >.>).