Interrupted LBs into oblivion

[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.