Macro recently broken

When 2.16 hit, I made a simple macro

/macroicon "Physick"
/ac "Physick" <mo>

With the target priority change in 2.16 this would, if I did not have a target moused over, function as if I just pressed my Physick ability and use my target or my self.

As of yesterday, this macro just reports an error of ' "<mo>" is not a valid target ' if I don't have something moused over.

Was there a change to this in one of the hot fixes that was not announced?

To say again, this macro worked fine with no errors a few days ago.

I don't want to have to go back to a longer macro of

/macroicon "Physick"
/ac "Physick" <mo>
/ac "Physick" <t>
/ac "Physick" <me>

... as that spams the middle of my screen with errors. (I can turn them off in chat, but not the onscreen one that beeps annoyingly..)

Anyone know why my first macro stopped working?

Yes, they change it back in a hot fix due to people being unhappy with the change.

The problem is, some people want "when mouse over nothing, do nothing" and other want "when mouse over nothing, cast on me"

My opinion : when there's diverging opinon for one thing => make an option for the user to choose...

In fact, when the dev team need to choose between multiple thing to do, it should always be an option in a menu (color of AoE ^^) unless it is a memory or resource problem or too different to be a trivial implementation.

PS: It's usually a trivial implementation and it's the way I do it for all the IHM I developped : choose a default option, let the user change it if he wants it.

Quote:

---

Originally Posted by Aura_Shurifon

The problem is, some people want "when mouse over nothing, do nothing" and other want "when mouse over nothing, cast on me"

---

The hotfix changed it back to the original because that pattern allows more flexibility. Having it automatically cast on yourself when failing the first attempt prevented things like a macro that can cast on either <t> or <tt>, or one that can cast on either <mo> or <t>, whereas people who want the "cast on myself" default can do it anyway with another <me> line in the macro.

The only disadvantage of the current version is, as mentioned, those errors on the screen. A post in another thread requested a <noerror> option, which seems a better solution than a universal default like casting all heals on yourself when the specified target is invalid.

I think i'm the one who write about the <noerror> option ^^
But yes, I agree with the "changed back to older system" because this way, everything is "doable" like you said.