Idea to simplify combo action skills

[Garvey]

Why wouldn't it work? I can't see any situation where you would still want to use "disembowel" when the next combo action is "chaos thrust", etc.

[Callback]

Why wouldn't it work? I can't see any situation where you would still want to use "disembowel" when the next combo action is "chaos thrust", etc.

It differs a lot between classes tho, in terms of how they branch. For many you need to keep the option of resetting to the first skill in the chain if you need to quickly set up for a different finisher than you are currently going for.

[Garvey]

It differs a lot between classes tho, in terms of how they branch. For many you need to keep the option of resetting to the first skill in the chain if you need to quickly set up for a different finisher than you are currently going for.

Ok, I've only really played lancer, so I haven't encountered a scenario where I'd want to reset a chain, but it may still be simpler to still use this new approach, along with a reset button for those situations.

At the very least, it would be nice to just have both styles as a preference option XD

[Darkstride]

So what about Ninja who has:

Spinning Edge > Shadow Fang
Spinning Edge > Gust Slash > Dancing Edge
Spinning Edge > Gust Slash > Aeolian Edge

What is the icon supposed to change to when I have multiple options?

Unless I've misunderstood your idea.

[Garvey]

So what about Ninja who has:

Spinning Edge > Shadow Fang
Spinning Edge > Gust Slash > Dancing Edge
Spinning Edge > Gust Slash > Aeolian Edge

What is the icon supposed to change to when I have multiple options?

Unless I've misunderstood your idea.

Good point, after giving it some thought, I'm going to adjust my idea a bit now. You could still simplify it into 2 buttons, one for each option you have at a given moment.

Initially, the first button is Spinning Edge, and the 2nd button is inactive.

Once you use Spinning Edge, the first button morphs into Shadow Fang and the 2nd button morphs into Gust Slash.

If you use Gust Slash, the first button morphs into Dancing Edge, and the 2nd button morphs into Aeolian Edge.

So your 3 sequences would be

1 -> 1
1 -> 2 -> 1
1 -> 2 -> 2

instead of

1 -> 2
1 -> 3 -> 4
1 -> 3 -> 5

And for dragoon it would be the following sequences (starting with either impulse drive or true thrust)

1 -> 1 -> 1 -> 1
2 -> 1 -> 1 -> 1

instead of

1 -> 2 -> 3 -> 4 or 5
6 -> 7 -> 8 -> 4 or 5

The only disadvantage I could see with this is that once you start a sequence, you can't stop it and switch to another one in the middle of it. But I think that could be solved with a simple "reset" hotkey, if that situation ever arose. Honestly though in playing, I've never really wanted to stop a sequence in the middle of it to do a different one, since it seems like a loss to do so.

[Genaxx]

I think would be possible to do this with a macro, I will try it tomorrow and get back to you.

If we could macro macro's to the hotbar then this would be simple, unfortunately we can't but I have another method in mind.

It would actually help with the low standard dps, since they couldn't use the same skill over and over.

[Darkstride]

It think would be possible to do this with a macro, I will try it tomorrow and get back to you.

If we could macro macro's to the hotbar then this would be simple, unfortunately we can't but I have another method in mind.

It would actually help with the low standard dps, since they couldn't use the same skill over and over.

Macros won't queue, though, so it would mess up the flow of chaining your combo abilities. I feel like the result would be less efficient.

[Morbid]

Make sure to click that little lock below the hotbar after setting up your skills. To see skills on cooldown I just activated one of the vertical hotbars shrunk it a bit and put those abilities on there so you can see when they refresh. Clean up the UI by also selecting the option to not show inactive slots.

[Genaxx]

I also use an additional hotbar like Morbid but a horizontal one to display all the long CD skills that are on my second bar. Make sure its not set to shared so you can use it for multiple jobs.

There's also the very annoying "quirk" where when you first pick something from the 2nd bar, it will swap back to the first.

Could you explain this more? I've never know this to happen. Are you saying that if you use R1 to go to the 2nd bar and then use a skill, it will change back to the first?

Macros won't queue, though, so it would mess up the flow of chaining your combo abilities. I feel like the result would be less efficient.

They wouldn't need to queue if you could macro macro's to the hotbar. It would work like this;

/mlock
/micon "Spinning Edge"
/ac "Spinning Edge" <t>
/crosshotbar set "Gust Slash" 1 RAR

which then changes the same button to this;

/mlock
/micon "Shadow Fang"
/ac "Shadow Fang" <t>
/crosshotbar set "MACRO NAME" 1 RAR

But since we cannot set macros to the hotbar like this, I will try another way.

The other way is to do it like this;

Hotbar 1
/mlock
/micon "Spinning Edge"
/ac "Spinning Edge" <t>
/crosshotbar change 2

Hotbar 2
/mlock
/micon "Shadow Fang"
/ac "Shadow Fang" <t>
/crosshotbar change 1

/mlock
/micon "Gust Slash"
/ac "Gust Slash" <t>
/crosshotbar change 3

Hotbar 3
/mlock
/micon "Armor Crush"
/ac "Armor Crush" <t>
/crosshotbar change 1

/mlock
/micon "Dancing Edge"
/ac "Dancing Edge" <t>
/crosshotbar change 1

/mlock
/micon "Aeolian Edge"
/ac "Aeolian Edge" <t>
/crosshotbar change 1

Technically it works, but its not very practical, since if you press the next action before the timer is up, it hotbar will change and you will lose your combo. Sadly I dont think its possible to do this right now, however I think its possible with 1 > 2 combo's like below, giving you however many seconds to combo the second action before it switches back to the original.

/mlock
/micon "Spinning Edge"
/ac "Spinning Edge" <t>
/crosshotbar change 4 <wait.3>
/crosshotbar change 3

[Bluffnix]

its been discussed before and it was referred back to why we have macro's, and etc. The argument was then, macro moves dont queue/subjected to delay.

Dev's are like "But it works!"