And this is why no one on this forum takes you seriously.
There are some classes who suffer a massive opening burst DPS loss without proper pulling etiquette.
Printable View
If I remember correctly, it's because they don't want players to cheese through the game by macro-ing multiple actions together.
Which is why I suggested for single action (and probably announcements) macros to be given the ability to queue. I believe it would make a nice QoL update, but I doubt it will happen anytime soon, if it even would.
Would you mind elaborating since I'm not sure I follow? Did they say why it would cheese the game? Would allowing macros to queue lead to rotation macros similar to what RIFT ended up with?
What about <mo>? Why would they give us a mouse over command we can't use because macros also break healing spell queues?
I'm not trying to be confrontational or anything. I legit don't understand since as it is now, things can be macro'd together or with text commands such as <t>, <tt>, <mo> etc, but the only reason it isn't common is because it's detrimental in one way or another (DPS loss, slow-to-fire heals).
Seems odd.
This flaming arrow macro is pretty god tier simply because it makes the skill easier to weave in rotation.
/micon "Flaming Arrow"
/ac "Flaming Arrow" <t>
It places the arrow directly in the center of whatever your target may be. In the case of a larger boss with a ton of adds, it may be preferable to use the normal skill but otherwise this really helps out
Most of those failed announcement macros are just badly designed. I've seen to many announcement macros with the call coming before the action which means that another macro can interrupt it (which is what causes the failed use). When they try to use the ability they start spamming the macro which interrupts itself causing it to fail until they stop spamming.