Troublesome.5670

But the select mount with mousewheel doesn't send anything to the game nor interacts with the game at all, it store a variable within the script. But even that is a 1 to 1 cycle. 1 click of mousewheel = 1 variable. Just as default is zoom settings, 1 click = 1 level of zoom adjustment. "Why don't you bind every mount to its own, fixed mount key in the game options?"That's what I'm doing, I'm just sending my choice to a single key based on which variable I want. In other words, I'm using the in-game mount binds. I'm just choosing which bind I want to press use the mouse wheel.Basically all it's doing is rebinding the mouse scroll wheel since the game does not support it yet.

I recently made an AHK (autohotkey) script that uses mouse scroll wheel to cycle through a selection of my in-game keybindings (such as Numpad4, which is my bind for Raptor mount) and saves that selection as I stop on it. This doesn't send any keystrokes to the game yet, just saves the selection to memory.It then takes this selection and binds it to another key for mount/dismount.It also throws an overlay up letting me know which current bind/mount my selection is on. So I can choose which mount I want to select (still not sending keystrokes to game yet) ,then press my dynamic mount/dismount key (which sends the appropriate saved keystroke to the game) to call that specific mount. Since It is only actually sending one keystroke to the game whenever I wish to mount or dismount, it doesn't violate the one press-one key rule.So it should be safe to use, yes? Just wanted to be sure before I used or shared this with anyone! Thank you in advance!