Macros falling to 2nd skill?

[Arasiel]

I've seen with testing that macros are bugging out.

Monk Example:

/ac "Snap Punch" <t>
/ac "Twin Snakes" <t>
/ac "Dragon Kick"<t>

Sometimes if the macro is pressed too quickly you will end up doing Dragon Kick no matter what stance. Is there a fix for macros behaving this way?

[Arasiel]

This is the only multi macro I use since I'm ps3 controller on PC.

EDIT:

So just testing out on a trianing dummy that particular macro.. If I just sit there and hit the button none-stop sometimes it will go: Dragon Kick, Twin Strikes, Dragon Kick.. Sometimes: Dragon Kick, Twin Strikes, Snap Punch, and every once in a while Dragon Kick, Dragon Kick..

I thought maybe it had to do with server lag vs. greased lightning giving more haste. But ive seen the opener fall back to Dragon Kick after Twin Strikes.

[soulz]

If you want to use macro on monk, i suggest to separate Opo-opo stance from Raptor and Coeurl stance (because you can use opo-opo stance anytime w/o restriction of form).

[Enfarious]

I noticed this happening on my healing macros:
/ac "Physick" <t>
/ac "Physick" <tt>
/ac "Physick" <f>
/ac "Physick" <me>

has started rolling all the way down to the final line, whether I have a valid target, target's target, or focus.
Also on jobs where I have Mercy Stroke(or it's equiv from brd) I used to:
/ac "Mercy Stroke" <t>
/ac "Whatever" <t>

and Mercy would trigger if it was available, now it just skips ...

@Soulz, the way his macro is ordered works fine, if your in Couerl it should use the Couerl form move, which is first, in Raptor it will fall through to the Raptor, in Opo-Opo or no stance, is the only time it would ever reach the final line. The problem is that for some reason macros are rolling over lines w/o executing them now, unless there is a /wait.

[Bixby]

I noticed this happening on my healing macros:
/ac "Physick" <t>
/ac "Physick" <tt>
/ac "Physick" <f>
/ac "Physick" <me>

This is a different issue. It's not falling through to the <me> line, it's self-casting on one of the other lines because <t> or <tt> or <f> matches a target that can't be Physicked. If you try to cast Physick (without macros) while you're targeting something you can't Physick, you end up Physicking yourself, so that's what each of the first three lines do, too. You'd notice the same behavior even if you removed the last line.

[Enfarious]

This is a different issue. It's not falling through to the <me> line, it's self-casting on one of the other lines because <t> or <tt> or <f> matches a target that can't be Physicked. If you try to cast Physick (without macros) while you're targeting something you can't Physick, you end up Physicking yourself, so that's what each of the first three lines do, too. You'd notice the same behavior even if you removed the last line.

Hmmmm ... well that's interesting, no more of that working as desired then ; ;

[Arasiel]

Just wracks my brain on what's causing the macro to fail and Dragon Kick reuse. I play around with macros from time to time and it's just odd.

[Bixby]

I haven't had a chance to mess around with these sorts of macros all that much, but I'd imagine it's just what you think: lag. The server doesn't update your client fast enough as to what stance you're in, so the macro ends up trying the wrong ability.

Also, macros interrupt each other. They're fired one line at a time, and any currently running macro is interrupted & stopped by any new macro being activated. These should be going from line to line pretty much instantly, so that interruption might be getting a little screwy. Try making a macro with just three /echo or /t <me> lines like so:

/t <me> line 1
/t <me> line 2
/t <me> line 3

Spam it as fast as you can. I haven't tried this yet (keep meaning to and forgetting) I wouldn't be surprised if your chat log fills up with lines all out of order and jumbled up. In theory, you should only ever get 1, 1-2, or 1-2-3. If you ever get 2, 2-3, or 3 on their own/out of order, that shows that interruption isn't working correctly, and that would partly explain why it'd fall through to Dragon Kick; you're ending up with the last line(s) of the macro going off on their own, and since Dragon Kick doesn't need any particular stance, it goes through.

[Arasiel]

I did some testing killing some time before work with this kind of macro:

/ac "Snap Punch" <t>
/ac "Twin Snakes" <t>
/ac "Dragon Kick"<t>

Here is the results:

11100111101111110111110001111

Binary? lol.

1: Represents the Macro going Dragon Kick -> Twin Snakes -> Snap Punch.
0 represents the Macro going Dragon Kick -> Dragon Kick or Dragon Kick -> Twin Snakes -> Dragon Kick

This was tested on a Training Dummy just spamming the macro none stop. The macro seems effective for the most part but if you get a triple 000 fail then Greased Lightning would drop.

[Kiwikies]

could have an answer though i'm not entirely sure, if you want the macro to use dragon kick>twin snakes> snap punch try this

/macroicon "dragon kick" (reason for this is that it flashes when you're in the right stance)
/ac "dragon kick" <t> (reason for this is so that it uses dragon kick on your target)
/wait 2.5 (reason for this is that you need the global cooldown to finish)
/ac "twin snakes" <t> (reason for this is that is uses twin snakes 2.5 seconds AFTER dragon kick)
/wait 2.5 (reason for this is that you need the global cooldown to finish)
/ac "snap punch" <t> (reason for this is that is uses snap punch 2.5 seconds AFTER twin snakes and 5 seconds after dragon kick)

what you will do is; press macro once let it run its course.
The "/wait 2.5" can be altered to a smaller number, however it has to be tenths of a second, so it can't be 2.43 but it can be 2.4, however round up. what this number is, is your global cooldown, to find this look on your skills and the majority will have something close to 2.5 seconds, for me, wearing majority darklight armor my gcd is 2.44 seconds, now if I put /wait 2.4 it wouldn't work, because i'm trying to use the next ability 0.4 seconds early so you HAVE to round up, this tends to be 2.5, but if you have say, 2.26 gcd, you would then round up to the nearest tenth, being 2.3 so your /wait would be "/wait 2.3".
Hope this is what you're looking for.