LB 3.1 changes are unfair to established teams.

[Shai]

I'd like to add since almost everyone seems to be reading it wrong ...

This only affects content you must queue as a team.
Anything you can queue solo in the DF for (which is practically everything listed in this thread) does not use this LB change rule.

Can anyone name a dungeon or trial you must form a group before entering?
If it is legitimately not including Raids, the only thing I can think of is Thordan.
Everything else you can queue solo (as of 3.1).

If it does include Raids (though that isn't stated) this only applies to Thordan and Savage.
Everything else you can queue solo.

If people actually read and comprehended the words written, rather than inferring things that weren't written, we'd have way less panic outbursts during patches. Just read what it says and then ask yourself how this even effects you. What pre-made team strategies could you possibly have for content you've never even done? I'm pretty sure it can't possibly include a LB since it's not out until tomorrow.

[BrodyCobalt]

It's pretty likely that King Thordan strategies will at least include a limit break, it's not unreasonable to be concerned about it. Being as these changes were likely targeted at end game raids to discourage single healer/single tank strategies, it's not unreasonable to think they will affect Alexander Savage as well, even though it's arbitrarily not classed as a trial.

These instances encompass the hardest content in the game, and generally requires the concerted effort of a static raid team to beat, hence the concern for teams that were established with three ranged players before this change was announced.

I'm glad the devs have responded to this issue. Delaying the changes to 3.2 and announcing them in advance will at least allow teams time to adjust their composition if needed. Thanks for the update, Zhexos.

[Shai]

Actually I was just reading in the other thread that the JP translation does indicate Alex (Savage) [and thus Raid content] is included in the list of content this affects, so the TC has a valid complaint. Still the only things this change affects (as I mentioned) are Savage and Thordan.

My point about Thordan is -there is no strategy yet- so if the LB factors into it then you can create the necessary team adjustments to clear it. You can't whine that this change affects "your strategy and team setup" for content that doesn't exist yet. However, that said, it does (apparently) affect Savage. I meant to put in my post "It wouldn't be the first time the patch notes were inaccurate, but we have to take it at face value" but opted not to say that.

Apparently, they are inaccurate and Savage teams will in fact be affected by this change. That is a bummer.

[BrodyCobalt]

People already do have team setups for Thordan though, in that they have static raid groups where each member has a favored job. If my team had three ranged DPS players, i'd feel bummed telling one of the casters they have to switch to melee DPS all of the sudden for Thordan, especially if said players don't enjoy or haven't leveled a melee DPS.

This would be less of an issue if the changes had been announced in advance, but we learned about them only a few days before the patch came out, which isn't enough time for someone to get a new job to 60, gear it and learn to play it in a worst case scenario.

Fortunately it's all a null issue for now being as we'll probably get hotfixed within a day or two. We'll have to see what the 3.2 changes will look like specifically before we can accomplish any more rabble rousing.

[Risvertasashi]

Then LB wouldn't fill in Alliance Raids like Void Ark lol

I'd assume they would keep this "feature" for content that is not solo queued, as it is now.

[Kaiser-Ace]

Hey everyone,

During the Japanese patch note reading, Yoshi-P mentioned that there has been a lot of feedback since the release of the preliminary patch notes, and he has been discussing this with the development team. As a result, they have decided to remove this feature and revert the system back to how it was originally. This will be done in a hotfix as early as possible.

This feature was originally intended to be added to allow more players with different jobs to be able to participate in end-game content, as well as keep the job setup to 2 tanks, 2 healers, and 4 DPS. However, they are aware that there are still many groups challenging Alexander (Savage) with their current groups, and also know how difficult it is to currently make a group for this content. Due to this, they will be fleshing out the feature a bit more, and plan to add it back in Patch 3.2.

We apologize for any issues this may cause your groups and ask you to please wait patiently until the hotfix for this to be reverted back.

It wasn't all that bad, the only real issue I saw was that "Ranged" and "Caster" classes (Who have two different Limit Breaks) were under the same category. That seemed to be the majority of the backlash I was seeing.

[Alcide]

This feature was originally intended to be added to allow more players with different jobs to be able to participate in end-game content, as well as keep the job setup to 2 tanks, 2 healers, and 4 DPS.

This is bs, we all know 2 melee 1 support 1 caster is already the most common setup, this was totally unnecessary to begin with.
The only reason to implement such a stupid feature is so that when you guys develop a content that doesn't work for a 3 ranged/melee party you can say "well you guys chose to gimp yourselves with a composition we don't approve so that's on you".

[Teiren]

It wasn't all that bad, the only real issue I saw was that "Ranged" and "Caster" classes (Who have two different Limit Breaks) were under the same category. That seemed to be the majority of the backlash I was seeing.

Yeah, I agree. Although to me it's not so much that their Limit Breaks are different. It's that Ranged and Caster really are different roles from my perspective. Ranged does a little less DPS than Caster for a little bit of support and deals with movement more easily, while Caster is about dealing some of the best AoE damage and can DPS forever unlike a TP user. To me those perks set BRD & MCH and BLM & SMN well apart from each other. It's very worrying and distressing to see the devs honestly thinking all 4 of those Jobs are the same role and considered treating them as such.

[SummonerSenah]

I feel like this is a poor bandaid over the problem that the raid design is problematic to begin with. So now we're going to have people switching jobs to maybe something they don't like as much just to avoid a penalty that really shouldn't exist.

[Zhexos]

Greetings,

Thanks for your patience as the development team reworked the changes to the Limit Break charge rate.

In Patch 3.2, we're planning to make the following adjustments to the rate in which the Limit Break gauge accumulates.

Content which utilizes the Duty Finder matching.

Regardless of the party composition, the accumulation rate will always be constant.

Content which does not utilize the Duty Finder matching.
(Content such as Alexander: Midas (Savage))

Under the below conditions, the Limit Break gauge will accumulate at a slower rate:

• When there are 3 or more Tank class/jobs.
• When there are 5 or more DPS class/jobs.
• When there are 3 or more Healer class/jobs.
• When there are 2 or more of the same class/jobs.