Printable View
I have a mapped key with a WoW macro action. The macro casts Sunfire. The hotkey for the mapped key is 3.
On my action bar I have slot with Solar Wrath that is bound to 3. When I press 3 I cast Solar Wrath. If I remove Solar Wrath from that action bar slot, then I cast Sunfire.
I thought InnerSpace did not pass hotkeys through to the client. So I don't understand this behavior.
Take this with a grain of salt since I lack actual technical knowledge in how it all is setup but my understanding of how it works is as follows:
When you create a macro in ISBoxer, you are required to give it an individual key combination. Exporting to innerspace will create the same macro with the assigned key in the config for the ISBoxer addon, which is how it is then usable in-game by simply sending that keybind. There needs to be keybind that ISBoxer can send because you can not really have a program injecting (probably not the right word ) actual actions to the game client while staying within the TOS/EULA.
I've ran in to some similar things where I've had conflicting binds on my bars. Unbinding them, changing the bindings to match or removing the spell from the bar slot should all suffice as fixes/workarounds.
Unless you unassigned it, disabled it, or didn't set it up (by default, it's configured for you), then "3" is already attached to a Mapped Key in "Combat Broadcast Hotkeys" that (eventually) sends "3" to all the game clients. So, I'm going to assume you're pressing "3" and both executing a macro, as well as sending "3" to the game clients. I don't know if this is the case since you did not share your profile along with your question, but if it is, then the simple fix is to either disable, or unassign the conflicting Mapped Key/Hotkey.Quote:
Originally Posted by sync00
Yup. I thought I had unbound all those keys. But it turns out some were still bound.Quote:
Originally Posted by MiRai