Look 64bit probably isn't enough in itself. It would be nice but that's not everything. There are a lot of potential factors that probably help blizzard come to a conclusion regarding an account, most of those only matter in the case of player reports and not a blanket detection. Some day they might decide it's worth it, but I wonder if they can get a ROI on it, so many botters have lifetime keys and the game is old. It would be a nice thing to have, but it isn't a miracle bandaid that solves all our problems. If I was starting out now building a bot I'd probably go 64bit and avoid click-to-move and keep everything clientside (offline bot) just to keep people happy, and I'd like that, but it wouldn't make it safe at all.
definitely dont think there will be a rebuild, since its still in 32 bit which shows that they do not care. But I am done botting until a 64 bit version comes out.
Must have been detected a while ago and saving up a list of users as I haven't been on wow or botted in 2 weeks as my time had ran out and also got banned.
I actually just reactivated my account and botted for 2 days. and was caught in the banwave. so.. it was detected
you didnt answer how adding more ip range makes any difference if they know how to find the ips in the first place
We all now blizz scans outside its mem, (read ToS, read some articles on internet) so why don't start with the basic most obvious EASY fixes: - Add ability to rename the .exe in process list - Change the hash code - Remove the friking description "Honorbuddy" in tasklist - Remove the name in the windows titles, done. Did i miss any easy fix? Add your own, pray bossland reads it and implements its, this shizzl is done in like say 30 mins progging? Got some time left, do the more difficult ones ;-) Don't say its IP based, its not. I'm running bot on computer A, clean account on computer B, they go past the same router, thus same ip for the internet world. Account on computer A is banned, account on computer B is still happly running.
I think most people understand this. Please keep up the good work and don't get disheartened. There are a lot of things the community would like and might make them feel more at ease though, and that might be worth some consideration going forward (where feasible), but hopefully the majority understand.
do you know that for a fact or are you just spouting buzz words that you dont understand the meaning of
Guess he just repeat bullshit. Even if hb would goes "rootkit" level (means not working as ring3 in usermode -> it would work as "driver"), it can be detected(several antich[ea]ts already take over that section and secure it). But, heads up bossland, we all know that this can happen, sadly it happens, reverse, investigate and bypass and everyone is happy again.
rename the process, rename the .exe and do add some mini line of code that u get another hash for your HB folder / .exe RIP HonorBuddy