Critical bug on Levi EX DF

Leviathan kept wiping us after the first tidal wave even when we had 30+ and activated converter. I know contents are being released on limited time but critical bugs like these cannot occur. What's the point of releasing contents if the players can't play it? :mad: Please fix it. Thank you.

Post in bugs report forum, kthxbai

Quote:

---

Originally Posted by Zelas

Thanks for the heads-up, but you should also post this in the bugs report forum so it can be acted on quicker :)

---

ftfy /10char

Did you activate the converter early enough? Because Leviathan will kill you if the converter animation isn't done when Leviathan starts speaking. It has always been this way.

if levi flying in circle around you and the shield not up, then it too late, shield has to be activate right after the single drive. the damage is calculate way before the actual animation hit you.

I was expecting this to be something like "DF won't match every group with a smn/blm because this fight is IMPOSSIBRU without meteor LB". Glad to see I was wrong.

But yes, maybe your timing is wrong. Are you pulling the lever during/just after he uses spinning dive? Or are you waiting longer for it?

Just did Levi Ex, i do believe it is bugged, same thing just happened, ran this prolly a hundred times before, tiggered switch at 27-30%+ right after dive and killing party like we never hit the switch at all, tiggered switch earlier 2nd time, even it didnt have enough % tank should of survived but they didnt, so ya something is up with it :X

Quote:

---

Originally Posted by Zelas

kthxbai

---

we truly live in a horrific time.

Just tried levi ex and it is indeed bugged.

As others have said, you absolutely MUST trigger the converter right as spinning dive goes off. Aka, if he does his little speech before the converter has been activated, it's too late. However, I have encountered situations where we had enough conversion AND we triggered it way before we needed to and we all still died (as though the shield did not register at all). This bug is incredibly rare, and before 2.28 I only encountered it once out of many, many farming runs. I haven't done the fight in 2.28 yet, so I'm not sure if this bug is more common. At the time, I assumed we had all just hit a lag spike or something.