OK, so...

Macros are not parsed as a unit. The client reads each line in turn and tries to do what that line tells it to do. If it comes across an /ac line, it sends that to the server and lets the server determine if it succeeds or not. If it comes across a /wait line, it waits that many whole seconds (/wait rounds up, <wait> truncates; /wait 2.5 is /wait 3, <wait.2.5> is <wait.2>) before it reads the next line.

This also means that if you encounter any lag at all, you tend to get screwed. For example, if the client sends an /ac command, but there's lag that makes it take a while to get to the server, the client doesn't check that. It moves on to the next line. If that's a /wait, it just waits that many seconds, then sends the next command. If the first command lags, and the second doesn't, they're going to hit the server too close together, and one or both are going to fail.

Macros also don't queue early like regular commands. You can hit a command pulled from the spellbook about half a second early, and the game will register that and cast that ability when it's ready. You can not do this with macros; the client will just start trying them immediately when you press the button, and if you're still in an animation or GCD or cast, the first like will just fail and it'll move on and try the next line, and so on.

Aaaaalso, you can only have one macro running at a time. If you use any other macro while this one is running, it will interrupt and stop this one, and any lines that haven't already been executed will be ignored.

So in your first attempt here:
Quote Originally Posted by Beyondgrave View Post
/ac "Cleric Stance"
/wait
/ac "Bio ii" <t>
/wait 3.0
/ac "Miasma" <t>
/wait
/ac "Bio" <t>
/wait
/ac "Cleric Stance"
You send the server a command to use CS. Then you tell the client to wait 1 second (which is the default if no number is specified). Then try to cast Bio II on your target. Then wait 3 seconds. Then try to cast Miasma on your target. Then wait 1 second. Then try to cast Bio on your target, which fails, because you only waited 1 second and you're still in your GCD. Then wait 1 second. Then try to cast Cleric Stance. Not entirely sure why CS would fail there. It's more than 5 seconds total (the CS CD), and the fact that you're still in your GCD after Miasma shouldn't matter (I don't think).


Quote Originally Posted by Beyondgrave View Post
So I changed it to :
/ac "Cleric Stance" <me>
/wait 1
/ac "Bio II" <t>
/wait 3
/ac "Miasma" <t>
/wait 2.5
/ac "Bio" <t>
/wait 1
/ac "Cleric Stance" <me>
You've got the wait times closer to correct here, but that 2.5 is really a 3, so you might as well just make it 3 so you're not deluding yourself. This looks like it should work otherwise, as long as you're not spamming it too early. Even though CS is off-GCD, if you're in the midst of casting something else, or still going through the animation of an instant-cast, you won't be able to use it. If you're going to use this, you'll either have to wait until you are absolutely done with everything else to push the button, or spam the button like crazy (so that the macro constantly interrupts itself) until you see CS activate, and then stop and take your fingers off the keyboard/controller.

You also won't be able to switch targets in the middle of this macro if you're going to use it. Because of that line-at-a-time parsing, if you switch targets after Bio II, for example, it'll try Miasma on your new target.