Cure Macro craziness with the new Fix

[Viridiana]

That's what every whm spell does if your target is invalid: it is cast on yourself.

Then that should be happening in scenario 1 as well. If the mouse is over nothing, the <mo> should resolve to nothing, which is invalid, and by your logic should then cure the player. Instead, it's being cast on <t>. Presumably, scenario 3 has a valid <t>, but an invalid <mo>; and the macro is instead resolving to <me>.

[Nalou]

Then that should be happening in scenario 1 as well. If the mouse is over nothing, the <mo> should resolve to nothing, which is invalid, and by your logic should then cure the player. Instead, it's being cast on <t>. Presumably, scenario 3 has a valid <t>, but an invalid <mo>; and the macro is instead resolving to <me>.

In scenario 1, you mention cure is cast on your <t>, so you do have a valid target.
If your target was a monster or something you cannot cure (like in scenario 3) then the spell would be cast on yourself.

[Emonik]

In scenario 1, you mention cure is cast on your <t>, so you do have a valid target.
If your target was a monster or something you cannot cure (like in scenario 3) then the spell would be cast on yourself.

OK I get your point, even if i think it's a bit counterintuitive. So i change the macro to

/ac "Cure" <mo>
/ac "Cure" <t>

The macro still resolves with the same 3 scenarios.
In scenario 3 instead of going to the next line and healing <t> it still defaults first to <me>.