[WoW] Understanding Key Maps and Mouse triggering

[TRoN]

I've been digging trough my ISBoxer configuration and I've been getting very stisfactory results. But there's something very basic that messes up with my playing that I still finding the right way to get it working as I want. That has to do with Mapped Keys and how ISBoxer works when broadcasting to the game windows. Here's an example (this is actually part of my main problem):


In all my teams I always have a designated healer ready to HEAL when needed. But in most cases he don't need to heal at all and I want him to DPS. So I made a toggle key that sets HEALER DPS Mode ON/OFF.

HEALER DPS Mode ON is:

I press 2 -> everybody receive 2

HEALER DPS Mode OFF is:

I press 2 -> everybody except Healer receive 2,
Healer receives CTRL+SHIFT+,

How I did it:

I have 2 ATGs: Healers and DPS

Configured default 'DPS FTL 2' key to send 2 to all DPS
Created a 'Healer DPS FTL 2' key that receives 2 and send 2 to Healers
Created a 'Healer HEAL FTL 2' key that receives 2 and send CTRL+SHIFT+, to Healers

When I press 2 it sends 2 to all DPS and it sends 2 or CTRL+SHIFT+, to the Healer depending on if HEALER DPS Mode toggle is ON or OFF. And this is working great!

The problem begun when I added a 2Step DPS toggle to the '2' key so when I press 2 -> 2 -> 2 -> 2 it sends 2 -> CTRL+SHIFT+- -> 2 -> CTRL+SHIFT+-

(based on Mercurio's idea here: http://www.dual-boxing.com/showthread.php?t=32633)
I really like this alternate broadcast method and it opens many doors to implement some interesting stuff.

Back to the point, the 2Step thing brought a new functional condition: When Healer is on HEALER Mode, I don't want him to use 2Step.

So:

I created another key, '2Step FTL 2' that receives 2 and broadcasts 2 then CTRL+SHIFT+, to DPS group.

The 2Step toggle switches between 'DPS FTL 2' and '2Step FTL 2' also 'Healer DPS FTL 2' and 'Healer Heal FTL 2'

This is working but I don't know it's the right way to go.


Now the real problem

I've alway played assigning my MouseWheelDown to key 2. Since ever, rolling down the wheel is spamming '2'. And that's the way I like it

Before the Healer and 2Step things I had a copy of the 'DPS FTL 2' key with MouseWheelDown as hotkey and that worked like a charm. But now, do I need a copy of each of my new 'receive 2 and sent whatever' keys and assign it MWD hotkey?

Or is there a way to configure globally 'MWD is 2!'.

I just can't get things togheter. Or the 2Steps don't work or the Healer don't heal or the Melee IWT stops responding or the talent pane (N) opens and, mostly, it lags like hell (I think because some broadcast feedback is occuring). I've tried several different approaches and nothing seems to get it right

My logic was. I just need to create a key map in General that receives MouseWheelDown with 1 step with the following 4 actions:

Do mapped key DPS FTL 2 -> DPS
Do mapped key 2Step FTL 2 -> DPS
Do mapped key Healer DPS FTL 2 -> Healers
Do mapped key Healer HEAL FTL 2 -> Healers

But that leads to something weird and out of control.

Using the key '2' is working.
Using MouseWheelDown is total chaos!

Can you help me with this, please?


It would help a lot if I could understand what InnerSpace does, step-by-step, when processing (for example) this:

Do mapped key DPS FTL 2 -> DPS

Beeing:
(DPS FTL 2 = FTL Assist me -> self; 2 -> all; Mellee IWT -> self)
(Melee IWT = Step 1. CTM ON; send WoW IWT key -> Melee. Step 2. CTM OFF)


Thanks in advance.
Best regards
TRoN

[lax]

Do Mapped Key Action is going to send an instruction to each and every window that is part of that ATG, and tell them to do precisely the same thing as if they had hit the Hotkey to activate the Mapped Key themselves. This means that instead of being like you press 2 in the current window, you are making it like YOU press 2 in each window. Each one is going to tell all of the others to assist and press 2, just like the mapped key was designed to do.

In other words, because your original DPS Keys are meant to affect other windows, they are still going to affect other windows when you use them via Do Mapped Key Action as opposed to via the Hotkey. If you want to limit those to your ATGs, you will need to modify the original DPS Keys (either to send to that ATG, or to send only to Window:Current). You should only send the Do Mapped Key Action to the windows that you want to act like you hit the Hotkey in each one. That'd be Window:Current in most cases.

[TRoN]

Thanks for your answer!

"You are making it like YOU press 2 in each window. Each one is going to tell all of the others to assist and press 2" is pure gold to me It explains why toons become confused. Every toon is telling everybody else to assist HIM and press 2 and this causes the mess and recurrent behaviour lagging everything.

I'm going to study and test this new knowledge and try to fix the problem.

I had a simple question that could help me to better understand Mapped keys behaviour but I think I can answer it by myself now.

When IS processes

DO Mapped Key X -> DPS
( being X: 2-> all)

who receives 2? DPS group or all?

The answer is all (and num_of_DPS_members times) because each of DPS guys are sending 2 to EVERYONE. If this is right I got it all!!

[TRoN]

Just need to know another thing:

a) When I press a hotkey, ALL the mapped keys associated with that hotkey will be processed and then the result sent to their targets?

or

b) When I press a hotkey, that keystroke is sent to each window and then every window processes the hotkey keymaps? (I'm talking about a simple Keystroke action here)

If a) is true, my MouseWheelDown fix will be:

Mapped Key - MWD is 2 (one step, 4 actions)

Do Mapped Key DPS FTL 2 -> self
Do Mapped Key 2Step FTL 2 -> self
Do Mapped Key Healer DPS FTL 2 -> self
Do Mapped Key Healer HEAL FTL 2 -> self

if b) is true, my MouseWheelDown fix would be:

Mapped Key - MWD is 1 (one step, 1 action)
2 -> all (I've tried this one and it doesn't work)

So option a) should be the way to go. Right?

It's very important to me to understand the mechanics of this. It will make any further configurations a breeze.
Thank you very much for the support.

[TRoN]

FANTASTIC!! This is working. Everything is working like it should now! I'm so happy!!

Now, a key map tunnel BEFORE InnerSpace process keymaps would be awesome. I let it here as a suggestion

If I could say a key (or mouse button) transforms into some other key AND THEN process keymaps like the hotkey is the 'new transformed key' that will be brilliant because, for example in this case, I would just say 'MouseWheelDown transforms into 2' and everything was set.

Now I have 'MWD is 1' to set* and probably a lot more fancy things
and that makes me have a lot of actions to be executed in EACH 'MWD is whatever' and keep toggles sincronized.


* Normally I use my ActionBarBUT1 to single target sequences, and ActionBarBUT2 to AOE sequence. I have a SINGLE/AOE toogle (my MouseBt4) and I just spam the WheelDown to cast the sequence I've chosen.

[lax]

If you want to transform it, look into Mapped Key Virtualization

http://isboxer.com/forum/viewtopic.php?f=14&t=233

The different ways of using this are:
* Select Virtual Mapped Keys in the bottom left pane of any Character or Character Set (selected in the top pane), and you can transform any Mapped Key that is used via Do Mapped Key into another Mapped Key.
* Mapped Key Virtualization Action can change the virtualization tables for any characters dynamically.

[lax]

Alternatively in this case, you can set them both in the same key map on the same Hotkey, then in the Advanced for one of the two Mapped Keys you can set it not to load when the key map loads. This means it will be inactive, but can be turned on with a Mapped Key State Action. A Mapped Key State Action can also be used to turn the other off at that time. Set up a third Mapped Key with its own Hotkey, that turns one on and the other off, in each of 2 steps.

[TRoN]

If you want to transform it, look into Mapped Key Virtualization

http://isboxer.com/forum/viewtopic.php?f=14&t=233

Man! This is SUPER!! I remember a few days ago, when I was installing ISBoxer and configuring my first set, I've looked on that topic and, understanding zero, I said "better come back to this later, maybe I can make some use of this...".

Well, now, for what I understood just reading the example use cases, Mapped Key Virtualization will put me on other level of multiboxing my teams. It's total control!! Can't wait to get home and do some testing (I'm at work now ).

The Assist toon X idea is brilliant and it will be the one I'm going to work on to explore the method. Thanks again for pointing me the right paths.

/cheer