Can we please cool it with the macros?

[Cakekizy]

My favorite is when someone spams LIMIT BREAK! LIMIT BREAK! LIMIT BREAK!

That would tempt me to LB with wrong class on purpose.

[MilesSaintboroguh]

That would tempt me to LB with wrong class on purpose.

I had someone in my party do that on purpose for the lulz. He said "hey, you didn't say who should use the LB"

[Raeletta]

I just set a couple of rules for my use: If it's in /party, it needs to be short and sweet. I WILL keep Provoke on a sound effect macro as I will keep Hallowed Ground on a sound effect macro.
If it's not important, just for effect or fun, it goes in /s like the words I spout when it comes to Limit Break.

If someone seriously spams them (Blunt arrow is one of the very worst) just ask them to nuke the macro. It's not hard.

[FoxyAreku]

<Blunt Arrow> <Just Used It!> <se.10>

[Cakekizy]

Is it possible to /blist a group member during an instance?

[Mere]

Those people who can't stop themselves from pushing a skill button multiple times till it finally goes off, should put their /p message on a 1 second /wait:

/action "Name" <t>
/wait 1
/p {Action Name}, {Just used it.}

That way the party message only appears once, when you stop pushing the button for at least 1 second.

Back to the subject, I do agree with skill announcement macros. Like for tank swaps, you either don't blink so you can catch when the other tank did provoke, or trust on their macro and confidently wait for the sound. Yes, provoke might fail, could be on a CD or fired right after another skill so it didn't go thru, but that won't be the norm. It will be more likely that the skill worked and all is good. People who fail to do what their macros said they did, aren't skillful enough to be using macros and should at least create another macro to announce their mistake when necessary, or trigger a macro interrupt for macros with countdowns.

[ElHeggunte]

There are only a few situations I don't mind macros:

1) To signify a critical ability or buff. Usually in the case of tank CDs.
2) To signify the use of abilities that don't stack so CDs don't go to waste. Bard songs are a good example if the group has more than one Bard.
3) To signify you're casting Raise on someone (so long as the macro is simple and not an obnoxious novel's worth of lines) so other players don't waste their time trying to cast on the same target.
4) Big, loud general raid warnings for places like WoD to draw attention to important mechanics.

Otherwise, I don't want to see it. I don't want to hear it. If it isn't important but you want to be sure you pressed the proper macro, keep it in /echo.

[DracotheDragon]

i only ever have macros on skills that are important to a fight (silence provoke stun virus etc) the only 2 i will use a lot is my "thanks for the party" macro and the "Were dead wipe it up" macro

though to those who spam the ever lasting heck out of macros need to tone it down quite a bit

[Shamo_Lomenzo]

I have 2 macros, both with very short messages and a sound effect. One for Virus, one for Raise. The raise one is mostly to say "Hey other healer, I'm swiftcast reviving this guy, please don't waste your MP doing the same thing." And if anyone gets bothered by that, sorry not sorry.

/p "Raising <t>, back on your feet! <se.7>"

[Chihaya]

Sounds like someone that joined my PF - would spam this 10+ line macro to say hi for every new person that joined and repeat it if he ever get interrupted during his macro