(05-05-2015, 01:32 PM)Temariah Wrote:(05-05-2015, 09:07 AM)-snip- Wrote: OTHER IMPORTANT NOTE! (Because I find it really important to say)
Please for the love of all that is good (or bad if that's your style), DO NOT put your fancy text before your actions. Why? Because when one spams their macro hotkey/button/etc as one is wont to do, it floods the chat. Add a sound effect and I can promise there's a person who get horrible eye twitching from the following.
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
I JUST DID A THING <SE.1>
*thing actually happens now that the skill goes off*
Alternatively, try a macro like this:
/ac "thing" <target>
/party I JUST DID A THING <SE.1>
Then, spam away. It won't actually go through until your skill does, AND you can get fancy text!
I'm not entirely sure that this is accurate. My CC macros look like this:
/micon "Repose"
/mk off
/action "Repose" <t>
/party "Repose" on <t>!
/wait 1
/mk bind1 <t>
The shoutout goes through to my party as soon as I press the button, even though the shoutout is after the command text. I tend to be pretty precise with my skill-usage, so I rarely spam party chat, but it has happened. Not sure how your example is different than mine, though.
I didn't show an improper macro.
The offending one that'd create my example would be:
/party I JUST DID A THING <SE.1>
/ac "thing" <target>
In the above, spamming the button does the text before the action. ...so if the action isn't ready, it will only do the text, and nothing else. It's particularly with trigger-happy button-mashers (like me), which is why I don't really macro anything that will end up in a text box.
