Confused on chaining multiple layers of targets

[Lax]

One thing I will go over real quick is that "All druids * all healers" (in terms of the tables above) is going to have each and every druid tell each and every healer to press a key. Not druid healers. There is a few ways to get that, though. An ATG specific to druid healers being the most obvious, but you can also do it with the two separate ATGs. Here's a useful trick: Send a Mapped Key State Action to all Druids to enable a Mapped Key (that everyone else should have disabled), then use a Do Mapped Key Action that targets healers. Or vice versa. Only the windows that have the Mapped Key enabled will be able to execute it, and since you're having Healers try to execute it, you're effectively limiting it to the intersection of Druids and Healers ATGs.

Now don't go complaining that all of the above isn't documented


As far as setting up your DPS mapped keys. What I do is set up my Mapped Key for each archetype (e.g. i have a mapped key for each of the 3 Paladin trees), and everything that Mapped Key does has Target=Window:Current. So if I want only one, two, or however many of my ret paladins to DPS, I can control that from the Do Mapped Key end. Secondly, a lot of my main DPS keys and even some of my situationals are virtualized. What that means is I can use a single Do Mapped Key Action, to perform the main DPS key in whichever set of windows I want, without specifying "hunters" or "paladins" etc as part of it.

To do that, I have one set of "master" mapped keys, and each of these masters has a Hotkey. Then I have a set of Mapped Keys that serves absolutely no purpose other than to be the Target for the Do Mapped Key Actions. They have one step, but it's completely empty. They do technically serve a purpose, these are what will happen if the Mapped Key is not virtualized for any given Character. (Another way to think of this feature is "mapped key override.") So that means I could put a Popup Text Action, or even a Sound Action, in these Mapped Keys to get an indicator that it's not virtualized and I need to fix one of the Characters.

To set up the virtualization ("override"):
1. select a Character in the top pane
2. click Virtual Mapped Keys in the left pane
3. Set it up so that it reads something like "DPS in Some Key Map is now DPS in Hunters Key Map". You can click and drag a Mapped Key from the top pane into the boxes on the bottom right, which means you do not have to click the < and manually select from drop-down boxes in a popup window.
4. Click the + to add one, there's an X to remove one.

As the Virtual Mapped Keys editing pane explains, when used via Do Mapped Key Action or Click Bar, it will override the mapped key on the left, with the key on the right. That's done on a per-Character basis when the instruction to execute the Mapped Key is received from the source window. This virtualization also helps when mix-and-matching your teams, like grabbing a shaman to use in place of a druid, etc. That can be done by dragging into a slot in your Character Set. (Note that I'm intending to simplify that in Joe Multiboxer)

[pinotnoir]

My head hurts from reading that. I am thoroughly confused.