Furthermore, if you try to CMD + Tab to switch windows with “Disable Keyboard Shortcuts” enabled, you can’t. You’re stuck unable to tab out of World of Warcraft.
Anyone else experience this on Mac?
On a M3 Macbook Pro.
7 Likes
Yeah I have this exact issue as of the pre-patch. I noticed because I have CMD+’ mapped to my alternate mount and that stopped working.
When I enabled the “Disable OS Keyboard Shortcuts” option, the CMD+’ now properly triggered my keybind, but CMD+Q still quit the game. So, I’m at a loss.
5 Likes
I play a healer and had CMD + Q bound to a raid cooldown before the pre-patch dropped, and never had problems with it until the pre-patch released.
Imagine my surprise the moment my client quit mid-raid when I hit the hotkey I needed.
I don’t know what to do outside of rebinding that key to something different for the time being.
5 Likes
I use CTRL+Tab as a keybind and have for years–it used to be what the game read as the input for the front-most of the thumb buttons on the Steelseries Cata Mouse; it’s worked for years. Prepatch bricked that command too.
(CMD+Q is Ice Block for my Mage… now I call it Ice Quit)
4 Likes
Same issue here. I actually thought my client was repeatedly crashing until I noticed one time that I had just pressed ⌘Q. Q and E are my strafe buttons, and I often use ⌘ as a modifier for action buttons. Needless to say I won’t be strafing left until this gets sorted out.
Update: Somewhat of a temporary workaround is to use BetterTouchTool to assign ⌘Q to nothing or something different (for the WoW app only). That won’t let you use the key combination for something else, but it will at least prevent you from accidentally dropping out of a raid at a critical moment.
1 Like
This is rather odd since CMD-Q is not ever supposed to work as a Quit function for WoW. In fact, thus far WoW has been set to use CMD-OPT-Q to quit, not CMD-Q precisely to avoid unwanted termination of the game client. The easiest explanation for this is that for some reason the .nibble file used when making the app’s baseline UI was either replaced with a default one (which has CMD-Q enabled) or that particular option was inadvertantly re-enabled in the file. Either way, if the UI compilation files are the culprit then a fix should be pretty easy to come up with on Blizzard’s end.
2 Likes
Could this also be related to the disabling of CMD-` and CNTRL-Tab?
A fix is being worked on. I don’t have a great ETA yet on when the fix for this will go live, but it’ll likely be the build after next (not including the one that went out today).
The binding for quit accidentally changed from <cmd+opt+q> to <cmd+q> in 11.0.0. I’ll restore the old behavior and add a config option to disable the binding all together on the off chance anyone wanted to use <cmd+opt+q> for something.
5 Likes
Oh good to hear, thank you Rommax.
I’d reassigned, in Mac OS, CMD+Q to screenshots; this to prevent accidentally closing my client all the time. It wasn’t an ideal workaround.
1 Like
I’m hoping this will also fix using CMD as a key modifier for ` also… it’s working in other cases without issue; I use CMD+A for Consecration, Immolation Aura, and a few other things and that’s all fine. Thanks as always!!
This pretty much aligns with what I figured it was. Thankfully among the myriad issues making folks’ heads spin this was probably the easiest to deal with.
1 Like
To be more exact, the code was converted from using a .nib file to using NSMenuItem calls programmatically and the fact the nib file used a non-standard hotkey mapping got overlooked in the conversion.
1 Like
Was the non-standard mapping one originally created for WoW, or was it the default (i.e., Apple ignored its own standards)?
1 Like
As far as I know, the mapping was made up for WoW.
1 Like
Gotcha. So it was just an inadvertent change. Thankfully it was a trivial fix relatively speaking.
1 Like