4 box shamans running off, more common in instance runs help

[boxblizzard]

Hi,



if there is someone who had the problem where the toons run off out of control until you tell them to follow again, this sometimes gets me whiped in instance, or very imbarrising in pvp its very annoying. :cursing:



any cure to this? :P



Al

[Anahka]

Put all movement keys on DNP, including modifiers like ctrl, alt and shift. Also don't hit a movement key and then change focus to another window. And unbind or DNP autorun.

[boxblizzard]

everything u said im doing correctly, it still does it ?(

[drevil]

i have the same problem, it's very annoying :(

[Naysayer]

As far as I've investigated the problem, I've come to the conclusion that this occurs when the clones happen to follow each other. Toon 5 following toon 4 and toon 4 following toon 5 for example. They don't actually follow each other because then they'd just bump heads. When this happens the camera views (mouse turn) of the toons also rotate 45 degrees for some reason and all hell breaks loose.

When this was happening to me I quickly switched to the problem toons and noticed when I manually stopped them with wasf the text said that they stopped following so-and-so, which was each other not the main, and were running to the middle of nowhere while the camera was going bat**** crazy twisting and stopping at 45 degrees.

I've since stopped spamming my follow like I used to and have given the toons a little more time to acquire their focus before pressing follow. Before the problem stopped, I also started to believe it had something to do with melee attack mode and following. It's since stopped happening completely though, so I haven't bothered trying to figure it out any further.

[keyclone]

there is a wow bug, reproducible by hardware boxers, where the leader of the group gets hit.. and a follower will just keep running (or something like that... maybe there was a stun involved).

[boxblizzard]

i will have to agree its to do with when you hit followm last night i was doing zul'farrack, and 1 of the toons ran off down the stairs at the big fight and brought everyone up from the bottom, wiped us and ruined the entire run. not a smart move but it was'nt my move. not impressed by it, it happens more often than it used to now, i believe its a combination of problems.

We need this fixed and properly investigated, its caused so many problems in instances its very annoying. :cursing:



maybe its my macros?/everyone elses, when people combine follow with assist :S

[Otlecs]

It's a long-standing problem, not attributable to a single boxing solution, and the only genuine fix seems to be that you need to have lightning reflexes to respond when it happens!

There was a thread (http://www.dual-boxing.com/forums/index.php?page=Thread&postID=12739&highlight=%22the+run+aways%22#post12739) a long, long time ago which attempted to establish a common reason for it, but didn't really come to any conclusions (although there's still some useful information in there).

[pmellyn]

I had this same problem on my 4x Shaman, as soon as I would see it happen, I would have to spam my follow macro to keep trying to follow my main, and would have to do to each window and move forward, back, autorun on off, I could never figure out what triggered it or what actually made it stop, I would have to fiddle with each character. I had my autrun, and QWEASD on DNP as well as a few other keys. Haven't had the problem in awhile, ut lately been playing my druid warrior, running only 2 wow's.

[Otlecs]

I could never figure out what triggered it or what actually made it stop
In my case, I'm convinced that the "key up" event is occasionally missed - it only ever happens to me when I'm hitting a broadcast movement key, such as a formation.

The fix is to hit the same key again.

[drevil]

In my case, I'm convinced that the "key up" event is occasionally missed - it only ever happens to me when I'm hitting a broadcast movement key, such as a formation.

The fix is to hit the same key again. yes, this is the exact problem.

and it happens very often for me, also on attack keys .. i'm still trying to find a solution.

[Zub]

i've been having this problem as well, and it seems it's always when i use my formation (which i often use just to break /follow)

Basically with my 3 toons, the formation key is '\' (backslash)
This is bound to DOWN on my main, STRAFELEFT on clone1 and STRAFERIGHT on clone2.

Seems sometimes clone2 decides to run forward instead. looks like it receives AUTORUN instead of STRAFERIGHT basically.

From memory it's always the same clone that runs like a fool.
Pressing the follow key (backspace in my case) usually bring him back if i'm quick enough.

i had the one time when he would turn and run back, but continue to run past my other toons until i pressed follow again, then turn again and run past us again etc.

[keyclone]

out of curiosity... do you have 'strict' checked or unchecked in your do-not-pass list?

[Zub]

out of curiosity... do you have 'strict' checked or unchecked in your do-not-pass list?
No idea. The default i guess
will check tonight.

[Fizzler]

In my case, I'm convinced that the "key up" event is occasionally missed - it only ever happens to me when I'm hitting a broadcast movement key, such as a formation.

The fix is to hit the same key again. yes, this is the exact problem.

and it happens very often for me, also on attack keys .. i'm still trying to find a solution.Bah that dang avatar you are using messed me up. We found a rotten apple under the couch that had small little bite marks consistent with the 2 year old. We sent it off to CSI for a full investigation. Anyways we have been killing these tiny little flying bugs the last few days and they keep landing on my monitor it looked exactly like your avatar. I have swiped at the screen a few times already.

[drevil]

out of curiosity... do you have 'strict' checked or unchecked in your do-not-pass list?
setup:
single machine, win xp
do-not-pass: [x] strict [x] white-list

for example:
party stands, i press "control+a" for small movment to the left,
they start running ... until i press "control+a" again, other keys don't help.

[Anahka]

out of curiosity... do you have 'strict' checked or unchecked in your do-not-pass list?
setup:
single machine, win xp
do-not-pass: [x] strict [x] white-list

for example:
party stands, i press "control+a" for small movment to the left,
they start running ... until i press "control+a" again, other keys don't help.

That happens to me if I switch focus to another WoW while holding the movement keys. Seems to happens more when using Octopus.

[keyclone]

ahhh... one way you can get can a 'run-away' is when you are using 'strict'... which was implemented for backwards compatibility.

basically this is what is happening:

let's say you put W on your strict do-no=-pass(DNP) list.
when you hit W, it is blocked. but, if you hit shift, control, or alt... THEN W... that is not blocked and allowed through.
in wow, if you have nothing bound to shift/ctrl/alt + W, it will use just W and move your character

so...
shift down
w down (allowed through since it is shift+W)
w up (allowed through since it is shift+W)
shift up

this is allowed.. and shift+W will move forward. BUT, what if you let go the shift first...

shift down
w down (allowed through since it is shift+W)
shift up

w up (BLOCKED... as it is just W)


notice that wow never got the W up... and in wow, down == go and up == stop... you get no up to your characters.

UNCHECKing strict will block all forms of W and this won't happen

(i hope that babble-fest made some sense)

[cheeseprophet]

Nice reply, but why are there posts here of people that only have one toon running? (the ZF guy)

[Prepared]

Nice reply, but why are there posts here of people that only have one toon running? (the ZF guy)It's because WoW has a bug that sometimes makes a key that is for movement continue to be pressed. I've seen it a few times before I started using any kind of keyboard boxing software. (I started using keyboard programs like Keyclone way late relative to when I actually began boxing). The problem with WoW wasn't always there however. It started some where around 2.4.0 patch. My belief is that whatever that bug is, Keyclone replicates it to the clones. It maybe that WoW internally is treating the keystroke as an ALT, CTRL or other such combination in conjunction with the actual key pressed. Whatever it is, WoW has the problem but Keyclone replicates it. Finding the actual key combination that is doing this is a b....h. I'm not using Keyclone because of this bug. It still happens with the other key replication software I'm using, however it only happens on one of my characters which is the WoW problem, not the key replication software problem. Until there is a solution to Keyclone stopping the replication of the bug in WoW, I can't use it. I wish there was a fix for it because I am registered with Keyclone on several machines and I use it for it's terrific maximizer function but I shut it down after it has started the maximized windows of WoW.

[drevil]

shift down
w down (allowed through since it is shift+W)
shift up
ok, i see the problem :-)
thanks for your fast reply.

so my workaround for now is:
1) strict off & whitelist on, adding "control+a"
2) wow ingame keybind: main bind "control+a" null, slaves bind "a" null & "control+a" left movement

[cheeseprophet]

Nice reply, but why are there posts here of people that only have one toon running? (the ZF guy)It's because WoW has a bug that sometimes makes a key that is for movement continue to be pressed. I've seen it a few times before I started using any kind of keyboard boxing software. (I started using keyboard programs like Keyclone way late relative to when I actually began boxing). The problem with WoW wasn't always there however. It started some where around 2.4.0 patch. My belief is that whatever that bug is, Keyclone replicates it to the clones. It maybe that WoW internally is treating the keystroke as an ALT, CTRL or other such combination in conjunction with the actual key pressed. Whatever it is, WoW has the problem but Keyclone replicates it. Finding the actual key combination that is doing this is a b....h. I'm not using Keyclone because of this bug. It still happens with the other key replication software I'm using, however it only happens on one of my characters which is the WoW problem, not the key replication software problem. Until there is a solution to Keyclone stopping the replication of the bug in WoW, I can't use it. I wish there was a fix for it because I am registered with Keyclone on several machines and I use it for it's terrific maximizer function but I shut it down after it has started the maximized windows of WoW.Ye ok, just maybe it was not the problem so i thought let´s ask :)