Interrupted LBs into oblivion

[Valence]

Some of you may remember that before 7.1 hit, it was possible, albeit extremely rare, to completely stun or lock someone out of their LB while them still spending it without any effect. For example, it was possible to stun a Zantetsuken at the right moment and have it spend the LB bar while doing literally nothing. A bit more rare, it was also possible to do it on a MCH LB, especially with miracle of nature. In those cases, it was very rare because of the window for the stun to land was extremely tiny, we're probably speaking in literal microseconds. It's also possible that those LBs had bad interactions going on the side with abilities like Miracle of Nature, I don't know.

Well, you'll be pleased to hear it, after the 7.1 changes and the hit registration rework.. this is still happening! Had my first Spite interrupted by a Miracle of Nature today. Even more annoying than before because it's just pure luck with the crowd control delays now. Not that it was any less pure luck before, but still.

Can something be done about this? Is this even intended or do we actually need to open bug reports? There is no way on earth something like this is actually designed to happen... right?

[Mawlzy]

Some of you may remember that before 7.1 hit, it was possible, albeit extremely rare, to completely stun or lock someone out of their LB while them still spending it without any effect. For example, it was possible to stun a Zantetsuken at the right moment and have it spend the LB bar while doing literally nothing. A bit more rare, it was also possible to do it on a MCH LB, especially with miracle of nature. In those cases, it was very rare because of the window for the stun to land was extremely tiny, we're probably speaking in literal microseconds. It's also possible that those LBs had bad interactions going on the side with abilities like Miracle of Nature, I don't know.

Well, you'll be pleased to hear it, after the 7.1 changes and the hit registration rework.. this is still happening! Had my first Spite interrupted by a Miracle of Nature today. Even more annoying than before because it's just pure luck with the crowd control delays now. Not that it was any less pure luck before, but still.

Can something be done about this? Is this even intended or do we actually need to open bug reports? There is no way on earth something like this is actually designed to happen... right?

Are there not multiple skills that can go on CD having "activated but not activated"? The added chaos of FL often makes it difficult to know what has happened, and I admit I'm not interested enough at this point to sift through battle logs. And while I am no longer on Discord, I imagine there are a whole host of timing/interrupt oddities that are being exploited by the professionals.

[Loggos]

This sounds incredibly aggravating.

The way LBs are handled is a source of endless frustration for me. Not only do some LBs take so long that casting them anywhere else than in Narnia is really just suicide with special effects, but if you miraculously survive your lengthy animation but then die at the last millisecond your entire LB is canceled and you still lose your entire LB bar without reaping a single effect.

In some cases the risk-reward balance is completely whack.

I'm not advocating for them to remove strategic burst denial but it should still be fair. If the enemy team is supposed to have a reasonable chance to outplay/cancel my LB then I should also have a reasonable chance to cast it at the site of the battle without turning into a helpless piñata for the enemy team.

Are there not multiple skills that can go on CD having "activated but not activated"? The added chaos of FL often makes it difficult to know what has happened, and I admit I'm not interested enough at this point to sift through battle logs. And while I am no longer on Discord, I imagine there are a whole host of timing/interrupt oddities that are being exploited by the professionals.

Yeah it happens to normal skills too. Very often your animation will play out fully even though the effect is canceled but since the animation played out it also counts as the skill having been used. The result: Cooldown. It happens when the enemy dies to somebody else before you finish your cast and also when you die. I don't know if it also happens when you are stunned/silenced.

[Mawlzy]

Yeah it happens to normal skills too. Very often your animation will play out fully even though the effect is canceled but since the animation played out it also counts as the skill having been used. The result: Cooldown. It happens when the enemy dies to somebody else before you finish your cast and also when you die. I don't know if it also happens when you are stunned/silenced.

This is actually the most irritating for me and is a major flaw in the hit detection IMO. Actually interested how the padders handle this.

Like from the point of view of trying to win, it's natural to target (haha "target") enemies with dropping health bars. If the padding goal of the day is to maximize damage, you'll go for enemies at full health.

For the rest of us, it means that optimizing damage application and K/A involves predicting which enemies will be at fractional health when your attack actually lands, in a FL skirmish that may involve 40+ players.

This is, of course, impossible.

[Loggos]

i

For the rest of us, it means that optimizing damage application and K/A involves predicting which enemies will be at fractional health when your attack actually lands, in a FL skirmish that may involve 40+ players.

This is, of course, impossible.

This already drives me crazy in CC and there it's only five people. FL sounds like an absolute headache.

[Mawlzy]

This already drives me crazy in CC and there it's only five people. FL sounds like an absolute headache.

One consequence is that AoEs rule over single-target stuff, simply because you'll probably hit something that's still alive.

[Aco505]

The DRG LB has always had the risk of automatically failing if you went up in the air with enough DoTs or at the right snap shot time. You die while flying and lose the entire extremely slow charging bar (particularly in FLs) for an LB that has plenty of counters.

You can also be charmed by a DNC or, worse, feared by a RPR, thus losing control of your movement and being unable to land prematurely.

Since this has always been a thing and that it could be understood as another layer of skill, that of being able to know when to use it so it's not cancelled, I'm sure the developers consider it working as intended.

[Mawlzy]

The DRG LB has always had the risk of automatically failing if you went up in the air with enough DoTs or at the right snap shot time. You die while flying and lose the entire extremely slow charging bar (particularly in FLs) for an LB that has plenty of counters.

You can also be charmed by a DNC or, worse, feared by a RPR, thus losing control of your movement and being unable to land prematurely.

Since this has always been a thing and that it could be understood as another layer of skill, that of being able to know when to use it so it's not cancelled, I'm sure the developers consider it working as intended.

Not disagreeing, but that particular phrase has a spotty history in FL (PLD for example).

[Aco505]

Not disagreeing, but that particular phrase has a spotty history in FL (PLD for example).

I doubt that PLDs removing a fundamental mechanic from point capping was intended.

Don't get me wrong, I'd like for the DRG LB to make me invulnerable while in the air, at least to CC, but since it works the way it does I must be mindful when executing it.

[Mawlzy]

I doubt that PLDs removing a fundamental mechanic from point capping was intended.

Don't get me wrong, I'd like for the DRG LB to make me invulnerable while in the air, at least to CC, but since it works the way it does I must be mindful when executing it.

Seem to recall devs claimed it was working as intended a few months before they fixed it.

But sure, working around certain oddities can be okay. Still not a fan of the general mushiness though.