idc cuz $$$
It's easier to create a virus for thousands of people using one client than creating and infecting the tens of few people using another one.
This will be Blizzards philosophy to ensure that a huge base of people will get effected if they decide to continue one mans product. If you have, 200,000 people using a client, it'd be easier to target those 200,000 people than to ban the 20 using the "private hack" that a 16 year old kid built.
Not to mention it's how you use it, I'm not paying a certain amount of money a month for a automated product to play a game I enjoy to play to play it for me. I dislike a few features that the game provides that I deem "boring" so I let bots do them for me. But I won't spend hours letting them doing it for me. I've not been suspended or banned because of it.
Then if you notice, immediately after the sentence, began to receive ban ... what do you think it means? it is clear, recently the sourcecode of bots to overwatch and stolen !! who assures us that they have purposely sent the code to the blizzard, and so they were able to reverse engineering to locate this shit
The only source code leaked to blizzard was announced, which was Stormbuddy. Apoc was facing serious litigation and could not afford to defend himself, so he reached a bargain agreement in which he handed over the source for. Zwetan Letschew (owner of HB stuff), has been pretty transparent about what's happening between their company and blizzard. Please don't spread false rumors regarding corruption in the HB dev ranks.
Need a guild in the US? Visit murlocs.com
you do not ramp bullshit, sniff please even a 10 year old child understands very well that if you for hours and hours reading a book which in this case is called an offset, and try to change it rewriting it, sooner or later with the type writing you understand that it was you, and then mom blizz'll burn the account .. what they never understood and that must create a ****ing scanner that goes in harmony with the bot, if the bot uses the offset of the CTM the scanner should check that this offset is not under control ... or if they are not able to create such a thing, IDA teaches you to understand that the ****ing warden in the 64-bit exe scan only 5% of the game. .. which are offset about 25 .. simple .. that's it .. you think why they did close anthrax and lazybot? because bots are passive, because they do not read and write offsets do not use direct commands dedicated to offset these damn .. so if someone puts in check the wow exe, will not find anything ... so if something can not be found = the problem must be eliminated upstream .. so do you close the company ... and then we return to honorbuddy why do you think are still active? you were there in court when ilo judge gave a judgment? even? they can say what they want, but the reality and the blizzard that if you can not track down, makes you close
Would you enlighten us, when those 3 banwaves in the past 3 months took place, mister?
The facts are clear:
This one was 4th successful banwave, targeted at Honorbuddy in the span of the last 18 months:
May 2015 - Dec 2015 - May 2016 and now Nov 2016.
But it was 4th banwave in the whole span of Honorbuddy lifetime too ~ 6-7 years!
Meanwhile Core Developers of Honorbuddy admitted, that they have successfully countered at least 6-7 unsuccessful banwave attempts, targeted at Honorbuddy only in 2016.
Beside those banwave events above, Blizzard have demonstrated high activity on the whole botting front nowadays.
Today there seems to be a rolling Firehack and Soapbox Rotations banwave too.
Just a week before Legion launch in August 2016 there was a banwave too, which affected again the Firehack and Soapbox, so there is no ban-free bot nowadays![]()