Log in

View Full Version : [ISBoxer] Two Keymaps, one wont work [FIXED]



Multibocks
11-11-2009, 01:23 AM
Im having trouble getting this to work (side note: F*ck vehicle combat)

MapA: DPS/healing map for instances

MapB: Vehicle Combat map for F(*&(&*(&(*!! ToC.

Now long time ago when I ran this on my shaman it worked. Fast forward to a new team and this doesnt work anymore.

When I turn off MapA and turn on MapB (via toggle switches) the friggin map doesnt work. (I learned from Lax you can type bind -list in the console to tell you what IS is doing.) IS clearly says that it loaded the map and the keybinds are all there. Yet nothing happens on the slaves. I dont get any errors, they just stand there. I just want to get the stupid sword for my tank in here and move on! HLEP!

edit: Ok I fixed it and it seems to be a limitation with ISboxer or IS itself. You cannot use the macroing in ISBoxer if you need to use the same hotkey for a vehicle. Let me give an example:

key 2 was used on my dps map for dps/tanking and I made all the macros in IS (no reason not to, there is plenty of macro space)
key 2 is also the shield breaker ability in ToC

No matter what I did key 2 always tried to cast my macro. EVEN IF I HAD THE MAP OFF. It didnt matter, so they wouldnt cast shield breaker and would try to cast macro'd spells which arent any use on mounts.

THE FIX: Moved my macros from IS for key 2 to the ability bar key2 in WoW. Instantly everything started working as intended. Im kinda sad that I have to put my macros in WoW for keys 1-4 (typical vehicle keys) since IS has a much larger macro text limit. I guess I will live though. Oh and I cleared ToC Heroic this morning with the brute force method (Heroism in p2, focus knight down and then strafe away from ghouls)

Multibocks
11-11-2009, 06:23 PM
Ah cmon someone has to know...

Ualaa
11-11-2009, 11:28 PM
I'm using something similar to this for my Eclipse.

Keymap A does one thing.
Keymap B does one thing.

You can have the same Keymap A across a lot of toons.
And the same Keymap B across more toons.

Each toon (if you want to change independently) needs their own Keymap C.
Or if they will all change at once, then they can share a Keymap C.

Keymap C has two steps.
On Step one, it enables Keymap A for toon A (or group A) etc. and disables Keymap B for the same toon/group.
On Step two it does the reverse.

Two steps, one for on and another for off, seems to be much more reliable then a toggle.

If a keymap loads but doesn't do anything, I'd guess the keybinds are in conflict with something in wow.

Fizzler
11-11-2009, 11:57 PM
I saw your coinfig........ we need to convene a think tank of intellectuals to figure it out :)

Multibocks
11-12-2009, 12:02 AM
lol that was you =)

Never thought of using a toggle keymap that alternated between my two keymaps, brilliant!

Multibocks
11-12-2009, 08:21 PM
Ok so I reconfigured:

MapA: dps map
MapB: vehicle combat

MapC: one button that toggles Map A and B on/off like this -

1: MapA on, MapB off
2. MapA off, MapB off
3. MapA off, MapB on

I had to add the second step or I couldnt type (I use a lot of keys around awsd for keybinds)

Here is the not so hilarious part. I got them to cast shield up to 4 stacks and then I misclicked outside of WoW window and now it wont work anymore. Only the main guy casts shield. So pissed off right now, wtf is that? I checked my keybinds in WoW and unless leaving 1-10 bound to the action keys is doing it... then Im at a loss. I love IS and ISboxer, but this is just bullshit.

P.S. I watched in the console and verified the loading and unloading of maps works, so its not that!

Multibocks
11-12-2009, 08:30 PM
ok I changed the keys I was using to call the vehicle commands (I was hoping that using the num pad would clear up the problems) back to 1-4. This made 4 useable by all (that key is only bound to mage) but GDI 2 is still not working (that is my dps button.)

Multibocks
11-13-2009, 01:54 PM
Found a fix, see original post. Would rather keep macros in IS, but I guess its not too big a deal.

Lax
11-13-2009, 02:04 PM
ISBoxer can't override Action Bar bindings, and does not put macros on your Action Bars -- it is designed to only make temporary changes to WoW, so you can play without ISBoxer and not be inconvenienced by the changes it made. Sorry :)

The "fix" for this is to continue using 2 (for example) for your Hotkey (what you push), but change the Key Combination for the WoW Macro Action to something that ISBoxer can use. It can be as obscure as you want, most of mine are like ctrl+shift+alt+Q (something I'll never press)

Multibocks
11-13-2009, 02:36 PM
hmm I was under the impression that when you changed maps it changed keybindings.

edit: wish you would have mentioned this when I was in IRC chat the other day, save me 3 hours of logging in and out trying different things =(

Lax
11-13-2009, 03:11 PM
hmm I was under the impression that when you changed maps it changed keybindings.

edit: wish you would have mentioned this when I was in IRC chat the other day, save me 3 hours of logging in and out trying different things =(
I'm not sure how what you just said relates to what I said, which is probably along the same lines as why I didn't mention this in IRC. Had I realized you were trying to make WoW Macro Actions with the Key Combination set to an Action Bar button, I might have told you to hit the ? next to Key Combination, which explains that you can't use Action Bar buttons as the Key Combination.

So back to this...

hmm I was under the impression that when you changed maps it changed keybindings.
When you change Key Maps, it is not making any changes in WoW. All WoW Macro Actions for any given Character while a are stored as WoW Macros, and bound to keys. This happens when you log into your character, when the ISBoxer Addon loads. The WoW bindings will stay that way until you log out. WoW will not let ISBoxer override the key bindings used for your Action Bars, so in actuality, a WoW Macro Action with the Key Combination set to 2 is precisely the same as a Keystroke Action with the Key Combination set to 2. It can't change what 2 does, but it's still going to press it.