Anyone else having macro issues after SB release?

[Razor]

Before I waste SE's time by making a bug report, I wanted to check with the community first to see if maybe its just a latency problem multiple people are having due to server loads.

So while I have only noticed the issue on Red Mage, I haven't done much with the other jobs since Stormblood launched. It also may not be as possible to write a macro that would screw up like this for other jobs.

So basically what I have written is this:
/macroicon "Verthunder" (have also tried /macroicon Verfire, no change)
/ac Verfire <t>
/ac Verthunder <t>

For those unfamiliar, Verfire skill is only executable when procced by Verthunder. (Unlike, say, Machnist where both skills are usable at all times.) So this macro is designed to be a single button press that will use Verfire if it's ready, otherwise use Verthunder and try to proc Verfire. It works as intended, most of the time. The problem is that every 1/5 or 1/10 times the macro goes off, it gets hung up and tries to hardcast Verthunder even though I have the Verfire Ready proc. The frequency seems more common the faster I hit the macro when GCD comes up.


If I interrupt the Verthunder cast and try again, 9/10 times it will work correctly and cast Verfire, but not always. Both Verfire and Verthunder are on GCD, so there should be no difference there. To the best of my programming knowledge, the macro should execute its lines with almost instant succession, so there shouldn't be any issue with me trying to use the macro too fast before GCD up. I have tried changing the macro to this hoping it would compensate for any latency issues:

/ac Verfire <t>
/ac Verfire <t>
/ac Verfire <t>
/ac Verfire <t>
/ac Verfire <t>
/ac Verfire <t>
/ac Verfire <t>
/ac Verfire <t>
/ac Verthunder <t>

It made no change to the issue, I still occasionally get erroneous Verthunders. And yes, I have the exact same macro for Veraero > Verstone, and it does the exact same thing. I just didn't want to confuse the non-RDMs in the crowd. Does anyone else have any info or experiencing a similar issue?

[Valkyrie_Lenneth]

Well, you see, macros are bad, and they dont work all the time, because queueing doesn't work with them. Never macro battle skills.

This is intentional, and has been this way since 2.0 released.

[kattzkitti]

Well, you see, macros are bad, and they dont work all the time, because queueing doesn't work with them. Never macro battle skills.
This is intentional, and has been this way since 2.0 released.

Can confirm. Macros are sketchy under the best conditions, even if you use the different "wait" commands to space the actions out.

[Razor]

because queueing doesn't work with them.

This is intentional, and has been this way since 2.0 released.

Yes, they removed queueing back in 1.3 or 1.35 something like that. But this isn't an action queue, it's using the macro function to force one skill to error while the other one is running. For example, I have another macro on PLD:

/ac "Shield Bash"
/ac "Shield Toss"

This one is a little different because the engagement distance causes Shield Bash to always fail if I am outside melee distance, BUT, I've never Shield Toss'd at close range due to a macro issue. But I also haven't done much on PLD since SB

[Rasylia]

Yes, they removed queueing back in 1.3 or 1.35 something like that. But this isn't an action queue, it's using the macro function to force one skill to error while the other one is running. For example, I have another macro on PLD:

/ac "Shield Bash"
/ac "Shield Toss"

This one is a little different because the engagement distance causes Shield Bash to always fail if I am outside melee distance, BUT, I've never Shield Toss'd at close range due to a macro issue. But I also haven't done much on PLD since SB

That actually sounds like a good way to free up a spot on my hotbar

[Valkyrie_Lenneth]

Yes, they removed queueing back in 1.3 or 1.35 something like that. But this isn't an action queue, it's using the macro function to force one skill to error while the other one is running. For example, I have another macro on PLD:

/ac "Shield Bash"
/ac "Shield Toss"

This one is a little different because the engagement distance causes Shield Bash to always fail if I am outside melee distance, BUT, I've never Shield Toss'd at close range due to a macro issue. But I also haven't done much on PLD since SB

Well, maybe you aren't waiting long enough to hit the button then, and the macro starts? I don't know, I dont use macros because they always fail when needed the most.