Quote Originally Posted by Hor',index.php?page=Thread&postID=181545#post18154 5]It can't do anything that isn't allowed by Blizzard code.[/quote]
[quote='Souca
If they didn't want it done, you wouldn't be able to.
Just because you CAN do it with the built-in macros or API doesn't mean you SHOULD.

There's only so much you can prevent, and there's the never ending battle of problem, patch, fix, find new problem. So I wouldn't take "it works" to mean "it's ok to use", particularly if there's no actual confirmation of the functionality and/or conflicting information (i.e. GM conversations regarding delays, loops and timers -- which can always be found on the GM conversations wiki).

...such things as if/then statements and time delays are not possible
Quote Originally Posted by Vyndree
While researching a bit on /click, I did find someone posting a way to insert a delay into the normal /macro interface (which we all know is a big no-no). So the argument that "it's in the in-game macro interface, it's ok" can be nullified:
[spoiler]http://forums.worldofwarcraft.com/thread.html?topicId=14697300474&postId=14695898097 1&sid=1
/cast MySpell
/script local t = GetTime(); while GetTime() - t < 6 do end
/cast MySpell2

Try it in your next raid. I'm sure you'll love it. Just change the "6" to whatever delay, in seconds, you want.

Disclaimer: Use at your own risk. I take no responsibility for any consequential actions which may occur from running the above code.
[/spoiler]
Like I said, delays are bannable. DO NOT USE this code.
"I can, therefore I should" is a poor argument. We have blues saying that "delays are bad", and we have an addon that utilizes delays. I'm not saying "I know this addon is bad", but merely saying "I don't know that this addon is good". It is a subtle but important difference.

OP: As a general rule, if you are ever concerned about whether functionality is OK/not OK -- your best bet is to ask an official source before using it.