Again, no such thing happens.
The client sends movement update packets to the server, server sends back "ok, you're here now". That's all there is to it. CTM just causes the client to do periodic updates as it moves closer to the "clicked" point. The reason I said it was more "precise" is that it automatically faces the clicked location. So that's one less thing to deal with. While we can obviously face a specific angle (we do this already), CTM just means 1 less call to do so. As far as the server is concerned, there is *zero* difference between WASD and CTM. Period.
Also, there's no such thing as an "idle" coordinate. You'll rarely (if ever) catch HB stopping movement while it's running a path. It stops when it has to do something on some object (which the distance is randomized for stopping), so that's about as "human like" as it can get. You have a max tolerance (aka; the distance at which you can interact with something) to a certain object. Anything inside that, is within human error range. It's quite unlikely that Blizzard is tracking, or even able, to track that.
The client doesn't do any sort of calculations for tracking anything. Only the required things for CTM (which is just a line-based thing to keep you moving towards your click point, that's it). So, please stop trying to make things sound worse than they are. If there was something they were doing on the client, we'd know about it. We're very tenacious about seeing what things do before we implement them in the bot.
