For anyone who didn’t see, for a bit there this past week, we had the ability to use @target in our macros using conditionals:
This was quickly fixed, and no longer works:
However, as you can tell by the comments in those articles, as well as Reddit and even General Discussion - this is a horrible thing to do.
Targeting Reticles are, by their very nature, an accessibility concern, as I’ve brought up before. I have shaky hands that can jerk at times, and I’ve ended up placing my Wild Spirits, Rain of Fire, Efflorescence, etc. on the wall, on the floor nowhere near anyone, etc. before because of it.
For melee characters, I can use @player, but most melee characters don’t have targeting reticles for dps reasons, just utility reasons.
There’s also the issue that people without accessibility issues bring up about them constantly - terrain in WoW clips horribly. You can go to place your reticle and suddenly your healing rain is on the ceiling, unable to reach anyone. You somehow placed the reticle under the environment, thus still, not hitting anyone.
@Target is something that needs to be added to the game. Being able to use @player has been around for years, and it’s hurt no one, and no one has complained.
There are concerns about @target in PvP - specifically for CC skills like Freezing Trap and being able to cast it on targets off-screen.
However, this is another case of PvE (and accessibility), suffering because of PvP.
Why can you not just make it so the @target macros don’t work when targeting players with specific spells? Like, allow things like Healing Rain, Efflorescence, etc. to do it, but not things like Capacitor Totem or Freezing Trap, for instance. Even a blanket disallowment in PvP would work until proper coding can be made to do something like that - PvE players shouldn’t have to continue to suffer over it.
And for the very few instances in PvE where people found a way to exploit an @target macro - fix the mechanic, not the macro. For instance, halls of atonement last boss, if a warrior used @target heroic leap, it let them absorb all 4 beams as they landed directly on the boss. This could easily be remedied by a simple hotfix to the boss mechanic and how beams are absorbed.
Please, add an @target conditional to the game baseline. If you have to, disable it in PvP until you can find a way to make it so only certain spells will work with @target in PvP.
Especially with the knowledge that Evokers will have targeting reticles, this is very much needed.