Stunlocking adds in Levi EX

I have done a few tries on Levi EX as ot and have some trouble getting around the stunlocking of the mage add.
From my point of view it seems a win or wipe is dependant on whether I can stop the mage's castings or not.
On the first mageadd I build up with the first two moves of the RoH combo on Levi's tale, and then on mage - RoH - RoS - FB - SW - SB - stun - FB - stun - SB - stun

On the second I start with provoke - shield lob - RoS - FB - sw - SB - stun - FB - stun

Sometimes it works, sometimes it doesnt.... Sometimes he is dead just before the cast finishes. Is that a sign that I didnt stunlock him and the dps is very good, or did I do everything right and the dps was just barely enough?
Is there anything I do wrong, or is there something else?
Too low skillspeed? (mine is 391)
Too low accuracy? (mine is 478)

I appriciate every kind of advise about this.

I heard the add casts the dread thing at a certain % of hp. Could be wrong though since I don't play tank. So just need to watch the hp.

Yeah, I forgot to mention that. With the rotation in my first post I usually hit the first shield bash around 75-80% hp.

If the dps of the group is slow, this tends to be a tricky part.

1st mage add: shield lob - flash - CoS - flash and then start your stunning. Note that you can only stun three times. Just start after it casts its two first spells (I think it's ruin or something). You can time your 3rd stun: as soon as it casts "dreadwash" you stun it. If you can't, someone else stunned too which you can't do anything about at that point other than asking the group to not stun adds. If you happen to know exactly when the add spawns, you can pre charge RoH and open with that and then start stunning. Group DPS differs, so it might spawn earlier than you'd expect.

2nd mage add same story basically.

There is however a way easier method to handle this. Let the MT pull it, he can just spam his enmity rotation. You can focus on stunning it 3 times.. I don't know why people always do stuff the way they've seen it being done the 1st video everyone saw. MT will not get the head's AoE (dread tide) for another 10ish seconds, so it's save. If it takes too long, he can just run away after your last stun since the mob can't move anyways. Again, if you can't stun it, not your fault..

Note that if the dps is high, you can pull it with shield lob or flash and actually stun lock it since it goes down fast. Should be the case now that groups start hitting i95 average.

Thank you!

This makes sense. Obviously I have been a bit too much hung up in the rotation mentioned, and didnt know that I had to time the 3rd stun.

Hopefully I wont send more groups for a swim they dont want. :-p

We tell our tanks to use the first stun for darkness (if he does it, sometimes with fast dps he won't do it) or at approximately 70-75% remaining HP.

Then stun lock him with the remaining two stuns beginning at 25%. If no one has stunned and dps is not brain dead then you should be able to get him down no problems.

[i]As a disclaimer I would like to also mention that since I'm a Warrior I do not do this personally, so it may be slightly different then what our Paladin actually does. This is what he has said that he does and we never died to dreadwash even with slow dps. Our group has pretty pathetic dps (usually around 180-220) but we never have any trouble getting him down.

I always rem that it's the 3rd ruin the ull get 6 sec then right as about that is gonna fall of stun again then once more once it's gone. If dps isn't quick enough there's not a lot u can do. I normally have a roh rdy and voke and hit it with that followed by sprits then cos. there burning it so quick it ain't worth trying to keep hate. Keeping it locked should be ur main focus.

I'm going to assume you meant to put CoS (for Circle of Scorn) instead of RoS since there isn't a PLD/WAR ability with that acronym.

Quote:

---

Originally Posted by LeoLeoLeo

On the first mageadd I build up with the first two moves of the RoH combo on Levi's tale, and then on mage - RoH - RoS - FB - SW - SB - stun - FB - stun - SB - stun

On the second I start with provoke - shield lob - RoS - FB - sw - SB - stun - FB - stun

---

I wouldn't go with a rotation mainly because the trigger for his dreadstorm cast (which is the dangerous one that can't be stunterrupted) is based upon his hp as well as time (much like Levi's phases). It'll start casting dreadstorm either after darkness (~10 seconds after spawn) or as soon as it hits 80% (it will finish the action it's currently performing but will cast as soon as that's over).

Which trigger you have to react to depends entirely upon your group's DPS (in this case, initial burst DPS) so you should try and figure out how much damage it's likely to take within the next GCD. You can pretty much always get off Lob>FB>SB; with good DPS, you won't be able to get in the RoH. If you're not sure if you should attack, don't. Tank DPS isn't substantial, and stunning the add is way more important than getting in an extra 300-400 damage.

The second interrupt is best used right as your first stun is running out since the add is generally still in its "use dreadstorm asap" phase. The third should be held in reserve to interrupt dreadwash since it only lasts 1 second so it's only good for the interrupt. If the add isn't dead by the time you get that third stun it, you've basically got bad DPS (often, this means that you had one or more DPS ignoring the add).

The only way that a PLD can fail at stunlocking is if the add gets off dreadstorm or dreadwash before your third stun. If the add gets off a cast otherwise, it was your DPS that failed.

You should be on the head side waiting for the caster add.

Fast blade the tail then run to the head side. Swift blade, spirits within, halone, CoS, fast, swift, bash, fast, bash, bash.

You want him locked down with no movement. With SEs delayed aggro system you want to be standing where he pops instead of range pulling him.

For the 2nd caster add I use tempered will before the deck slam so I can be running towards the add and have him locked in place while everyone else is still sliding.

well after 120 runs here my rotation:

when i play with my tank-buddy WAR - i either take the add to the middle or if it spawns at head let the WAR take it - WAR position at edge so that head won't hurt other ppl

(depents on dps FoF) -> Provoke -> (SL)/RoH (position to MT additional dps) -> CoS -> Fracture/FB if time -> 6sec stun -> SW -> 3sec stun -> 1sec stun (by then it should be down OR start dps as much you can)

ADD: does always 1. Ruin 2. Ruin 3. Darkness
be sure to stun first time after darkness or 75/80%!

priority to stun then dps
i failed few times cuz dps was low and i tough >1 skill between stuns will work come on< might result cuz of lag or GCD miss calculation that 'DEADSTORM' is casted which is UNSTUNABLE~ better play save

if by any chance dps is that low that you run out of stuns and he does cast something position yorself further in the middel
1 cast can still be fine just make sure to dodge when your run from divebomb etc.

ty all for alot of advise! xD

too bad PSN maintenance wont let me back in.. ugh

For me i don't stunlock the Mage Adds I just use "Shield Bash" on one move. Dread Wash is the only thing I need to stun dreadpool is unstunnable you can't do nothing able beside position it to side that no can't hit by it. It's DPS job is too kill as fast you can or not the 2nd Dreadpool will mess you up you can't stun Dread Wash. But i get the mage I just use RoH then RoH combo.

Quote:

---

Originally Posted by KristianFortNox

dreadpool is unstunnable you can't do nothing able beside position it to side that no can't hit by it.

---

You stunlock the add so that it never has a chance to cast it. You can't stunterrupt the cast, but you can prevent it from casting it in the first place (and, in fact, if you stun it long enough that your DPS push it into a separate health bracker, its AI changes the priority such that it delays the cast further). If you're only stunning the spell that can be stunterrupted, you're doing it wrong and putting your group at much greater risk than you need to.

@Kitru

Sadly enough people said that and they all fail. All Paladin that I see that did that what you said and failed. Maybe you're right it can be stop but I never seen a successful one. The only way you can Delay Dreadpool if the White Mage use Fluid Aura even then that has chance of missing because the accuracy can be low. Beside there is no right away of tanking a lot of people tank different I am the people tank Levi EX different. I was giving my two cent about the matter. Me and you can disagree how we can tank Mage ADD but me and you can agree that it's need be killed quickly as possible

Since its mentioned - what is the prefered accuracy for a paladin on Levi EX, if it matters at all?

Dragoon Feint/BLm Lethargy can buy you a bit more killing time.

Quote:

---

Originally Posted by LeoLeoLeo

Since its mentioned - what is the prefered accuracy for a paladin on Levi EX, if it matters at all?

---

I'm not sure for PLD since it may be lower if you're on the Tail + adds, but I've had misses on the Head as WAR with ~470; currently no noticeable misses at 483+.

If the add isn't dead after the 10 seconds a PLD can keep it stunlocked, he has done all he can. At this point if the add begins casting Dreadstorm, the WHM can Fluid Aura or the WAR can Holmgang to interrupt the cast. If the WAR does Holmgang, the rest of the party has to move out of Leviathan's head LoS or they will get Dread Tided which will oneshot anyone who isn't a DRG. If the add is still not dead, you need to get better DPS.

Quote:

---

Originally Posted by KristianFortNox

The only way you can Delay Dreadpool if the White Mage use Fluid Aura even then that has chance of missing because the accuracy can be low.

---

The only ways to *interrupt* the fear patch cast is with a knockback or pull effect (Fluid Aura, Garuda push, Holmgang). You can delay it exactly as I described via stunning. If people are saying that they're doing what I'm talking about and failing, it's because they're not doing it right. I have farmed the living hell out of Leviathan and that's exactly how it works; the only time I *ever* see a fear patch is when the DPS sucks so bad that the add isn't dead by the time I've stunned it for the third time.

If the fear patch gets placed before you've gotten all 3 of your stuns in, you're failing as a tank. If you honestly think that the proper strategy for dealing with the fear patch is finding a nice, out of the way place to place it, it's because you suck as a tank.

I stun once as soon as I get it, then twice... then I wait for dreadstorm to almost finish casting and stun again (it will always cast storm after 50%). That gives you almost an extra 3 seconds of dps time. If it starts casting dreadpool a whm will fluid aura as an emergency move (with lowered acc that's not 100%), but it shouldn't get to that point. Dreadstorm IS stunnable. Then again I haven't done Levi since I got my tank mount a long time ago so things might have changed.