The new upcoming no duplicate job requirement setting

[Mynaria]

Is this really necessary? Having an earlier lb3 to clear content is not a necessity and I don't think content was intended to be balanced around this.

I understand that people can already set their parties with the above restrictions and more with just a bit of effort, but this only really seems like a QoL change for speed/parse runs. I'm just worried that it will lead to the widespread mentality of people unnecessarily checking the setting because of a one button press, and making it more difficult for people to find parties overall.

Am I overly concerned or alone in this?

[KDSilver]

It won't change thing that much.
People who already don't want double job in their party won't need to write "no double" in the pf description.
That's more a QoL.

As for LB charging faster. It's not "necessary", indeed. But it's a nice little boost having a lb3 + eventually a lb1 or 2 if the damage are lacking a bit (cause every pf groups aren't the same).

[Ursa_Vonfiebryd]

Is this really necessary? Having an earlier lb3 to clear content is not a necessity and I don't think content was intended to be balanced around this.

I understand that people can already set their parties with the above restrictions and more with just a bit of effort, but this only really seems like a QoL change for speed/parse runs. I'm just worried that it will lead to the widespread mentality of people unnecessarily checking the setting because of a one button press, and making it more difficult for people to find parties overall.

Am I overly concerned or alone in this?

As long as its just a PF setting and not a DF setting, I'm ok with it. No 'dupes' has been a thing since Stormblood and is generally understood as a best practice for high end but this will make it so whoever set the PF doesn't have to repeat themselves ad infinitum. I don't see it being an issue any more than it already has been.

[SamRF]

As long as its just a PF setting and not a DF setting, I'm ok with it. No 'dupes' has been a thing since Stormblood and is generally understood as a best practice for high end but this will make it so whoever set the PF doesn't have to repeat themselves ad infinitum. I don't see it being an issue any more than it already has been.

As a Bard I wish there was a setting for that in duty finder as well, for your own job only, unless they do something about double Bard (e.g. make the passive song buff stackable in a way).

[Fynlar]

SE enforced this themselves by instating the slower LB thing. Until/if they were to back out on that, this option should exist.

Loads of groups already did the "no dupes" thing as it is; this will just simplify the process for party leaders and prevent people who don't pay any attention to who's already in a PF group from being able to join as a dupe.

[Xatsh]

Do not see an issue as long as it is not forced on ppl.

Same thing as loot master setting, minimum item level and all that.

[Liam_Harper]

I doubt it'll make a difference. You can already specify "no doubles" in the group description or lock the last few spots to specific roles.

I always found "no doubles" amusing in EX groups though. These groups, without fail, never take advantage of their earlier LB3. They just save it for the healer and melee lb at >10% like everyone else. It feels like they're just repeating something they saw a Savage progression group mention, in the assumption it's more "pro", without even knowing how it works.

[Mynaria]

Thanks all for the responses, it just rubbed me the wrong way, and made me think of the PFs that pull absurd restrictions on even practice/clear parties. I felt like it would give justification to some people who ran with unrestricted classes normally, to choose otherwise because the option would then exist.

As for LB charging faster. It's not "necessary", indeed. But it's a nice little boost having a lb3 + eventually a lb1 or 2 if the damage are lacking a bit (cause every pf groups aren't the same).

I always found "no doubles" amusing in EX groups though. These groups, without fail, never take advantage of their earlier LB3. They just save it for the healer and melee lb at >10% like everyone else. It feels like they're just repeating something they saw a Savage progression group mention, in the assumption it's more "pro", without even knowing how it works.

Yep, optimally, i'd like to drop melee lb3 as soon as an opportunity arises to have an extra lb when everyone is healthy, but i've been scolded before for doing so in the past in savage, ex, and 24 man runs when everyone was fine, and then suddenly multiple people die. So I use it tentatively now after the blame.

As a Bard I wish there was a setting for that in duty finder as well, for your own job only, unless they do something about double Bard (e.g. make the passive song buff stackable in a way).

I didn't really think about double BRD/DNC, but that feels more of a class balancing issue that SE needs to work on. Perhaps just give a diminishing returns % effect to duplicate buffs used after the initial cast/duration of the original?

[Liam_Harper]

Yep, optimally, i'd like to drop melee lb3 as soon as an opportunity arises to have an extra lb when everyone is healthy, but i've been scolded before for doing so in the past in savage, ex, and 24 man runs when everyone was fine, and then suddenly multiple people die. So I use it tentatively now after the blame.

Honestly, I'll always save it for the healer and melee lb3 at >10%, unless it's progression and we're perfect on mechanics but really scraping enrage.

I've seen the most amazing groups in all sorts of content, perfect smooth runs that you'd never dream could wipe, suddenly fall to pieces on a mechanic midway and that healer lb3 saves the wipe. If I'd popped the lb3 we'd be starting over. In most cases the early melee lb3 doesn't add much unless your group really cut enrage close and even a healer lb3 for 2 dps can be a gain over it due to no weakness.

[Freyt]

Necessary? No. That's why it's an option.