WoW - IsBoxer Keymaps occasionally become "corrupted"

I put corrupted in quotes because I don't know if it's actual corruption in a programming sense. Here's my story:

I've got a typical 1 Pally 4 Shaman set up I've had since WoTLK. I quit boxing after hitting 85 in CATA and repeatedly failing in heroics, but restarted boxing for MOP. I've updated Isboxer to the latest build, rebuilt my macros to a priority system a la dual-boxing.com, and 98% of the time everything works flawlessly (in terms of the software, not the user).

However - I have the following issues:

1. Whenever I load my team up at the start of a play session, my mouse repeating portion of my Earthquake key doesn't work. I press 0, and 0 gets pressed on my slaves, and the targeting reticle shows up on each slave window corresponding to the position of the mouse pointer in my main window at the time I pressed the key, HOWEVER - the mouse repeater stops at that point and I can't move the reticles or transmit a mouse button click to fire the spell. I then go back to isboxer, and export to innerspace, without making any changes, and the key functions perfectly.

2. Occasionally I will see a slave either stand idle, or repeatedly casting the wrong spell during DPS spamming. Sometimes it's a spell with a WoW keybinding similar to the one I want sent, such as Shift + 2, when I'm really spamming my keyboard's 2 key so ISboxer will send out the 4 WoW keybindings I use in my priority setup (Alt Num 1 through Alt Num 4). Sometimes the spell she's casting repeatedly has nothing to do with what I'm pressing, such as one toon spamming her chain heal macro (Shift + Logitech G510 G11 key), while I'm spamming Keyboard 2 to send out WoW Keybindings (Alt Num 1 through Alt Num 4). I then go to IsBoxer and export to innerspace without any changes, and the key functions perfectly and the errant slave falls back in line.

3. Occasionally my burst DPS macro ( Alt + 4 on the keyboard) correctly sends my priority WoW keybindings to the tank, but my slaves sit idle, wasting my Ascendance CD, rather than IsBoxer sending "6" to them. An IsBoxer export to innerspace also fixes this issue.

4. Sometimes, despite being fixed, these issues seem to magically reappear during the same gaming session. I have taken to exporting isboxer to innerspace at the start of every gaming session to try to get everything lined up properly, but each of the above issues seems to work its way in there at some point during a typical 4-5 hour session.

Here is my isboxer config pastebin: http://pastebin.com/E2VYte5v

Thank you in advance for taking time to look at this. I hope I have been descriptive enough above. If any additional info is needed, I'll be happy to provide what I can, but I am no programmer.

Side note: I haven't seen Jafula being as active on dual-boxing.com lately. Has there been any thought/discussion of collaborating to get some of Jamba's functionality integrated into IsBoxer's add-on, in the event that he stops developing Jamba? I hope he never stops working on it, as his contribution to the community cannot be overstated, but multiboxing without IsBoxer + Jamba would be like eating a PB&J without the J.

[lax]

Which Character Set, specifically, are we talking here? Your config has 3, and it will make a difference in my answers... I'm going to assume "Pally4Sham".

Here's what sticks out to me in your config.

A. You made copies of Activate Maps and Activate Repeat seemingly for alternate hotkeys (G510-MR and G510-M1). These copies unfortunately don't synchronize correctly with the other windows. (This will cause unexpected behavior as you switch windows.) You should delete the copies, and instead right click the originals and select "Create Alternate Hotkey", then assign Hotkeys to the generated alternates. The new alternates will do the original Mapped Key via "Do Mapped Key Action" to preserve all of the original behavior.

B. All of your Key Maps are going to be activated when you toggle Key Maps off and then back on. Every single one. FTL DPS Keys, Horde DPS, and Custom DPS -- all of which assign Hotkeys to 1 through 0 -- will all be activated, and each of them will be attempting to do their assigned behaviors. So when you turn key maps off and then on again, and then press 0, it's going to do FTL DPS Keys 0, it's going to do Custom DPS 0, and it's going to do Horde DPS 0. And the Send Next Click from the Custom DPS 0 and Horde DPS 0 may break each other. So that's why your key maps get "corrupted": because you didn't mean for all of them to be enabled.

The reason they are all going to be activated is because that's what your "Activate Maps" key says to do. It says to turn them all off in Step 1, and then turn them all on in Step 2. So that's what will happen! There is a feature in ISBoxer that will prevent the "wrong" Key Maps from getting loaded by the "wrong" teams; see the FAQ: I added a new Key Map but the Key Maps toggle does not disable it?, particularly the part 2 paragraphs down that starts with "If you have new Key Maps for different teams, that would conflict with the others (e.g. because they use the same Hotkey)" and this will tell you how to solve this problem.


After fixing those two things I think you'll be okay. Let me know

Awesome. Thanks for the rapid response. I had no idea that key maps could become activated for character sets to which they weren't assigned. That's very good to know. I will make these corrections when I get home. At some point I plan to convert to the Pro config, so hopefully that will help protect me from myself.

Thanks again.