Quote Originally Posted by 'Fuzzyboy',index.php?page=Thread&postID=162747#pos t162747
It's happened a lot to me lately, probably due to the increased lag I've been having the last few weeks, which my be related to my local ISP. One of my slaves will randomly just start running (although usually I can hit the follow key before he gets out of range which fixes it). Although I only mousestrafe, and it's happened often when not strafing, so I'm not sure what causes it. It happens both with keyclone and ahk, so I think it's probably something related to either the game or the way keypresses are sent to the windows, but I doubt it's a bug in keyclone/ahk unless they would happen to have the same implementation :-)
Totally latency based. It seems from my observations that the clone
recieves the spread out command but it either conflicts or overrides
with the "leader your following just stopped moving command" and thus
the clone moves to its position but keeps moving forward.

So my conclusion is that its server side error. The server doesn't return the command that the leader has stopped (it would be a stop moving command) and omits that command and instead gives the spread out or strafe command and then acts like the leader is still running (because it ingored the command that the leader has stopped). If Blizz changed the priority from stop follow, then strafe. We would just notice that sometimes our toons dont spread out correctly.

Its actually good programming on Blizzards side, we are just the exception. Normally you would want the toon to do what we command it to do first. In this case we want it to do what the leader (from a single player perspective this is not what "they" want it to do" before commanding it to do what other /follow /party commands it recieves. I think its an easy server side command fix but I doubt well get the visibility. All said like I always though Keyclone is perfect, and blizz is broken :P