2.16 macro change

[necrosis]

OK. Home now.

If someone is out of range it errors out like normal. This is with using <mo> commands but most likely works like this for all.

However. With <mo> commands if your mouse cursor is over no target the action defaults to you. Which is complete and total horse crap. I have missed targets from moving (me or the target) before. This only adds another way to get shafted and send an important spell to cool down.

Benediction anyone? Bad enough we see targets die after casting it and it going to cool down when we click on the right target to begin with.

This needs to be rolled back.

[PlanckZero]

However. With <mo> commands if your mouse cursor is over no target the action defaults to you. Which is complete and total horse crap. I have missed targets from moving (me or the target) before. This only adds another way to get shafted and send an important spell to cool down.

Wait... what?

Do people actually use mouse over commands on character models or something? Is that how you're ending up with activating macros over no target? When someone literally moves away when you hit the macro? I'm having trouble imagining any other scenario where you would end up hitting a macro on dead air unless you're just whacking buttons by accident.

[necrosis]

Wait... what?

Do people actually use mouse over commands on character models or something? Is that how you're ending up with activating macros over no target? When someone literally moves away when you hit the macro? I'm having trouble imagining any other scenario where you would end up hitting a macro on dead air unless you're just whacking buttons by accident.

It happens. Last thing we need is another way to get screwed out of a casting.

[Naunet]

If someone is out of range it errors out like normal.

Awesome. That's all I was concerned about with this.