combo skills

[Vrankyl]

Especially when there are times in pve you are in the middle of a combo that splits, but a mechanic happens making you need to change which finisher you are using. Such as melee aoe happening forcing a PLD to go out and suddenly that Royal Authority needs to be a Goring Blade otherwise the DoT falls off. With them reduced to separate 1 button combos you can't really do that, unless they code both buttons to go through the motions each time one is hit.

[Vandril]

Especially when there are times in pve you are in the middle of a combo that splits, but a mechanic happens making you need to change which finisher you are using. Such as melee aoe happening forcing a PLD to go out and suddenly that Royal Authority needs to be a Goring Blade otherwise the DoT falls off. With them reduced to separate 1 button combos you can't really do that, unless they code both buttons to go through the motions each time one is hit.

That's actually exactly what happens in PvP.

[ElHeggunte]

That's actually exactly what happens in PvP.

Not both at the same time though, which is what they mean. Or rather, if you're hitting Combo I, Combo II doesn't also change along with it. If I'm using Combo I and then start using Combo II it makes me start at the beginning of II instead of its Combo I equivalent (at least that's how it works for Monk).

Example: Combo I for Monk is Bootshine > True Strike > Snap Punch and Combo II is Dragon Kick > Twin Snakes > Demolish.

If I use Combo I up to True Strike and then press Combo II, I'll perform Dragon Kick instead of Twin Snakes. This works OK in PvP where abilities have drastically different effects than normal, but in a PvE environment where you might work on a priority system and not a set 1-2-3 rotation, having skills forced into a set order would cause a lot of issues.

[Legion88]

Not both at the same time though, which is what they mean. Or rather, if you're hitting Combo I, Combo II doesn't also change along with it. If I'm using Combo I and then start using Combo II it makes me start at the beginning of II instead of its Combo I equivalent (at least that's how it works for Monk).

Example: Combo I for Monk is Bootshine > True Strike > Snap Punch and Combo II is Dragon Kick > Twin Snakes > Demolish.

If I use Combo I up to True Strike and then press Combo II, I'll perform Dragon Kick instead of Twin Snakes. This works OK in PvP where abilities have drastically different effects than normal, but in a PvE environment where you might work on a priority system and not a set 1-2-3 rotation, having skills forced into a set order would cause a lot of issues.

Counter Argument:
All tanks have 2 combo strings starting with the same skill.
Both combos are advancing to their second tier if either of the combos is used.
After this they split up, combo 1 advances to skill X while combo 2 advances to skill Y in the second tier. And with the use of a second tier skill only the combo with this skill will advance further to tier 3 and the other combo resets to tier 1.
It is the same mechanic like in PvE, the button shows the highlighted skill of the combo, if no skill is highlighted it shows the combo starter.
Same for NIN.

MNK lost his forms in PvP.
With this change they had to force 2 combo strings or allow multiple combo requirements and the former was more easy for them then the later.

All in all i would welcome the PvP combo button for the reasons of button pruning.
I think a job schould be fully playable with just 3 to maximum 4 Cross-Hotbars (R2, L2, R2+L2, L2+R2) on a Controller with the ability to display all of this Cross-Hotbars on the UI. So 24 to 32 Slots for Skills, LB, Sprint, Potions, maybe a mount or more and encounter specific actions.

[Vandril]

Not both at the same time though, which is what they mean. Or rather, if you're hitting Combo I, Combo II doesn't also change along with it. If I'm using Combo I and then start using Combo II it makes me start at the beginning of II instead of its Combo I equivalent (at least that's how it works for Monk).

Example: Combo I for Monk is Bootshine > True Strike > Snap Punch and Combo II is Dragon Kick > Twin Snakes > Demolish.

If I use Combo I up to True Strike and then press Combo II, I'll perform Dragon Kick instead of Twin Snakes. This works OK in PvP where abilities have drastically different effects than normal, but in a PvE environment where you might work on a priority system and not a set 1-2-3 rotation, having skills forced into a set order would cause a lot of issues.

That's because neither of your PvP combos as MNK start with the same weaponskill. If they did, both combos would progress until you use a skill that the other combo doesn't utilize. For example, if you use Fast Blade as a PLD in PvP, which both of your combos start with, both Combo Buttons will highlight and progress to the second weaponskill of the combo regardless of which Combo Button you press to use Fast Blade.

For reference, the PLD PvP combos are:

Combo A: Fast Blade -> Savage Blade -> Rage of Halone
Combo B: Fast Blade -> Riot Blade -> Royal Authority

A bit of detail on how this works:

* If you press either Combo Button to use Fast Blade, Combo A will progress to Savage Blade AND Combo B will progress to Riot Blade.

* If you then use Savage Blade, Combo A will progress to Rage of Halone and Combo B will RESET to Fast Blade.

* If you then use Combo B's Fast Blade, Combo A will reset and progress to Savage Blade AND Combo B will progress to Riot Blade.

That should be enough information to understand how it works.

The only thing you can do in PvE that you can't in PvP with the PvP Combo Button system is use 2nd/3rd abilities in a combo without the combo bonus (like spamming Savage Blade without using Fast Blade first). As far as gameplay mechanics go, the only classes I can see this being a problem for in PvE are MNK and SAM due to their cooldowns that allow them to ignore combo requirements for the combo bonuses of some weaponskills. With the PvP Combo Button system as it works now implemented into PvE, there'd be no way for MNK/SAM to make use of the cooldown.