Auto Combo Buttons in PvE

[BubblyBoar]

No thank you. PvE has far more nuisance than PvP

[Mirch]

No thank you. PvE has far more nuisance than PvP

Players play with 50 buttons in pve no one bats an eye, you have 50 in pvp and the worls ends. Uwu

[Vaer]

I wouldn't use it for most jobs since it wouldn't benefit that much from it since jobs that do have combos usually have branching combos off the same starter.

All of ninja's combos start with the same one, Samurai is similar but has an aoe combo with 2 branches, Monk has a combo system where you can replace each step with something else depending on what you need. DRG is really the only one that would really benefit from it since their combo is just 1-2-3, 4-5-6 [+f&c/wt] and I guess the RDM melee combo and the tank 1 2 3. Would get weird if I had like 4 different buttons that start with the same combo starter.

Works ok for PvP since they delete some of the PvE combos and just have 2. Some jobs have 4+ combos in PvE.

Personally I would rather do 1-2-3 1-4-5, 1-4-6 instead of 1-1-1, 2-2-2, 3-3-3. Feels like a combo instead of using just 1 button.

If it's optional I guess I'm neutral about it as long as they don't delete things to accommodate it.

[LiliBoulanger]

I wouldn't use it for most jobs since it wouldn't benefit that much from it since jobs that do have combos usually have branching combos off the same starter.

This could potentially make the UI confusing in a new way, yeah. It would be a case by case basis and would take memorization of your UI. But that's true of the system we have now as well. Maybe the real solution would be to make them not only optional but also customizable? So maybe something like for PLD what I described in the OP, OR Fast Blade could be a dedicated button, and the 3 distinct combos could be their own buttons. 4 buttons total instead of 6. Still improvement.

[Vexander]

Wouldn't mind it for SAM for the three main Combos. Getsu, Setsu, and Ka. That'd trim the keybinds from 6 to 3.

[LiliBoulanger]

Works ok for PvP since they delete some of the PvE combos and just have 2. Some jobs have 4+ combos in PvE.

Yeah this is probably why they didn't just implement the UI feature to PvE and PvP from the get go.

[DeaconMoore]

They don't have the capability to do this already with macros in the game?

[LiliBoulanger]

They don't have the capability to do this already with macros in the game?

I don't think so but even if there was this functionality, because the macro system is so broken with regards to using them for high level play, it's a moot point.

[CorbinDallas]

They need to have Dreadwyrm/Deathflare automatically swap to Summon Bahamut/Enkindle Bahamut.

1 button tank stance swapping for Warrior and Paladin, once you hit 30 have a trait that automatically puts you in tank stance when switching to said jobs, then have one button to swap to and from DPS back to tank. There's literally 0 reason to not be in a stance at all post 30.

Consolidate Fire and Blizzard 4 into 1 button, changing based on whether you're in Astral/Umbral, you can't use either without the respective buffs anyway. Have Leylines change to Between the Lines for the duration it is active, again, you can't use the latter without the former active anyway.

There are lots of small consolidations like this that should have been there when Stormblood launched. They've done it to other jobs already, for example Nastrond on Dragoon, yet why are there so many left unaccounted for?

[Bourne_Endeavor]

Even optional, I cannot support the idea since it would likely mean the devs don't bother consolidating less used skills and semi-incentivize this aspect. It may seem silly to some, but reducing the combos down to mashing one button repeatedly makes the game itself feel boring. It's one of many issues I have with Dark Knight; you just spam Dark Arts half the time. Now if future expansions add a new lay of complexity to the combat system, thus making up for the lack of combo specific buttons, I could warm to the idea. Alas, Stormblood showed they would rather simplify everything. So I'm not too faithful it wouldn't just dissolve into 1-1-1.