Please stop inserting unbranching combos in new jobs

[Jokerz_93]

Soooo, if I’m correct,

DRk combos would be like: 111 111 111. 2 when you have to bloodspiller/quietus.
WAR would be 112 111 111 111 112. 3 when you have to Fell cleave and 4 when you have to Primal Rend.
PLD would be 111 222 4 111 222 4 111 222 4 333 (where 2 is Ato, 4 HS, 3 Confiteor combo)
GNB would be 111 2(5)2(5)2(5) (2(5) Continuation combo)

DRG would be 11111 22222
MCH would be 111 111 1111
And so on…

Really I’m not getting the point how condensing a simple 123 into a 111 could be better.
I main the last most busy jobs left in the game (DRK/GNB DRG AST) and there isn’t a real “button bloat” problem, just a skill issues problem (or ping issues that would be more understandable tbh).
If there are more OGCDs/GCDs in the game, it could be a better thing for sure but now? Nah, I don’t think it’s a good idea with these skills we have now.
Just my opinion tho.

[UkcsAlias]

Really I’m not getting the point how condensing a simple 123 into a 111 could be better.

If its only condensing and no extra branching its worse. But condensing makes 2 more buttons in easy reach for potential additional branches:
For example using just 3 buttons these can still be diffirent combos while keeping the same initiator.

Thats where condensing can be powerful. Here a simplistic example while not going for full variety:
123 is the default as we know it. Nothing even changes here. But as alternative combos you can have 132, 122 and 133. The 2nd button you pressed decides what the 2 and 3 button will be at the final step. Giving 4 potential branches to pick from.
But we can take it further, as we can also make double pressing the 1 cause a diffirent branch, and this then means a combo like 113 can exist. This is obviously a bit less clean, but effective.

But why stop at 3 button combos in this case? what if 1233 and 1322 are both the 4 button combos (where 1232 will have broken the combo and perform the weak 2)? And maybe other abilities can even branch into this? For example button 4 is a boost modifier button that at a variety of steps can boost the effects. 123, 1243, 132, 1432 can all become a combo then.

Ninja already shows such condensing system. Its not new in the game. And for ninja while the buttons are quickly to select an ability, for other jobs it doesnt have to.

And even then, it doesnt have to be a full set of combos. Even just 123 and 132 can be more than enough for branching. With the advantage of not requiring new buttons.

[Mikey_R]

Thats where condensing can be powerful. Here a simplistic example while not going for full variety:
123 is the default as we know it. Nothing even changes here. But as alternative combos you can have 132, 122 and 133. The 2nd button you pressed decides what the 2 and 3 button will be at the final step. Giving 4 potential branches to pick from.
But we can take it further, as we can also make double pressing the 1 cause a diffirent branch, and this then means a combo like 113 can exist. This is obviously a bit less clean, but effective.

Whilst the hypothetical is fine, what you then have to do is give each one a reason to exist. Why should I do 123 over 132 for example. Without duplicating, you have 6 possibilities (123, 132, 213, 231, 312, 321) and each one needs to have a reason to exist. So, let's try. One is going to be a pure damage, one a DoT, one a damage buff, maybe a debuff...maybe an oGCD makes one stronger, maybe go the Monk route and have one combo make the damage one stronger (in the same way DK makes BS stronger).

But now we have the issue of fitting it into a clean rotational loop. You have 18 GCDs, at 2.5 seconds, you get 24. Hm, maybe we have it so the combos proc a 4th GCD that changes based on what comes before. That gives an extra 6 GCDs making a clean 1 minute loop. Add some oGCDs here and there and voila, here is the baseline for every job if you want to do away with combos and have something more free flowing. But, wouldn't that make every job feel the same? Why yes it would.

And therein lies the problem. It would be fine for a single job, but you couldn't make all jobs do it, in the same way Monk has something different (you 'combo' your forms, you just choose which GCD to use in said form) but you wouldn't make EVERY job follow that framework otherwise, every job would be the same.

As to the topic at hand, I have no problems if they want to condense the buttons, just make it an option for people to turn on if they want to and no, just because they combine the buttons doesn't necessarily mean they will add something else to replace it.

[UkcsAlias]

Whilst the hypothetical is fine, what you then have to do is give each one a reason to exist. Why should I do 123 over 132 for example. Without duplicating, you have 6 possibilities (123, 132, 213, 231, 312, 321) and each one needs to have a reason to exist. So, let's try. One is going to be a pure damage, one a DoT, one a damage buff, maybe a debuff...maybe an oGCD makes one stronger, maybe go the Monk route and have one combo make the damage one stronger (in the same way DK makes BS stronger).

Not all need to exist. And as you already imagined, chains dont have to start at 1 either.
But for example this is possible:
123 is just the normal damage
But after pressing 1, 3 becomes a button that applies a self buff (+5% dps for 30s?), and allows 2 to be chained afterward, this 2 is then just the basic 2 again, so after this its a 3 again.
this gives 123 and 1323 as combos.

Now we dont have to stop here, as we can have all 1,2 and 3 as initiators for certain chains. But they arent required to exist.

We can for example also introduce a 11 chain where each consecutive 1 adds stack that allows a faster cast of for example 3, creating as combo: 113. And sure, the example i gave here is bad since it makes 113 compete with 123, but its to show a potential chaining system in a condensed situation.

Its up to the devs what they will use. But i generaly would focus on the case of: if a button is ment to be chained, but has no feature outside of that chain, its generaly worth to condense (make it the initiator for a diffirent chain).

[Shurrikhan]

Whilst the hypothetical is fine, what you then have to do is give each one a reason to exist. Why should I do 123 over 132 for example. Without duplicating, you have 6 possibilities (123, 132, 213, 231, 312, 321) and each one needs to have a reason to exist. So, let's try. One is going to be a pure damage, one a DoT, one a damage buff, maybe a debuff...maybe an oGCD makes one stronger, maybe go the Monk route and have one combo make the damage one stronger (in the same way DK makes BS stronger).

Ideally, this. Every key should ideally have a reason to exist at every step.

Though, that's also so far above what we have now that it's asking for divine quality while living in eradiated fecal waste. I'd therefore be content with every key having a reason to exist at almost every step, and at least a majority of steps giving every key a reason to exist.



Interesting to note, too, though, is that we can also differentiate even that ideal state with more dynamic combos.

At the moment, difference in "combos" is just how many forks they have and how often one can actually engage in them. SAM ST has 3 forks, available every 2-3 GCDs. DRG has 2, effectively available only 1 in 10 GCDs (though instead 1 in 5 GCDs in two-target combat). WAR and NIN ST have 2, available per 3 GCDs. GNB, DRK, and PLD each have just 1, which is effectively none / no decision-making around/regarding combo choice.

That's effectively just... a competition in how wasteful they can be.

By comparison, more dynamic combos could instead feature differences like:

• Synergies (Skill A has synergies with multiple follow-ups, perhaps at multiple steps, allowing for a differently advantaged combo from the paths leading through them) vs. Replacements (using Skill A vs. B for the opener literally changes what options come thereafter).
  
  
• Discrete Finisher[s] (you have a discrete key to fast-burst from the opener at resource cost, stop your combo short, or finish off an empowered combo) vs. Prepped Finishers (skill becomes a finisher once its prior use has already been performed -- open rune -> burst rune, so to speak) vs. Fixed Length (the combo always uses its nth GCD as a finisher, so you don't need any key).
  
  
• Repeatable Actions (you can, during at least one combo step / Form, repeat a certain action that keeps you from moving to the next step yet -- useful for GCD sync), Cumulative Actions (repeatable, but ramping in intensity of its own throughput or buff provided -- also useful for situational burst), or Neither.
  
  
• Unidirectional combos (only proceed in a single direction of options opened up) vs. Bidirectional (can move back towards previous steps, which then wouldn't necessarily be any less powerful, but only by one step at a time) vs. Freeform (capable of jumping even to non-adjacent steps, akin to Monk during PB).
  
  
• Etc., etc.

[CelestiCer]

DRG would be 11111 22222
MCH would be 111 111 1111
And so on…

Really I’m not getting the point how condensing a simple 123 into a 111 could be better. .

If anything? it showcases how much more dumber and boring our Jobs gameplay can become... If I oversimplify SAM of what it is now, vs what people believe they are suggesting, vs what I think could possibly happen by encouraging this route of Job design...

- Present 6.1
TN - M 368 (Iai) M 3 (Iai->Ogi) 3678 (Iai) end opener
123-456-78 (Iai) 123-456-78 M 3 (Iai) 3678 (Iai)

- vs Suggestion of compression
TN - M 123 (Iai) M 1 (Iai->Ogi) 1233 (Iai) end opener
111-222-33 (Iai) 111-222-33 (Iai) M 1 (Iai) 1233 (Iai)

- Worst case I can imagine happening...
No TN - M 111 (Iai) M 1 (Iai->Ogi) 1111 (Iai) end opener
111-111-11 (Iai) 111-111-11 (Iai) M 1 (Iai) 1111 (Iai)

There's No promise Square will give us any depth/improvement/nuance - just anything after we suggest to remove anything from our Jobs. As they continue to homogenize our Jobs? they have not really added any depth of any kind in Endwalker, all they done is simplify and streamline everything. And when they smack the concept of fully un-branching combo's on say a new Job? it wouldn't surprise me to transfer a testing concept that functionally works onto others, even if the gameplay is worse.

I can't recall the last added layer of depth they implemented after they removed two layers off of each Job. I'm still waiting for something that supposedly was supposed to replace my " Kaiten ", mhm

[Deo14]

What do you guys think you will get:


What will you really get:

[Shurrikhan]

What do you guys think you will get:

What will you really get:

If left to just the devs in a sort of "spacemaking" attempt instead of an explicitly "depth-increasing" one... I'd agree.

I feel like for that reason we should probably be asking to make every combo have complexity worthy of its button-count, rather than a button-count befitting its (lack of) complexity. I'll admit, though, that those two things sound a lot alike, especially to anyone who's only ever played with an XIV idea of "combos" in an MMO or MMO-adjacent setting.

Our GCD rotations really are currently the most wasteful, lackluster (especially, relative to what more they could easily support) part of job design at the moment, though.

We absolutely should be looking to improve upon (not merely simplify) them, but that does require not putting on a pedestal what they are now on the basis of what they could be and instead actually trying to reach those more lucrative prospects.

[Deo14]

If left to just the devs in a sort of "spacemaking" attempt instead of an explicitly "depth-increasing" one... I'd agree.

I feel like for that reason we should probably be asking to make every combo have complexity worthy of its button-count, rather than a button-count befitting its (lack of) complexity. I'll admit, though, that those two things sound a lot alike, especially to anyone who's only ever played with an XIV idea of "combos" in an MMO or MMO-adjacent setting.

Our GCD rotations really are currently the most wasteful, lackluster (especially, relative to what more they could easily support) part of job design at the moment, though.

We absolutely should be looking to improve upon (not merely simplify) them, but that does require not putting on a pedestal what they are now on the basis of what they could be and instead actually trying to reach those more lucrative prospects.

Don't get me wrong, I agree with you, but it just feels hopeless to ask them to do anything that isn't dumbing down jobs even more. Hell, you don't even need to ask them, they'll do it anyways. But yeah, I just don't have much faith left in job design in this game. They can't even bring back one fucking skill that we've been asking for nearly 1.5 year. If all the Kaiten uproar with 100s of threads just on EN OF didn't work, nothing else will. Last solution is manufacturing some drama, since they started doing some QoL stuff after all the plugin drama last year.