How to change focus with fast window switch?

[Sliceback55]

Hi all,

altough I don`t multibox atm, there`s still an issue that`s bothering me.

Some time ago I tried to combine Pwnboxers fast window switch with macros that change the group members` focus.

For example, if my main dies, I press a button which switches to my next char and puts him on focus at the same time.

F1: switch window Char1
F2: switch window Char2
F3: switch window Char3
F4: switch window Char4
F5: switch window Char5

situation: main dies (Char1), I press F2 which switches to Char2, at the same time I put /focus macros on F2 ingame on all chars:

Char1: /focus Char2
Char2: /clearfocus (alternative: /focus Char2)
Char3: /focus Char2
Char4: /focus Char2
Char5: /focus Char2

Now to the problem: the window switch works as intended, however the macros won`t activate unless I mouse-click them.

Is it impossible to put both the fast window switch from Pwnboxer + ingame macros on the same key?

I used the same method with keyclone and it worked, would be nice to see it work on Pwnboxer aswell. Hope you could follow my babbling.

Cheers!

[Ualaa]

With most boxing software, you can have both an in-game macro/command and a software switch on the same key.

So you push a single key, and the correct region becomes the main region while that toon is set as focus by all of the others, who will then correctly assist it, follow it, etc.

This was a feature request at one point, and I know prior to then you could not have switching and focus change on the same keybind.
Not sure if that is still the case, or if you've encountered an unforseen bug.

Hopefully someone who uses PB can give you a definitive answer.

[XIXEagle50AE]

I just ran into the same issue with a setup that I am working on. Does anyone know if this is "suppose" to work in the current release?

[Tim]

Hey Eagle,

The fast game switching intentionally isn't part of the keys that get broadcasted. The reason is to prevent the issue that the WoW game clients can have with a heightened likelyhood of those "run away" (key state not being correctly recognized by wow.exe) situations when the game window is switching.

What I do is this:

F12 -> Fast switch window 1
F11 -> Fast switch window 2
F10 -> Fast switch window 3
F9 -> Fast switch window 4
F8 -> Fast switch window 5

Then to set the new leader:

SHIFT+F12 -> Leader is window 1
SHIFT+F11 -> Leader is window 2
SHIFT+F10 -> Leader is window 3
SHIFT+F9 -> Leader is window 4
SHIFT+F8 -> Leader is window 5

So basically I can spend about 1/4 of a second hitting F12/shift+F12 knowing that, in the event that the WoW client lags, I can just button mash shift+F12 to make sure the leader focus is set correctly. Because if it didn't, then having F12 as both the window swap+focus key would cause huge issues if you button mashed it. Know what I mean?

So yea, it was done by intelligent design

[XIXEagle50AE]

Roger that... Thanks Tim

I have been playing around with a virtual keyboard and I tweaked it a little (after your post), and I think I got passed the button mashing scenario. The keyboard lets you set up any key, but every virtual key has to map to a physical key. So I can map F20 (for example) to "Alt+Shift+Cntl+F1" and when you hit the virtual F20, it issues an F20 but also performs the action that you map to it (in this case the "Alt+Shift+Cntl+F1"). I set the fast switch key to F20 and the /clearfocus /focus <master> macro in bindpad to "Alt+Shift+Cntl+F1". I still get the lag issue but I can do pretty much whatever key sequence I want for the virtual keyboard mapping. So in this case, I built in the button mash by setting the mapping to multiple "Alt+Shift+Cntl+F1" key sequences.

I guess my only concern would be setting the mapping to some sequence that would trigger Blizzard to think that I am running some sort of automated bot. Is that a valid concern?

[Ualaa]

As long as every action that occurs is a result of something you push at the time the action takes place, you will be ok.

Several people use a pseudo-priority system where they push a single input, and their software outputs six different keybinds with a different spell on each (or the same spell multiple times, for a weighted chance). All six (or nine) keybinds are a direct result of a user input that takes place at the time the input (key push, key release, mouse click, etc) occurs.

The only time you could have issues is if you have a delayed action. If you push something now, and can walk away from your computer and have another action take place a few seconds later, without any further input beyond the first action. For actual GM quotes on this, check out: GM Quotes - Multiboxing vs Automation

[XIXEagle50AE]

That's cool...

I do remember hearing (or reading) something to that affect. My stuff will definitely be compliant then. Thanks Valaa

[Tim]

Oh one more thing to say on this...

Just because that is what PB does now, doesn't mean that can't be changed.

Perhaps there should be a toggle, something like "Enable this to limit run-away situations" which would then disallow fast game switching to have broadcastable keys. Then, if you don't have that enabled, you can set those keys to be broadcasted?

Whatcha think?

[Ualaa]

As long as the documentation or labels are clear, or potentially you have a mouse-over for additional information...

More options are always preferable.
Someone might have a use out of a function, which makes the software even more powerful/flexible for them.

[XIXEagle50AE]

Agreed... sounds like a good enhancement.