SE fix limitbreak and make the melee lb avoidable!

[Redfame]

Melee LB: Sometime it have a range for -20y to 20 y (back-front) in attantion to the casttime.
all dmg LB's: Sometime the dmg comes after the animation, that means---> casttime is over but if you die between the animation and casttime, so lb was like never used = 0 dmg.
Melee LB: works in all directions??!! what a shit.

https://www.youtube.com/watch?v=rgTGoFV3B3c
its not a conection prob.
https://gyazo.com/08129502c2c4790fd22c432cf85820fc

[seraphuslol]

What do you mean "works in all directions"?

Like they have the setting to automatically face targets enabled? I think that's intended.

[Dotsusama]

The added leeway is probably there to make up for latency, positioning of characters on the client side versus the server, and the animation lock. I've been the victim enough to know that there are very rare circumstances where I can avoid the damage completely; like if someone casts the LB the instant I hit Attunement, receive a shield, or either I get pushed back by some other ability, or the melee character is stunned.

I still think this is balanced and working fine, since melee jobs generally have range as their largest issue, and having something that still goes off and doesn't waste their adrenaline if it misses or you dodge out of the way makes up for that shortcoming. In other words, this is working as intended. Ranged LB have a beam or large area of effect, to make up for the lower damage and distance. Melee LB is, well:

[UshiMushi]

The damage is dealt when the melee lb animation begins. That mixed with latency is why the melee lb acts in such an odd manner. The alternative of making the damage happen after the animation would make melee lb almost useless. At least this is my understanding on how melee lb works.

As for caster that's almost entirely lag time from client and server and/or processing. Just because you have a good ping to a server near your geographical location does not necessarily imply a good connection to the games server; especially the case oof PvP when a lot is happening.

It's dumb, It feels like you get wronged. But the issues are almost entirely latency.

And the main reason for writing this is do I can say this: Taru you rat I'm the hero.

[Stupiduglytaru]

Lolol sushi do you need me to come to odin so I can rescue you at all times?

[xxczx]

The main people that have been shafted with LBs is BRD/MCH.

Let us pray for those silly avoidable straight lines.

[seraphuslol]

I personally think the limit break gauges should be like in pvp period.

It would be cool for people to be able to limit break alone instead of always just one person per full party.

[Dimitrii]

Lol funny how this works. No one cared about the mechanics of melee limit break in slaughter where it was a casters paradise. Only ones shafted are BRD/MCH and as such are the only ones that can complain as others have said, their limit break is absolutely pathetic and questionable whether it's even worth using given how fast they are killed after they use it and miss (though I think they fixed it's unusually long animation lock now so maybe it's not as bad).

Anyway it only takes me one fending accessory, food, and the tank vitality buff to survive a melee lb as a drg because the majority of the melee in a seize don't know how to limit break anyway. They will attempt to limit break me at full hp without making any attempt to damage me before hand and expect that limit break to kill me on its own. Even worse some don\\'t even stun and fetter ward beforehand allowing u to interrupt the lb before it even goes off.

[Darwyn_Ulondarr]

Melee LB is very avoidable already. Problem exists between keyboard and chair.

[Lorielle]

Face Target is a thing.