We already have [@player] which casts a spell at your feet, and [@cursor] which casts a spell wherever the cursor happens to be at the time.
We are sorely missing “/cast [@target]” to allow us to cast a spell at the target without the need to position the reticle.
Think the argumentation agains it is related to pvp… Though it shouldn’t be impossible to disable it against other players.
On the other hand it’s also not ideal to hit targets dead centre since you usually want to hit something else standing a bit further away from them, or if they move.
All in all, it would have been a great feature for handicapped individuals who have to rely on tab targeting because they have problem moving a cursor around.
I am not sure what you mean by “position recticle” but you can always do something like this:
#showtooltip
/cast [@mouseover, nodead, harm] Shadow Bolt; Shadow Bolt
“Harm” defines that it’s enemy target and that is also not dead.
If you have a target selected, meaning there is reticle under the target or target unit frame has popped up, spell will go to that target.
If you don’t have a target selected (no reticle under target) but you move a mouse over enemy target, spell will go to that target that has mouse over.
Flexibility in this is that when you DO have a reticle under target, you can still mouse over other target. Priority is on mouse over target, so when you are not mouse overing, your spell will automatically go back to reticle target or target with reticle.
P.S: You can make variations based on harm - friendly targets, nodead, dead and similar.
The idea is to avoid positioning the cursor in the thick of the fight, where the camera maybe facing backwards or sideways, and you are aiming and shooting towards another direction. Even if the camera is facing your target perfectly, even then you’d need to position the cursor/reticle.
If the cursor is already positioned, you can then simply do “/cast [@cursor]” no need for anything cleverer.
For quicker casts you can bind the macro “/cast [@cursor] Blizzard” to say “ALT-right click”, so then you simply alt-Rclick where you want to drop the Blizzard.
As fast as that is, you still have to move the mouse. If “/cast [@target]” existed you could do it from the keyboard, similar to tab targeting, no need to use the mouse, and the camera could be facing backwards even.
Doesn’t this massively take away from the skill of using the ability? Making the fact its ground targettable at all almost pointless? @self is enough.
if i remember right they did add [@target] accidentally in 7.1 with [@player] & [@cursor], lasted about a week or two before it was fixed, was kinda fun while it lasted in pve, but caused huge issues in pvp
this was about 2-3 years ago mid legion, i remember i made some macros to see what worked & then one day they just stop’d working & my buddy who does pvp went on a mad rant about how broken it was when i asked him
One of my favorite things in gw2 was the ability to cast positional aoe abilities on targets. You basically traded the ability to set and predict aoe placement for the ease of use. Made playing some classes/weapons with tons of aoe a real smooth ride. In wow I still occasionally end up with my death and decay being cast to some tree branch or on top of the cave ceiling.
People will always complain, no matter what you give them.
There are plenty of direct AoE spells that use a target, eg
Mind Sear
Chain Lightning
Prayer of Healing
Mind Bomb
Seed of Corruption
Hand of Gul’dan
Circle of Healing
Shining Force
Outbreak
And probably a few more. All the above spells require a target, which you can easily tab to, and do not use a reticle. There is no reason in my opinion to have other spells using a reticle, it seems an arbitrary decision to me.
Therefore once more I would ask, please give us a “/cast [@target]”.
Yeah such skill involved when you D&D with the @cursor get casted into the air cause there is a root in the ceiling that count as texture.
I mean, i am okay with leaving it as it is if they stop putting texture in such annoying place, dungeon usually.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.