• Visit Honorbuddy
  • Visit Rebornbuddy
  • Visit Demonbuddy
  • Visit Exilebuddy
  • Visit Hearthbuddy
  • Visit Pokefarmer
  • Visit Buddystore

[Official] October 13th Banwave

Discussion in 'Honorbuddy Forum' started by raphus, Oct 13, 2017.

Thread Status:
Not open for further replies.
  1. raphus

    raphus Administrator Staff Member Moderator Buddy Core Dev

    Joined:
    Jun 17, 2010
    Messages:
    2,103
    Likes Received:
    465
    Trophy Points:
    83
    Fellow buddies,

    As most of you have already noticed, Blizzard rolled a big banwave this morning. As far as we know, every
    single bot/tool for WoW got fully hit.

    It was already known most of the bots were already detected and that is why it took Honorbuddy more than
    a month to adapt to new detection vectors.

    Honorbuddy is not detected by the same detection vectors as other bots. Honorbuddy was partially detected
    during the first tripwire event on October 10th which have been pushed to target us directly. After Tripwire
    reacted to the new detection vector and the event was analyzed, it was assumed that only a few accounts
    would get flagged by it. However, it is clear now that it affected a wider audience.

    Here is a summary of our beliefs:
    • The new detection on October 10th was rolled out in waves
    • Tripwire was able to react only when it saw the new detection
    • As of this moment, Honorbuddy 892+ is undetected.
    Our beliefs are supported by the facts that we lost only half of the online sessions when the banwave hit, and
    people who only ran 892+ are not banned.

    Improvements are already being done on Tripwire to avoid such flaws for future attempts.

    We strongly suggest everyone to NOT use any other bots/tools as majority of them are still detected and
    to not use Honorbuddy on your beloved accounts.

    Leaving this thread open for further discussions.

    Be safe!
     
    c4melboy likes this.
  2. Aion

    Aion Well-Known Member Buddy Store Developer

    Joined:
    Jan 18, 2011
    Messages:
    3,905
    Likes Received:
    95
    Trophy Points:
    48
    Thanks for the humble stance, Raphus!
     
  3. hijaq

    hijaq New Member

    Joined:
    Sep 15, 2014
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    But there are some bans @ 892 version of hb
     
  4. Zicoth

    Zicoth Member

    Joined:
    Oct 17, 2011
    Messages:
    544
    Likes Received:
    1
    Trophy Points:
    18
    Personally was awaiting banwave few months earlier, good thing you keep bot up!
     
  5. shinavaka

    shinavaka Member

    Joined:
    Jan 16, 2011
    Messages:
    385
    Likes Received:
    2
    Trophy Points:
    18
    Just as a heads up i quit wow quite a while ago and decided to start botting last night, botted all through the night, i was not hit (yet) and will continue to bot. I have not used any other tool for quite some time as i quit raiding a while ago :p A while ago for me is around 4 months or so...
     
  6. Aion

    Aion Well-Known Member Buddy Store Developer

    Joined:
    Jan 18, 2011
    Messages:
    3,905
    Likes Received:
    95
    Trophy Points:
    48
    Me personally got all my test accs affected by the TW event, so they are banned. All other accs, not attached bots recently are safe.
     
  7. Tony

    Tony "The Bee" Staff Member Moderator

    Joined:
    Jan 15, 2010
    Messages:
    126,204
    Likes Received:
    415
    Trophy Points:
    83
    keep this thread civil plz, we have the first keyboard warrior behavior "victims" already
     
    djmag and obzzcure like this.
  8. Obvioka

    Obvioka Member

    Joined:
    Apr 27, 2017
    Messages:
    93
    Likes Received:
    4
    Trophy Points:
    8
    So the oct 10 event was the fault, then why 1 of my bot what used at the end of august last time got banned too? It wasnt even active from the end of august.
    And tell me why my fresh account what was registered at oct 12 why got ban too if Honorbuddy not detected?
    This announcement full of bu...sh.t, you cant just say sorry HB is detected or something, jsut lie continously. From my 4 accounts 1 was inactive like 2 months got banned and 1 was nearly 2 day old got banned too.... Quester lvling ....not even 24/7 hours gathering or something jsut 4-8 hour questing..... Stop lie, better.
     
  9. obzzcure

    obzzcure Member

    Joined:
    Jan 5, 2014
    Messages:
    328
    Likes Received:
    9
    Trophy Points:
    18
    :cool: GJ
     
    Tony likes this.
  10. lcw4928

    lcw4928 New Member

    Joined:
    Mar 19, 2016
    Messages:
    25
    Likes Received:
    2
    Trophy Points:
    3
    3/5 banned,but i fight again,banwave has gone:p
     
    Tony likes this.
  11. Azhemoth

    Azhemoth Active Member

    Joined:
    May 8, 2013
    Messages:
    533
    Likes Received:
    35
    Trophy Points:
    28
    Accounts I activated on the 12th and botted all day with questing were not banned. Still going strong.
     
    Tony likes this.
  12. Qtmeganr

    Qtmeganr Member

    Joined:
    Apr 20, 2017
    Messages:
    33
    Likes Received:
    7
    Trophy Points:
    8
    Ran .892 and was banned so that’s invalid, sorry. It’s only a matter of time honestly. After constant disconnects and crashes from HB, this comes as no surprise.
     
  13. Rashikami

    Rashikami Member

    Joined:
    Oct 18, 2014
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    6
    By far not all were fully hit, there are many FH + SBR/T:O/TuanHA Users which havent been banned including me
     
  14. crazywh

    crazywh New Member

    Joined:
    Oct 6, 2016
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    I ran 1 account to test the waters out after the 1 month wait for the update. Got caught only in the 1st tripwire on the 10th of October (there were 2 tripwire events on that day). The bot ran for a few hours on 11th and 12th of october and today the account is banned.
    I guess waiting for a month wasn't really worth it.
    I will be giving HB one last chance.
     
  15. Shok

    Shok New Member

    Joined:
    Oct 3, 2010
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    Few accs started after trip on 892 banned too.
     
  16. HB1892O30

    HB1892O30 New Member

    Joined:
    May 7, 2011
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    1
    Hello,

    Account name: WOW # 2

    Account Action: Suspended until 2019/04/13

    Violation: Abuse of game mechanic error

    In the recent activities of this account, the characters abused the functionality to the detriment of the game environment or the planned game experience



    was the email and the banishment that I received yesterday at 11 o'clock pm, is it because of the bot or something else, algeum has any idea how I can appeal to account not be banned for so long Thank you
     
  17. Tony

    Tony "The Bee" Staff Member Moderator

    Joined:
    Jan 15, 2010
    Messages:
    126,204
    Likes Received:
    415
    Trophy Points:
    83


    we are talking about accs only used 892+
     
  18. creedence

    creedence New Member

    Joined:
    Oct 10, 2014
    Messages:
    27
    Likes Received:
    3
    Trophy Points:
    3
    Just saying..

    I dont use HB Anymore since lifetime keys where disabled...
    I use another WoWBot, and i was BANNED for EXPLOIT for 6 months too right now...

    This time was EXPLOIT and not THIRD PARTY PROGRAM like when i have used HB

    waiting for appeal response..
     
  19. hijaq

    hijaq New Member

    Joined:
    Sep 15, 2014
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    Got few accs only used 892 and still banned. Was paid at 12th of october
     
  20. winifix

    winifix Member

    Joined:
    Dec 25, 2011
    Messages:
    155
    Likes Received:
    8
    Trophy Points:
    18
    Ok please explain my ban then, becuase I only ran 892+ and was not online for a single tripwire event? try make up better excuses in future and possibly research?
     
Thread Status:
Not open for further replies.

Share This Page