Can't cast spell with mouse buttons while hovering over raid frames

Support Bug Report
1

After much messing around, I finally figured out how to work around this problem, but the problem is still there. I will try to explain it as clearly as possible. I use a lot of mouseover macros for things, so I thought this might have been a macro API ussue, but then I found it being a constant problem with a regular ability that I don’t have in a macro.

Also, AutoSelfCast is enabled, so if I cast a regular non-macro heal, like vivify, that is bound to the mouse button, it should default to myself. If I hover over my own portrait, the ability will not go off until I move it away. The same goes for if it’s in a macro with mouseover in it.

I use the stock UI and don’t use any addons that mess with frames.

How to replicate this problem:

  • On my monk, I have thunder focus tea on my action bar. Any other spell will do this as well, but this is how I noticed the problem
  • The action bar button is bound in the interface settings to mouse5(this bug happens on all of my other mouse buttons like middle mouse) under the secondary bindings column
  • If I hover over raid frames or my character portrait and press the mouse button, the ability will not work
  • If I move the mouse cursor away from the frames and press it, it will work normally

The work around:

  • I removed the mouse5 binding from WoW
  • Within my Logitech mouse options, I bound the mouse button to the keyboard button (8 in my case)
  • The ability will now work while hovering over the raid frames or character portrait

Can this please be fixed so that I don’t have to rely on an external program to remap my mouse buttons? I have a friend with the same issue, except he has a generic mouse that doesn’t come with fancy software for rebinding.

3 Likes
2

This is a fundamental engine limitation, and has existed since at least as far back as patch 1.12 since I recall isolating it while Blackwing Lair was still worth running. To that end I’m fairly confidant it’s deliberate (even if not specifically intentional) functionality, rather than a bug.

Basically the game engine interprets mouse buttons first and foremost as mouse buttons. The only variation they have beyond that is having MB2 (right mouse) used for context menus, starting auto attacks, and “drop” abilities or items - that’s all. You can even select a spell to cast and assign a target with it using MB3, MB4 or MB5, instead of MB1, just that most of the time you’d never think to do so.

As you’ve found, changing to any non-mouse button function externally will let you use a button on the mouse as it might seem like you should. Addons can also bypass this behaviour, at least in part - Clique can be used for mouse-over casting on buttons assigned to mouse button functions, though I seem to recall this only works on unit frames.

Beyond that, however, you’re at the mercy of the base game itself. And the base game treats all mouse buttons equally.

4 Likes
3

You present no evidence to back this up. Why shouldn’t they fix it? They made the engine. It’s not a third party engine. They could fix it.