in game optional tools

[MorbolvampireQueen6]

Well let's be real there: bots don't need that functionality to operate and it doesn't really help them.

About the only game I've played where a castsequence-type macro was useful was Rift, but only because it allowed spell cascading AND you could legitimately have a rotation with 50 abilities in it because of how their class system worked.

In WoW... eh, I tried it for a while when I was first learning the game, but it didn't take long to realize it was a bad idea if I ever wanted to like... do well. I feel the same thing would happen in FFXIV. It's just not that useful when compared against just learning your rotation properly.

you do know in pvp it basicly forces the use of castsequence and dps is just fine lol take a lok at rdm mele combo in your pvp profile

[Aramina]

you do know in pvp it basicly forces the use of castsequence and dps is just fine lol take a lok at rdm mele combo in your pvp profile

What is done in pvp is not at all the same as a castsequence macro.

As an example, let's say you have Spells 1-4 and the GCD is 2.5 seconds. If you hit the button at exactly 2.5 seconds then it would work fine (barring spell queuing in ffxiv which I mentioned in an earlier post). BUT if you don't, the spell will fail, but the the macro will still progress meaning you skip a spell.

Spell 1.
2.5s
Spell 2.
2.3s (hit it too early)
Spell 3 fails.
2.5s
Spell 4.

If Spell 3 interacts with Spell 4 in any way, then it is even worse.

The macro does not (can't) take into account if you mistimed hitting the button. It only knows that you hit it, and hitting it means to go to the next spell in the macro.

[MorbolvampireQueen6]

What is done in pvp is not at all the same as a castsequence macro.

As an example, let's say you have Spells 1-4 and the GCD is 2.5 seconds. If you hit the button at exactly 2.5 seconds then it would work fine (barring spell queuing in ffxiv which I mentioned in an earlier post). BUT if you don't, the spell will fail, but the the macro will still progress meaning you skip a spell.

Spell 1.
2.5s
Spell 2.
2.3s (hit it too early)
Spell 3 fails.
2.5s
Spell 4.

If Spell 3 interacts with Spell 4 in any way, then it is even worse.

The macro does not (can't) take into account if you mistimed hitting the button. It only knows that you hit it, and hitting it means to go to the next spell in the macro.

im pretty sure i said like pvps o n 1st post i even used bard as a example in pvp for how it should work lol

[Lersayil]

Personally I just wish mouse over macros would work properly with healing spells and not fizzle / self-target 30% of the time. Fixing cast sequencing in macros would just be icing on the cake.

[Aramina]

im pretty sure i said like pvps o n 1st post i even used bard as a example in pvp for how it should work lol

It works exactly how I said it works. Maybe you should follow the advice you gave me and make a starter account on WoW. The macro can't tell if you succeed in casting a spell or not. It can only tell if you hit the button. Now if you want something that does work like pvp does, that is another thing.... but they have already said they won't be making combos like that work for PvE.

[Callinon]

you do know in pvp it basicly forces the use of castsequence and dps is just fine lol take a lok at rdm mele combo in your pvp profile

That's a bit different since the game's own interface is doing it for you rather than a macro just executing a sequence of commands. The game knows when a spell has fired off correctly and moves to the next one, the macro doesn't know that... it just moves to the next one. I'd talk about spell queuing here too but Aramina seems to have that covered nicely.

Personally I just wish mouse over macros would work properly with healing spells and not fizzle / self-target 30% of the time. Fixing cast sequencing in macros would just be icing on the cake.

I've never had a mouseover macro do that to me, but I only use them for certain off-gcd things (like Goad or Cover). Haven't tried to use them for straight healing. I'd be interested in seeing the macro that's failing for you, it's possible it's just not laid out properly.