Benninger
Member
- Joined
- Apr 22, 2010
- Messages
- 457
Well, it is called "honor"buddy - I supposed it was used toWas it ever used in a pvp?

Well, it is called "honor"buddy - I supposed it was used toWas it ever used in a pvp?
These theories must be great entertainment for the developers. It's like someone going up to NASA and sharing their theory that the moon might be made of cheese, you are so far away from the truth it cannot even be called wrong.
So to be clear, as your tripwire did'nt catch the event, you actually have no idea what you have to modify too prevent it again?
The tripwire didn't catch the event because it was set to look for a different thing (a potentially outdated thing) and wasn't reset to look for the right thing. So they do know what they need to change to prevent another hit.So to be clear, as your tripwire did'nt catch the event, you actually have no idea what you have to modify too prevent it again?
That's why its a Theory and not a fact. Can u show me a better Theory that can explain why some get targeted and banned while others dont? And I dont mean Ban Waves. I have ran test using honorbuddy and reviewing the ban section. Bottom line we all know the risk with Botting and its been said over a million times dont bot on an account u dont want to lose.
Haven't u seen Transformers?humm did they ever reached the moon well am in limbo still![]()
They're not forcing you to use their software go elsewhere.
Just my two cents
well said
For me Tripwire was always the biggest marketing gag of Bossland. It is in my eye just the message when Authservers are taken down. Nothing more and nothing less. People laughed at me when I told them that. Your message just proves to me that this is indeed the case. Come on, a failure in your config? It is obvious that you won't say you got caught again, you want to sell your product - fair enough. But tell us it was a config mistake is a poor joke and a lie in my eye.
Maybe you did not even change something since may - milking the cashcow of your business. Blizzard will just wait, ban again next time and you are gonna tell us "Blizzard changed something / improved warden/ the new patch was the reason of..." and one day blizzard will win and you finally go out of business. Until then you will tell us stories to find people that pay your salary.
Still thank you for your bot - I enjoyed HB but it has come to an end already in may.
Sorry if this may sound harsh, but it is my opinion.
Btw: I got banned in may and did not bot anymore with HB and my account is untouched... HB is detected that is a fact for me...
Furthermore, your "open trusty communication" is for my none. Bossland did open a thread about SB and the leaked source and said he will answer questions. Well my question is still there if other products are at risk.
Just my 2 cent.
Thanks Tony and the rest of you guys. I've had honorbuddy for almost 6 years now. In that time I've only had 2 bans and 1 6 months suspension (which occurred the other day). I'm not one of those people that bots on more than 1 account at a time, but I have been dumb enough to AFK BG's and stuff in the past. There's no denying that blizz doesn't have a way to detect honorbuddy, but I fully believe the Tripwire system has saved my butt a few times. As with Warden, we don't know the specifics of what Tripwire is capable of. You KNOW that if you attach a BOT or inject any kind of LUA code that's against the ToS that you are vulnerable to a suspension/ban IMMEDIATELY. You are out of your damn mind if you come here complaining about Honorbuddy. 32/64 bit, click-to-move, HB properties, "i've been a blah blah blah for 40 years"....no one gives a shit. You don't know anything about what they are doing to protect botters as best as they can. And as far as banning arena's and BG's goes, it won't make a difference. If you've actually played you can tell when someone is botting. Not even professionals are so good that they can do an opening sequence or burst rotation perfectly every time, which every CR strives to do. So sit back, relax, drink some adult hot chocolate, and wait for the next release. We all know you're going to download the newest release as soon as it's available. Thanks again Buddy team and Merry Christmas/hanukkah/Kwanzaa or whatever holiday it is you'll be celebrating
Edit: Tomorrow is officially my 5 year (HB) anniversary.
Think you missed the part about "strives to be". Either way, you can still tell, especially when it tries to use an ability/item multiple times and you get stutter animation. I've also been top DPS many many many times before even when I wasn't as well geared as others and using a class that's generally "weaker" than others. DPS is dependent upon more than just rotation. Placement, timing, and cooldowns are all integral to having the best dps.i wouldt mind if the crs did put me on top dps but they most certainly do not ( user of millz warlock routine and tunha ret paladin routine both are far from perfect )
Think you missed the part about "strives to be". Either way, you can still tell, especially when it tries to use an ability/item multiple times and you get stutter animation. I've also been top DPS many many many times before even when I wasn't as well geared as others and using a class that's generally "weaker" than others. DPS is dependent upon more than just rotation. Placement, timing, and cooldowns are all integral to having the best dps.
Well I won't argue against that. I honestly think that paid routines in the store have stunted progress on updates. The only one I can think of that has updates on a very regular basis is one I'm pretty sure I can't mention here on the forums (it's a rogue CR).nothing to do with the fact routines are never updated !![]()
Honorbuddy was recently hit with another banwave.
We have spent the last two days trying to figure out how Honorbuddy was detected.
After the May banwave the Tripwire service was made a lot more aggressive to catch
any detection methods that it might have missed. However, having reviewed the server
logs, it was discovered that Tripwire service was not running properly after an update
that took place about a month ago which nullified all the new heuristics.
We do NOT know for sure what caused the banwave, but we strongly believe the tripwire
service would have been able to catch the detection that took place if it was working
properly.
Words cannot express how sorry we are for this mistake, but we are truly sorry. We
take your account security very seriously and strive to do everything possible so
that this exact situation does not occur.
We now plan for the service to run for a while with these checks configured correctly
and see what it shows. In the meantime we will update you when we are ready to re-open
auth and to do a test release. Please be aware that this release will still be considered
'unsafe' to use and, like always, should not be used on accounts you cannot afford to lose.
Again, we sincerely apologize for this massive mistake.
This thread will remain open for discussions.