@cursor spell setting?

Since prepatch I’ve been having issues with reticle spells casting as if I have an @cursor macro set up during combat. Like I’ll go to cast capacitor totem and it just instantly drops on my cursor when I’m expecting the reticle to pop up so I can click where to drop it. It’s kind of inconsistent and I can’t always tell if the spell went off or if I was just pressing it while I was still waiting for the previous gcd to end and it’s frustrating.

Is this some kind of setting or a bug? Is anybody else having this problem?

Check to see if you made an @cursor macro. If not disable all addons to see if it’s one of those causing it.

1 Like

Didn’t they also add a setting recently to automatically cast spells at cursor?

I ask because I don’t have any addons or macros, but my spells all cast @cursor by default.

#showtooltip Teabag
/cast [@cursor] Teabag

You actually don’t need the “Teabag” for this particular macro, since the /cast is already specifying “Teabag”. In fact, most macros don’t need to specify an ability name, unless you’re using one ability to represent every action in a /castsequence.

#showtooltip Teabag
/castsequence reset=combat/10 Teabag, Fartblossom

I use a few that are setup similar when the actions are simultaneous, like for my Druid Bear, I’ll use Wild Charge and Moonfire in one macro. Moonfire will fire all the time, and Wild Charge will fire when distance and CD conditions are met:

#showtooltip Moonfire
/cast [@focus, harm, nodead] [@mouseover, harm, nodead][] Wild Charge
/cast [@focus, harm, nodead] [@mouseover, harm, nodead][] Moonfire

I use the Moonfire tooltip specifically in this case since the macro reads from top to bottom, left to right, so the actual macro would show Wild Charge all the time, but Moonfire is the primary function.

1 Like