With the release of pre-patch, /cast [@mouseover] Spell macros are broken for healing and damaging abilities. The default behavior no longer functions as expected with and without Auto Self Cast, Self Cast Key, Press and Hold Casting, or Enable Action Targeting each toggled.
Prior to DF pre-patch, the macro with that one line would work on 3D world targets only, and not try and target you or your selected unit.
Before DF pre-patch: You are 45 yards from the target your mouse is over, but have the unit in front of you targeted, and hit your binding. You are met with the Out of Range message as expected. The spell does not fire on the undesired target.
After DF pre-patch: You are 45 yards from the target your mouse is over, but have the unit in front of you targeted, and hit your binding. Your spell files on the target selected that is close to you. The macro does work again if you move within range of the mouseover, casting on the mouseover target. The issue being if the mouseover is far enough away it fires the spell on current target even though the conditional is set to be strictly @mouseover.
There is a strange grey area with this; if you are ~37 yards away from a target and the spell is 35 yards (so close to being in range), it acts like it used to sometimes. Because of this oddness, I believe the issue is related to the Enable Action Targeting system that has been built. As it seems to be firing on the unit you have targeted because they are in the range of what would be the actionable target and the mouseover is far enough that it’s over some threshold.
This happens with both healing and harming abilities, and completely breaks my oh snap taunt macros and multiple other pull macros where many people depend on /cast [@mouseover] Spell.
This was reported during beta and not addressed, and isn’t even listed on the known issues thread unfortunately.
2 Likes
Some further testing done and I can confirm it is directly related to the Action Targeting system. I toggled action targeting on and off to see where it starts to automatically target something and it lines up with exactly where this bug occurs.
This testing was done on the target dummies in Org. The ones on top of the gate that are all in a line. Target 1 is on the far left, Target 2 is far right.
Testing was on a druid with 40yd range on Moonfire.
Target 1 is within action targeting range.
Target 2 is out of range entirely (greater than ~5 yards out of range)
With action targeting off, select Target 1. Go to a spot where both targets are out of range, but Target 1 is closer, and begin to walk toward them. Be using your @mouseover macro the whole time on Target 2. As you hit a point where Target 2 is about 46-50 yards away and target 1 is within range, the spell will fire on Target 1 instead of giving you the expected Out of Range. When you get ~45 from target 2, it’ll switch to saying Out of Range again and stop firing on Target 1 before ultimately firing on Target 2 when it’s in range.
Note the exact spot you are standing in when it starts firing on Target 1. Now turn on Action targeting and step further away from Target 1 so that nothing is targeted any longer. Slowly walk toward it while spamming your @mouseover macro over Target 2. Action Targeting will select Target 1 about 1-2 yards before the exact spot the macro you noted earlier, then it start firing on Target 1 again (because it’s target).
In both of these situations, when Target 2 gets to ALMOST in range of your spell, you get the Out of Range message you would have expected to get the whole time. Looks like some grey area around 40-45 yards for a mouseover where that takes priority again over the action targeting system.
Easiest way to see it is what I posted in the first post. Select a target right in front of you, try and use a @mouseover macro on something 45+ yards away. Fires on your target. This was just me figuring out some specifics to hopefully point Blizz in the right direction. Action targeting breaks mouseover macros, even when off.
This happens on live and on beta, with no addons loaded.
2 Likes
This issue is still present and now in current content with other players is very noticeable. It also has an impact on healing macro’s that user @mouseover targeting and just target your character when your mouseover is just slightly out of range. It’s very jarring.
1 Like
I came across this thread while doing a Google search for this exact issue. I’m aware that it’s an old thread, but this still has not been addressed. Thanks to the OP for all the testing. I hope the time they sacrificed to report this in such detail is not wasted.
+1 This also happens with explict target macros (@ or target=). Very annoying behavior.