Required LB3 Fights Are Terrible And Bad

[SpitbreakFTW]

I just failed The Final Day fight TWICE because two different people disconnected midfight. Meaning we didn't have an LB3, meaning we died. Mandatory LB3 doesn't actually add anything to gameplay. It's a glorified Press X To Win Game quicktime event. All such a mechanic brings to the table is the ability to have the fight ruined by garbage netcode.

LB3 was always one final burst of damage to finish off a fight, or a healer's saving throw after everything went pear-shaped. And tank LB was always totally irrelevant. And that WORKED. Then they came along and fixed what wasn't broken by forcing Tank LB3, and now it's actually broken. Good job.

[TimotheusReed]

I honestly like the overall concept of a LB and I especially like it the most in the new Pvp mode.

I feel Square should rework the whole LB system and make it so everyone has their own individual LB gauge and every class has its own individual LB in PVE.
Also don't make PVE fights require LB3 anymore and make every class have their individual LB similar to Pvp. Also make it charge faster.

As a tank I almost never use my LB in PVE except for some fights where it is required. But in Pvp I use my LB all the time.

[Vidu]

While thos instances are frustrating I actually like having to use the tank LB3 once in a while - or rather: getting to use it once in a while. I'm probably a little biased here but as tank you're mostly not allowed to touch that button and having moments where you summon a giant shield to save your whole party can be pretty amazing. If it werent for that we might as well remove the tank LB alltogether.

...which, maybe we should - or think of something different. But until that happens I'll take getting to use it once in a while over not using it at all. Even if it comes with the occassional frustration because fights being unwinable if someone DCs.

[NekoMataMata]

While thos instances are frustrating I actually like having to use the tank LB3 once in a while - or rather: getting to use it once in a while. I'm probably a little biased here but as tank you're mostly not allowed to touch that button and having moments where you summon a giant shield to save your whole party can be pretty amazing. If it werent for that we might as well remove the tank LB alltogether.

...which, maybe we should - or think of something different. But until that happens I'll take getting to use it once in a while over not using it at all. Even if it comes with the occassional frustration because fights being unwinable if someone DCs.

Isn't that the whole problem? Tanks have no reason to use the LB normally, so maybe something else should be done. Make Tank LB actually useful outside of instances that are essentially crafted for the purpose of forcing it.

[Jeeqbit]

I prefer it when we find good times to use tank LB3 without being forced to, such as with Byakko, Garuda or the Ultima Weapon.

[Deveryn]

I agree with the idea of some forgiveness with losing party members for a moment.

I prefer it when we find good times to use tank LB3 without being forced to, such as with Byakko, Garuda or the Ultima Weapon.

Garuda? That fight where people don't pay attention to the plume they're not supposed to kill?

[Jeeqbit]

Garuda? That fight where people don't pay attention to the plume they're not supposed to kill?

That's right. They kill the spiny plume with their aoe, resulting in a wipe, but you can tank LB3 instead.

It might not have aged well in a time where we have Reprisal, a stat squish and a lot of changes to our stats, but I've got parties through with it multiple times.

[Avidria]

Alternatively they should change it so it doesn't vanish if someone disconnects and/or reconnects mid fight
Unsure if or how that could be done but it's always been incredibly annoying

[Avoidy]

They should just make it so that one dude disconnecting doesn't screw the whole party out of their Limit Break gauge.

[Xaphire]

There's nothing wrong with the mechanic of requiring tank LB to survive a mechanic. The issue is the bar resetting when a player disconnects. That should be changed.