I recently got a account banned, which i got no issue with, i have been botting for 5y+ and have done it ALOT.
But when creating a new account, wow how has a 'anti-cheat' agreement you accept. I startet to read this policy and i was STUNNED!
One of the factors they use to detect a botter is as follows. Quote from their site:
If you open your process list you will neatly find "Honorbuddy" there(obviously). Writing a script that detects this takes like 20 lines of code.
The matter of the fact is, when Blizz uses this method, they could(if they wanted), ban everyone using HB the second they log in, alot more then they do. And i dont get why i, and countless more, havnt gotten banned before. So rest a sure, they know about EVERYONE botting. Why they dont ban everyone instantly, must be a matter of money, or something else.
Never the less, HB should make better security to protects its botters. Eg. let ppl name the HB process to something they often use like itunes, winamp, etc etc.
Its simply WAY to easy to get banned, from a program name in the windows process list. And should not be a big of a deal to fix.
But when creating a new account, wow how has a 'anti-cheat' agreement you accept. I startet to read this policy and i was STUNNED!
One of the factors they use to detect a botter is as follows. Quote from their site:
If you open your process list you will neatly find "Honorbuddy" there(obviously). Writing a script that detects this takes like 20 lines of code.
The matter of the fact is, when Blizz uses this method, they could(if they wanted), ban everyone using HB the second they log in, alot more then they do. And i dont get why i, and countless more, havnt gotten banned before. So rest a sure, they know about EVERYONE botting. Why they dont ban everyone instantly, must be a matter of money, or something else.
Never the less, HB should make better security to protects its botters. Eg. let ppl name the HB process to something they often use like itunes, winamp, etc etc.
Its simply WAY to easy to get banned, from a program name in the windows process list. And should not be a big of a deal to fix.
