Originally Posted by Phred
This looks great but it's really difficult to imagine Blizzard turning a blind eye to things like in<>. My understanding is they've refused to put a similar mechanism in the default macro processor because of the chaining it allows.
|
You are very uninformed sir. There is absolutely nothing wrong with this functionality... of course, you would need to read further to see the important part...
|
Originally Posted by Maul
This command allows for the execution of an unsecure chat line after a specified event for a given spell
|
See, UNSECURE being the key part of this feature. UNSECURE means you can do lots of things that blizzard has no problems having timed or automated or chained or anything. Secure actions are things like targeting, casting spells, movement, etc... none of that can be done.