So I’m not really new to the game but every macro I use is a copy/paste from what someone else made. I’m currently trying to make a movement macro for my Worgen Rogue where a regular click is Sprint and Shift+Click is Darkflight. What I have is:
#showtooltip
/cast [nomod] Sprint
/cast [mod:shift] Darkflight
and this doesn’t work. Can someone please tell me how I can make this macro work without changing keybinds?
First off, I would recommend that you edit your thread and move it to #guides:ui-macro section of the forums. There you’ll find more assistance with this issue.
Second, personally I would use
#showtooltip
/cast [mod:shift] Darkflight; Sprint
Just moved the thread over however that macro does nothing when I click it as well.
This is going to sound perhaps condescending and pedantic, but the biggest mistake that happens is forgetting to actually move the macro to the bar.
Does the icon change when you hold/release the shift key?
No it’s just the icon I selected. Nothing happens when I interact with it in any way
Check your keybinds to see if you already have a shift key assigned to that key.
Example: Macro placed on 8. Shift+8 is assigned to another keybind so just unbind it.
Note: your original macro would still work. But the one I gave you is more condensed and will avoid showing question mark icons on the macro when you hold down Ctrl or Alt.
Select the ? icon and try it.
If it does NOT change, verify that you have the MACRO on the button, not the SPELL. Believe me, I make that mistake all the time myself.
Also, make sure the button in question is not bound to the Numpad-5 key and that you’ve not bound it to one of the Blizzard Keybinds by accident.
Yeah I don’t have shift + anything bound atm and it’s definitely on the action bar. I’m pretty certain the verbiage is the problem.
#showtooltip
/cast [mod]Darkflight;SprintTry that. It should work with ANY modifier key. That’ll eliminate any issue with the shift key (unlikely that is the issue, but let’s shotgun this thing).
What key is it bound to. That’ll help a little as I can check for defauilt bindings that you might not be aware of.
There is nothing wrong with your “verbiage” at all other than it’s a tad inefficient from a coding nerd perspective.
It should be working.
That it’s not means we have to look at other things.
I typed that in exactly as you sent it and the button does nothing no matter where I place the macro. I’ve tried taking it off my main action bar and putting it on the side bars and that doesn’t work either. The only keybinds I have are my 1 through = corresponding to the 12 buttons on my gaming mouse.
Does Sprint work if you just hit the button on the mouse?
Yes. And I can even type a macro for just sprint or just Darkflight and that works too
Ah. Okay. Sometimes those are NUMPAD 1-0 and ±, not the normal 1-0 and ±.
Hmmmm.
Shift and numpad does not work well.
Try it with ctrl or alt and see if the icon changes (assuming you have the “?” icon chosen - at least for diagnostics, you should).
Yes I’m using the red “?” It changes when I type something simple like “/cast Sprint” but when I type anything about a modifier it goes back to the question mark.
What gaming mouse do you have. I’ll look up the default key assignments.
Razer Naga
There are a number of Razer Naga mice. Is it the Naga Hex?
How many side buttons?
If it’s the “Hex” version, make sure you’re not in NUM mode (that maps the 6 buttons to numpad 1-6).
If it’s the 12-key version, open the configuration software and make sure the keys are mapped to 1-0 plus and minus NOT NUMPAD 1-0 NUMPADPLUS and NUMPADMINUS.
They produce the same characters when you type or do data entry, but they’re different hardware events and they’re not interchangable. You may need to remap your buttons.
Verify by moving the macro to the bar (again, I know) that the macro is actually there.
Then press the button you THINK fires that macro and see if the button highlights. If it does, then try it with ctrl, with alt, and with shift. It should work for all three.
IT WORKS. Thanks so much for your patience.
Any time. That’s why were’re here. 