Is HB over forever?

[Billythekid]

Is Honorbuddy coming to an end or are we gonna try to get back in the game?

 

[xsilverdicex]

No....HB devs need to work out what was actually detected, and use a new method...then botting will be fine until the next banwave.

 

[razer]

but to find out how it was detected will take a while and they are still not 100% sure that it was this or that. Rewrite the whole code in 64bit new system new private bot

 

[frosticus]

id surely pay for a new key, a 64b key, if one were introduced.

dont get me wrong, ill patiently wait for 64b, but if it were decided to make a 64b instead of updating to old, i wouldnt be real mad if they charged a bit for it.

 

[Mario27]

but to find out how it was detected will take a while and they are still not 100% sure that it was this or that. Rewrite the whole code in 64bit new system new private bot

and i bet blizzard already knew how to detected it but kept it stil low to not use it or els we would be gone even quicker

 

[namook]

but to find out how it was detected will take a while and they are still not 100% sure that it was this or that. Rewrite the whole code in 64bit new system new private bot

If I was them I would be rewriting the code in 64 bit take every measure possible, everyone knows honor buddy only works in 32 bit, that is one thing that will have your account looked at.

 

[lolp1]

but to find out how it was detected will take a while and they are still not 100% sure that it was this or that. Rewrite the whole code in 64bit new system new private bot

I find it a bit unlikely that rewriting code to 64 bit would have much impact one way or the other in terms of preventing future detection, unless there is some reason I'm unaware of(could very well be!) the detection method used would be null if tried on 64 bit users, such as something like checking the call stack far enough back to see calls from outside of WoW being impossible on 64bit but not 32.

It's more likely to me if any time consuming process takes place, it would be re-writing their anti-detection tools to further avoid the new detection method(s) and any anticipated methods not used yet but deduced as possible in the future from this detection method used. It all remains to be seen.

Funny enough, in 5.4 they added some detection for lua related stuff that looked to be targeting HB. Then in 6.1.0.(19702) they re-added a similar detection method for 32 bit clients, and that check was caught by their tool tripwire and HB updated shortly after thinking to have protected its self against the attempt. It seems some sort of trickery has occurred on blizzards end for this current detection and figuring out what that was will possibly be a very tedious process, and re-writing tools to anticipate possible future detection methods not previously thought about could be equally as tricky.

I'm a big noob really though, and am just curious to see how it goes.

 

[namook]

I find it a bit unlikely that rewriting code to 64 bit would have much impact one way or the other in terms of preventing future detection, unless there is some reason I'm unaware of(could very well be!) the detection method used would be null if tried on 64 bit users, such as something like checking the call stack far enough back to see calls from outside of WoW being impossible on 64bit but not 32.

It's more likely to me if any time consuming process takes place, it would be re-writing their anti-detection tools to further avoid the new detection method(s) and any anticipated methods not used yet but deduced as possible in the future from this detection method used. It all remains to be seen.

Funny enough, in 5.4 they added some detection for lua related stuff that looked to be targeting HB. Then in 6.1.0.(19702) they re-added a similar detection method for 32 bit clients, and that check was caught by their tool tripwire and HB updated shortly after thinking to have protected its self against the attempt. It seems some sort of trickery has occurred on blizzards end for this current detection and figuring out what that was will possibly be a very tedious process, and re-writing tools to anticipate possible future detection methods not previously thought about could be equally as tricky.

I'm a big noob really though, and am just curious to see how it goes.

64 bit would still be a lot better, from my perspective it's compatible with things such as Tmorph ;D but come on everyone knows that most people who run in 32 bit are going to be the majority who run a bot of some description.

 

[Skavi]

I suppose it would be a good thing if devs added some more randomisation into the bot. Like randomised interval between using spells (since blizzard analyse logs, though it's probably CR related task), randomised hotspots (as far as I know the mesh system "shows" the bot where he can go through and where he can't but for some reason several bots always use the same path) and stuff like that.

 

[lolp1]

64 bit would still be a lot better, from my perspective it's compatible with things such as Tmorph ;D but come on everyone knows that most people who run in 32 bit are going to be the majority who run a bot of some description.

It's not a viable option to ban from simply having a 32 bit client and not 64 bit running, in my eyes, only if it is tied to the detection method being only viable in 32 bit but not 64 bit. 32 bit client is a totally included and approved for use with WoW, used by a large enough number of legit users to make detection for that alone pretty much totally unrealistic.

I suppose it would be a good thing if devs added some more randomisation into the bot. Like randomised interval between using spells (since blizzard analyse logs, though it's probably CR related task), randomised hotspots (as far as I know the mesh system "shows" the bot where he can go through and where he can't but for some reason several bots always use the same path) and stuff like that.

It is known for a long time Blizzard has used forms of detection related to specific sub-scripts created for bots and not bots themselves. I find it unlikely this had anything to do with this ban wave, out side of possibly targeting a wide range of included HB scripts/plugins/bot bases successfully at once.

 

[namook]

It's not a viable option to ban from simply having a 32 bit client and not 64 bit running, in my eyes, only if it is tied to the detection method being only viable in 32 bit but not 64 bit. 32 bit client is a totally included and approved for use with WoW, used by a large enough number of legit users to make detection for that alone pretty much totally unrealistic.



It is known for a long time Blizzard has used forms of detection related to specific sub-scripts created for bots and not bots themselves. I find it unlikely this had anything to do with this ban wave, out side of possibly targeting a wide range of included HB scripts/plugins/bot bases successfully at once.

I think you will find over 60 percent of 32 bit users are bots, that is why honor buddy is running 32 bit and not 64 bit, I know many asian gold farmers will be using low end computers they are out to make money not spend money, I understand what you are saying but making everything 64 bit would be a good thing overall, it will force everyone to transition to 64 bit and less traceable, as GM I would be looking at accounts 64 bit or 32 bit I know honor buddy doesn't run on 64 bit we can rule that one out, so now they only have to check x amount of accounts. Virtually making honor buddy under a 64 bit program will make it slightly harder to detect since you then can't rule out one platform.

 

[TheDrGonzo]

I can think of about 20 flags HB causes right now. then all it takes is a GM to watch your screen for a minute or two. (yes they have the ability to see what you see, like when a Shadow Priest mind controls you) I've been guilty of running bots that are casting spells that aren't even on my action bar.

 

[Owneth]

THIS post is VERY viable HBDev's!!!

Think about the simple logic.

You run a 32bit client in a world that's becoming and is mostly 64-Bit when it comes to OS/Programs.

It's time to rewrite HB in 64Bit please.

How stupid are you to dispute this?

 

[lolp1]

THIS post is VERY viable HBDev's!!!

Think about the simple logic.

You run a 32bit client in a world that's becoming and is mostly 64-Bit when it comes to OS/Programs.

It's time to rewrite HB in 64Bit please.

How stupid are you to dispute this?

What would you suggest caused detection for 32 bit users only that could not be applied to 64 bit clients? Simply using 32 bit alone is no grounds for a ban, it is a current supported, blizzard produced, legitimately used client many people use for non bot reasons. For 32 bit to be considered the real issue we would need evidence to suggest any detection method would be impossible or too unpractical on 64 bit clients as well.

 

[Mario27]

i think hb wil be gone to when glider got detectedthey where gone to same happened with pirox bots i gues it wil be over but i dont know for sure.

 

[namook]

What would you suggest caused detection for 32 bit users only that could not be applied to 64 bit clients? Simply using 32 bit alone is no grounds for a ban, it is a current supported, blizzard produced, legitimately used client many people use for non bot reasons. For 32 bit to be considered the real issue we would need evidence to suggest any detection method would be impossible or too unpractical on 64 bit clients as well.

Your missing the point no one argues the difference between detection methods on 64 bit or 32 bit, but it will make it a lot harder, since blizzard will have to check all 64 bit accounts opposed to the one percent who will then only use 32 bit, at one point blizzard disabled 32 bit from the settings but all us botters then made accusations we could not play the game effectively so they placed a 32 bit under the settings, the majority of those who complained were 32 bit botters simply because the bot ran under 32 bit. We could still run under the 32 bit client however it was just not in the settings, blizzard then patched it back into the game. The whole point I make is if everyone is under one os 64 bit you then have to look at multiple accounts, legit players then your finding legit players are banned also, then we could easily appeal accounts, running under 32 bit really is a dinosaur approach, 64 bit will have many more positives for the most part though, people will just have to upgrade their shitty computers.

 

[umshakalaka]

i think hb wil be gone to when glider got detectedthey where gone to same happened with pirox bots i gues it wil be over but i dont know for sure.

You're so horribly wrong on so many levels I don't even know where to begin...

1. Glider got detected multiple times, they were never "gone" because of that. They got closed after losing case in court against blizzard.
2. Pirox never got detected, they closed because blizz threatened them with court, it was at exact same time they threatened HB, which was followed by court case with bossland / warping it up with pirox.

 

[namook]

You're so horribly wrong on so many levels I don't even know where to begin...

1. Glider got detected multiple times, they were never "gone" because of that. They got closed after losing case in court against blizzard.
2. Pirox never got detected, they closed because blizz threatened them with court, it was at exact same time they threatened HB, which was followed by court case with bossland / warping it up with pirox.

@ umshakalaka I just laugh at these guys statements they take quite a lot out of context, people think a tripwire even will kill honor buddy, christ how many trip wires have we had now lol?

 

[mb41375]

Hurt blizzard where it hurts them most. Since they tried to hurt us. Don't buy new accounts. get the word out to everyone

 

[lolp1]

Your missing the point no one argues the difference between detection methods on 64 bit or 32 bit, but it will make it a lot harder, since blizzard will have to check all 64 bit accounts opposed to the one percent who will then only use 32 bit, at one point blizzard disabled 32 bit from the settings but all us botters then made accusations we could not play the game effectively so they placed a 32 bit under the settings, the majority of those who complained were 32 bit botters simply because the bot ran under 32 bit. We could still run under the 32 bit client however it was just not in the settings, blizzard then patched it back into the game. The whole point I make is if everyone is under one os 64 bit you then have to look at multiple accounts, legit players then your finding legit players are banned also, then we could easily appeal accounts, running under 32 bit really is a dinosaur approach, 64 bit will have many more positives for the most part though, people will just have to upgrade their shitty computers.

Agree entirely 64 bit would be more convenient for today's standards, but it would not offer much improvement for the task HB is actually written for, botting. I'm not so sure the work to do so much R/E work needed for a project as big as HB would be worth it. HB developers seem to think not, unless needed for other reasons that have not yet existed.