MNK Meteodrive - working as intended? (animation lock vulnerability window)

[Raikai]

So... I'm wondering, Meteodrive stuns the target through the duration of the animation, which is great (and looks great tbh!), but I could realize that the Monk is ALSO, in practice, stunned through the animation lock.

That makes really bad to use Meteodrive between a cluster of opponents to finish someone, as you can be literally killed through the duration of the animation lock, and I was wondering if that side effect was intended.

Hopefully is something they can address in the next balancing patch, because it makes it a bit frustrating at times.

[KouYanagi]

So... I'm wondering, Meteodrive stuns the target through the duration of the animation, which is great (and looks great tbh!), but I could realize that the Monk is ALSO, in practice, stunned through the animation lock.

That makes really bad to use Meteodrive between a cluster of opponents to finish someone, as you can be literally killed through the duration of the animation lock, and I was wondering if that side effect was intended.

Hopefully is something they can address in the next balancing patch, because it makes it a bit frustrating at times.

Yeah but its a little bit of a dilemma because vice versa the victim is stuck unable to do anything as well. So do we want Meteodrive to be fast so that we can survive and assassinate or slow so that our team can follow up?

[Raikai]

Yeah but its a little bit of a dilemma because vice versa the victim is stuck unable to do anything as well. So do we want Meteodrive to be fast so that we can survive and assassinate or slow so that our team can follow up?

As the poster above this one mentioned, there are other jobs that achieve similar effects but without the animation lock. Monk plays good, but it falls on the backseat when compared to other jobs, so I'm asking if this "complexity threshold" of having to plan Meteodrive around being stunned as well is really intentional or just an overlook.

[KageTokage]

Animation/OGCD delays are a definite problem in PvP, and some jobs can follow up with their LBs to secure kills much more effectively then others.

I think they really ought to look into speeding things up and normalizing the delays across the board.

[Enjuden]

So... I'm wondering, Meteodrive stuns the target through the duration of the animation, which is great (and looks great tbh!), but I could realize that the Monk is ALSO, in practice, stunned through the animation lock.

That makes really bad to use Meteodrive between a cluster of opponents to finish someone, as you can be literally killed through the duration of the animation lock, and I was wondering if that side effect was intended.

Hopefully is something they can address in the next balancing patch, because it makes it a bit frustrating at times.

Considering Ninja does the same thing and can't be killed during it, it's likely unintended.

Edit: Guess it's intended. Nin is susceptible to the same.

[Bureda]

Considering Ninja does the same thing and can't be killed during it, it's likely unintended.

Incorrect. You can stun a ninja or polymorph mid animation to stop the lb. If a NIN dies before the animation fully finishes, the effect won't go through but the LB bar gets used still.

[Enjuden]

Incorrect. You can stun a ninja or polymorph mid animation to stop the lb. If a NIN dies before the animation fully finishes, the effect won't go through but the LB bar gets used still.

Oh, well then. That's good to know. Thank you.

[RyuDragnier]

Considering Ninja does the same thing and can't be killed during it, it's likely unintended.

No, NIN can be killed during LB. It has happened to me multiple times, and if the NIN is killed before the animation is done, their target lives and the LB is cancelled.

[KageTokage]

I don't think you can actually stop the damage from LBs short of straight up killing the player before it registers because every instance of my slow LBs being "interrupted" by CC has just caused the damage to register immediately instead of at the end of the animation.

[Bureda]

I don't think you can actually stop the damage from LBs short of straight up killing the player before it registers because every instance of my slow LBs being "interrupted" by CC has just caused the damage to register immediately instead of at the end of the animation.

Damage and execute can be fully denied. There's a threshold in the animation for it to pass before fully registering. I've had plenty of executes be denied.