Because the same packets are sent whether you're using CTM or WASD to move. This is publicly documented information. Not to mention, we have more of WoW reversed than most people. (In fact, we probably know more about the client than most actual WoW developers, which is quite sad) That said, if it was an issue, we'd work around it. But again, it's not an issue, so there's nothing to worry about.
So all these bans were about reports and not them actually finding out something about HB and pathing?
Thanks for the reply Apoc. It is appreciated from someone who is actively working on the code. I understand where you are coming from in there being no difference. With that out of the way does it seem at all plausible to you that they are recording idle coordinates and then checking for successive usage of those coordinates? You did say that CTM is much more precise. That is my concern here. Trajectory mapping can be automated and a tolerance level used to set up a flag for any number of reasons (uptime, away uptime, reports, etc). For obvious cpu crunch reasons I think this would be client side.
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.
Apoc can you please tell us what might be causing the recent increase in bans since mop? If not player reports, what kinds of things do you think their "security systems" can track? I consistently get instant perma banned within 1 week from using gatherbuddy but only 72 hours for questing profiles. A lot of the bans just have to be automated so what are they detecting?
Furyzor maybe people with over 20 accounts have been banned before and their IP got flagged by Blizzard, that would make sense. Also if you've gotten banned a lot before I think you've raised suspicion.
OMG... it's so easy to link your botting accounts together it's not even funny. Stop blaming HB unless you know for sure you're using a different IP, MAC, HD, etc. for every client. They don't say anything about guaranteeing safety with running 5 clients on the same computer all gathering.
I'm not trying to flame or anything, but there are clearly a lot of people that would like an annoucement from anyone, saying yes or no, but the case it's that they don't even talk about it.
Ive tried buying a new pc and new internet connection and got the same result. Other accts on the same pc/ip that only use questing dont get hit but sometimes get a 72 hr days later
hmmm i think the way you are botting is importnat. questing isnt that bad as spamming the AH ... thast my opinion. if someone will report me as botter. i thikn a 72h ban is possible. i ever heard that blizzard is more looking for farmers than questing bots. i think wow will be free2play in 2014 and bots will be normal se Jadedynasty they have an build in bot and its pretty nice to use. so why shouldnt BLizzard do it too?
This is the post with the most speculation I've ever read. >Blizzard looking for farmers instead of questing bots >Questing isn't as bad as spamming the AH >72h are possible if someone reports you as a bot >WoW will be Free2Play in 2014 I have never ever read a thing like this before.
well nothing is impossible ..... i have read so many in this thread here and some was good some bad ... and now i just give a new these here ...
The free to play part may be possible, but there's been no mention anywhere from a credible source so it's pure speculation.
Shh, you're supposed to be staying "completely silent" on this. How are people going to justify complaining otherwise?
Botting too long. I have 4 accounts and I am fine. I found a great range and Blizzard doesn't bother me.