I don't think SE consider D4 RDM in the mechanics in this patch

[AmiableApkallu]

But it's an independent thing from what I want, which is classes not based on the static rotation archetype.

So long as encounters are centered around static timelines, the only thing such a class design brings to the table is, "well, I guess I stunk this run because my class's RNG didn't favor me." See also: The evolution of any class/job in FFXIV who's earlier designs featured RNG elements. Because, as I said before:

SE's problem starts with the fact that they're fixated on a particular, singular style of encounter design.

You want to move away from the static rotation archetype? Hallelujah.

But by the evidence available to us, it seems clear that SE's first problem is encounter design, because that's all but their stated reason for smooshing every class/job into a static rotation. And the general praise for PvP proves the point that less static encounter design is a good thing, even in the presence of job kits with little or no RNG.

[Absurdity]

I don't see a solution proposal, I see someone wanting to add complexity to try solve a problem with fight complexity by shifting it into the job they're playing. If your goal were to actually reduce complexity or keep it equal while improving red mage potential, you'd simply shift damage from the combo into the filler, including overhead for the burst potential reduced. Tuhdaaah, same damage in uptime fights, improved damage in disengagement fights. Increased damage in fights with breaks like Ultimates, too!

It's the exact opposite though, this doesn't add complexity. You're turning a currently tricky problem "Trying to execute your melee combo with no safe spot near the boss" into "Lol just ranged combo".
But yes, at that point just remove the actual melee combo from rdm because if potency on both is equal then "Lol just ranged combo" becomes the default anyway.

[Carighan]

It's the exact opposite though, this doesn't add complexity. You're turning a currently tricky problem "Trying to execute your melee combo with no safe spot near the boss" into "Lol just ranged combo".
But yes, at that point just remove the actual melee combo from rdm because if potency on both is equal then "Lol just ranged combo" becomes the default anyway.

That was my point, exactly. If it's just about "Oh I cannot melee at the right times and clearly this is unfair and not okay" then the correct solution is to eliminate or factually-eliminate the melee combo (an opinion I do not share, if that wasn't obvious enough). Adding an extra ranged combo is absolutely pointless, because either way you're just standing at range, might as well just remove the melee combo entirely then?

[Voryn]

Is it a problem specific only to that spot, or is it also problematic with other ranged spots?

The mechanic in question has four players (decided by the strategy) tethered to the walls while the boss is in the middle. A tether deals damage over time, but stretching it will make the player take heavier damage. So usually the two healers and the two ranged DPS are hugging the walls and can’t get closer without taking very heavy damage.

In D4 rdm is not able to melee combo in phase 3 tether, the only thing I can do is AOE combo. The burst cannot delay, because of tether stuff.

Since the adds spawn at the walls around that time and they do nothing for a while, at the start of the burst window as RDM you have the option of using Manafication or 50 meter to hit your nearest add with your melee combo and then hitting the boss with the three finishers. However you’d have to do the math to see if this is worth it. It does more potency to the boss during this burst window if you just used your usual single target attacks during this time, lets you use Prefulgence during buffs if Manafication was used, and gives you a guaranteed proc if you don’t have them already, but spends 50 meter or a Manafication that could have been otherwise fully spent on hitting the boss if it was done at another time. Damaging the adds is unnecessary for this mechanic.

After that the adds will start moving to the tanks to attack them, and then you all you can do is your usual ranged attacks on the boss. Unless you have an Acceleration to spare (or have a Swiftcast and are willing to spend it there) for using Verthunder/aero and Grand Impact.

[Arohk]

When a job is particularly bad in some fight, just dont play it then.

[NightHour]

I assume by D4 you mean R2? Sorry I retired from savage so I'm not familiar enough with M7S.
Is it a problem specific only to that spot, or is it also problematic with other ranged spots?

NA and JP use D1 D2 D3 D4 T1 T2 H1 H2 instead of M1 M2 R1 R2 MT OT H1 H2

[Carighan]

When a job is particularly bad in some fight, just dont play it then.

Exactly this. I want classes to be good at different things, and I want (some) fights to be brutally difficult.

This naturally means these fights will need to be balanced to only work with a particular subset of classes. So long as fights exist where all kinds of classes excel, that's more than fine with me. Or maybe even areas of fights.

[Shadyshawty]

it's totally possible to perform perfectly as a redmage, I'm sorry but it's a question of skill really

[Nero-Voidstails]

you mean a job isn't balanced around a fight!! gonna fix that and remove it! obviously we cannot have a fight balanced around a job nah nah nah can't have that

[luca20]

As someone who progged most of M7S as RDM in the R2/D4 spot and changed to PCT as soon as I could, I feel the problem is not RDM or fight design, the problem is the job balancing team hard on on melees. If RDM was competitive with a melee for damage then this wouldnt be an issue because you could easily join parties as the flex dps and take the melee spot. This is not only theorical but something you see often in ultis. I progged most of UCoB as fake melee RDM and have seen it as well in DSR and FRU when it was current. But with how much better melees are than any job not called BLM makes it so that there's no flex dps spot, it's locked to a melee.