UnderratedPost
Member
- Joined
- Dec 18, 2015
- Messages
- 362
dude I USE HONORBUDDY FOR 8 10 years this is just a new forum account i know how to bot retard tripwire doesend protect us noob why would my accounts bee banned evrytime il bot and not without bot i tested this i botted i got banned within 3 4 days and i only quest botted and when im playing legit i never get banned so they know when we bot.
I think blizzard is trolling you if you get banned in 3-4 days

Now I have to disagree with you there, In December rapphus/hawker admitted tripwire failed and were so sorry for the accounts lost and even went as far as they stuffed it up and they had to update it for it to catch the way Blizzard caught them in May/December. Come on buddy LOLHB took off servers offline or manually hit tripwire themselves to stop as many accounts as possible it's all there in black and white disagree all you want next time I'll repost the text and links from there post(s).
True about they have other way of getting people but those two banwaves were due to detection HB team admitted it and with how Tripwire fail read statement in December![]()
Like I said they updated it in December to be more aggressive or smart which it did catch out Blizzards way of the last 2 major detections which HB admitted caused them and plugged it. Then we saw most of those accounts that were flagged banned a short time later we they also said but was really minor they did not even take auth serves offline during it being so confident and minor.
Also for 64bit who knows we won't go into that since HB is not apart of it or else we can speculate all day![]()
no you misunderstand it, how you misunderstand it I don't know because it is so simple. the tripwire did not fail in december IT WASN'T EVEN RUNNING, they messed up but that could happen to anyone, sure it's annoying but I would rather be banned because of a mistake than because the tripwire was running and didn't work properly, think about it! the only time tripwire failed was the first banwave in may, and they updated it after that. sure it took until recently to work out what caused the banwaves but do you think it is easy or something? we should give big props to them for working it out (or rather for tripwire working it out

right now we are as "safe" as we were before may banwave, that is a fact and anyone who denies it doesn't understand the situation.
and to give you proof this is from the official Buddy wiki:
[Tripwire Fail] On 13-May-2015, Tripwire failed to catch a new Bliz spyware mechanism causing the 13-May-2015 Honorbuddy ban wave. Due to this event, Tripwire heuristics were significantly broadened and strengthened.
A second banwave happened on 16-Dec-2015. However, we do not count this second banwave as a Tripwire failure, since the root cause of the problem was Tripwire was not running as designed due to some internal code mis-handling in another subsystem. We are quite confident that had Tripwire been running as designed, the second banwave would've never happened. On 12-Jan-2016, our confidence was vindicated when the unmodified Tripwire codebase (properly running as designed this time) caught the Bliz spyware's attempt to use a new detection mechanism.
Last edited: