/wait n and <wait n>

[Kikosho]

At this point, I would settle for my macros working when I use them the first time. No reason I should be hitting my macros multiple times just to get them to work properly. Tired of equipment not being equipped or abilities not being used.

[Enfarious]

Ah, I see. I'd rather just see unlimited (or expanded) macro lines, rather than jamming a wait into another command, but I'm ok with your suggestion as well.

I don't disagree, it was one of the things about ffxi windower(which I would never use of course) that made it useful. But since there's already code in place to handle other placeholders adding another place holder would probably be more convenient at least until 2.0.

Peeeeersonally...
I'd prefer if the macro was validated entirely client-side and then sent for the server to execute it on it's own, rather than continuously sending commands, this way one could make a much bigger macro.
Hell, that'd probably be pretty great because it'd probably let them add stuff like a bigger macro size, an If statement, oh god i'd love that (because I want to make just one macro for 'self-heal' but it'd be different for each class and job)

Sadly this will probably never happen, it would make it entirely too easy to add hax to macro's to accomplish things that they won't want happening. By offering up a way to insert binary date into a macro that's seemingly "safe" you could effectively packet spoof through the use of the macro system.

At this point, I would settle for my macros working when I use them the first time. No reason I should be hitting my macros multiple times just to get them to work properly. Tired of equipment not being equipped or abilities not being used.

This is the reason for a /wait, especially in the case of gear swaps where it causes a frame delay when you blink lines get skipped. With a <wait> after a gear change it would essentially allow you to compensate for that gear/blink delay in the client/server communication chain.