Mapping my Razer Naga for Rift

Thought it might be interesting to others to see the problem-solving I did when mapping my Razer Naga for Rift.

At first I just used it on the number setting, but after a bit I realized I wanted a more comprehensive mapping that would work generally across all 4 classes and across the different roles I play within those classes.

So I set it to use numpad instead, and immediately came across the shift+numpad5 problem. No idea why the thing doesn’t come with a warning that shift+numpad5 simply does not exist in Windows. It would have saved me hours of google. Seriously, HOURS. Solution to that problem further on in this guide.

Decision #1:

I like using my left hand to maneuver, and the razer thumbpad for actions.

Decision #2:

Using plain, shift, control, and rarely alt, I built visible hotbars in rift accordingly. So I have four bars onscreen that correspond to 4×12 thumb keys. The top bar (alt) I don’t use many actions, so mostly just keep it as a visual reminder of cooldowns. Some actions overlap so that I always know where certain actions are – my heals, shields, and potions for example, are in the same place across multiple characters.

Decision #3:

At first I mapped my most common actions to 1,2,3 etc but then I realized I wasn’t using the full power and flexibility of the razer and remapped according to how easy it is for me to access certain buttons.

Fig 1. Lei's Framework

The first three buttons on the naga correspond to Utility/Emergency. They’re the easiest buttons for me to hit and to find on the naga. It took a bit to retrain from 1,2,3 to 4,5,6 for my Single Target buttons. 7,8,9 are for Multi Target, and 10,11,12 are for more Utility, plus the big cooldown abilities the Rift devs love to throw in those soul trees.

As you can see from that graphic, the framework will easily transfer to different classes and roles, while maintaining some standard of similarity so I always know where certain types of abilities are on my mouse.

Decision #4:

Decided to remap the keyboard along with mapping the naga. NOT doing a graphic for that one, it’s pretty messed up.

1-9 on the keyboard are bound to the hotbars just so that I can be lazy in some fights. Only reason. 0 is battlerez, easy to remember. – is to drink, because it gets tired hunting for that on a side bar somewhere. = lets me mount up. It means I always have to use the mouse for the 10-12 abilities but I’m fine with that.

Movement keys are RDFG instead of WASD, a BIG departure from tradition. However, that frees my baby finger to hit 5 extra keys easily. Q and W are mapped to two different kinds of targeting, A resets the hotbar to bar 1 in case I got fatfingered, and S is available once I figure out what to put there. Z is my vent key, pretty easy to hold down if I’m yakking away.

In addition, I can access a couple of keys quickly with my index finger – H selects my focus target, Y is an emergency heal.

Fixing the Shift+Numpad5 Problem:

Since I’m using the numpad setting, in order to get around the windows idiocy of shift+numpad5 not existing at all to assign anything to, I had to rig Autohotkey along with Rift in order to use my razer’s 5 button. For that I use [ and ] on the keyboard and juryrigged the code. In addition I set numpad5 in the razer utility to use ] instead of numpad5. I’m not gonna be using square or curly brackets to converse in a game, so I think I’m safe.

Fig 2. Razer Settings

Code:

IfWinExist Rift
{
WinActivate

; Hotkey to fix shift+numpad5 problem in razer naga by assigning it to ] and } and assigning ctr+] below

^]::[

; RP Commands

::btw::by the way
::omw::on my way
::brb::be right back

}

Hopefully that’ll save someone else 4 hours on google trying to figure it out.

Conclusion:

I love my razer! All set… now I just need to l2p! 😀

Advertisements