Honorbuddy Detected?

/thread

 

Hi

Noticed something odd a little earlier (After patch). When starting Garrison***** the navigation was all off. HB said can not find object, moving to known location (or something similar).
It kept running into my inn and got stuck on an object. Tried restarting, new innstal.... The navigation was not working at all???
Turned off the bot.. No ban... Yet...

Don't know, could be an coincident, I don't know.

WW

 

Looks like I have been a rule breaker long before using HB Thanks for the info, I had not seen that before.

Given that I don't see a long list of people being banned for this Macro combination I am still confident that the instant cast "aimable" spells is not the cause of our demise.

 

Its because the navigation in the Garrison was never fully working And all of the Garrison farming profiles/bases uses custom navigation for it
And not because of HB issues, but because of the new dynamic buildings.

 

I've been using GarrisonButler once a day with HBRelog for a few weeks, at the day of the tripwire event and after it. Other than that I've been using high risk rep farming profiles, fishingmaster for many many hours unattended, leveled ~7 characters from 1-100 using questing from 1-15 and then dungeonbuddy from 15-90 and then questing from 90-100 (kicks). I use Enyo+CR in Arena, Ashran and Raids. I sometimes play manually when I'm not superdupertired, but I can't perform as well as the bot (but close enough) and I use a different build when not using bot (Germination instead of Moment of Clarity).

My account is still safe. I'd chalk down all these to overdue reports/investigations being banned. Even Blizzard employees procrastinate

There was, however, talk about a new detection method being implemented on lua commands (I'm guessing this is what caused tripwire?), which maybe botbases regarding Garrison utilize more than enyo+cr? Such as starting missions et.c. Also if you're using or have used lua unlockers that could've been the reason? The fact that almost everyone who has been reported to be banned has reported using Garrison botbases might just be that almost everyone uses garrison botbases because garrison is just AIDS and noone wants to do it on their own.

I've been wary of using HB since all of these reports, my brother and his GF are currently raiding with Enyo+CR and they're fine.

I'll be using it on my next raid, I've told my team I've been thinking of vacationing from WoW over the summer. 6 month ban wouldn't matter much to me. It sure beats a permanent one.

 

Wats strange is the Garrison Botbase I'm using (not mention any names) hav had perfect navigation from day 1
Never a stuck or missdirection ever, but suddenly after the patch it's totaly off????

 

Also guys dont forget, that users of another bot also received same bans. It is not only HB problem.

 

I got a 6 month on my main account I haven't botted on in quite awhile

 

If that were the case then the AutoHotkey scripts I used when HB is down would be detected even faster since it mashes many more keys with identical delays.

Which ... good thought ... time to randomize the sleep timer in my AutoHotkey scripts and possibly randomize a few of the key presses.

I -would- like to see a HB plugin that can randomize the GCD a bit and possibly cause "oops" in ability procs occasionally to further minimize CR-only detection, but overall that seems fairly low demand.

 

Every patch lead to new HB revision, and as we all know, new revisions sometimes do require the developers to make their products complain with the new changes, plus there was 2 fast HB revisions, which had some bugs last week, so that is the reason once working 100% AFK product to have stucks in the new HB revision.

Nothing bad for the botbases, it just needs time for its Dev to address the non-complaint stuff, fix it, beta test it, fix again if needed, then upload on the Store, and finally get approved as live product again! This could not be done neither in few hours, nor in few days - usually takes a week or so. But latest HB .777 is less than 10hours old ...

 

I am pretty sure these bans have to do with Combat routines. I am an avid botter and got my little brother to start botting. I use Garrison butler every day and have for months on 11 characters. He barely started using Garrison butter on 1-3 toons. The on thing he was doing that i did not do was using routines in LFR and Arenas. As of today he has been banned from wow for 6 months and I have not. I ran garrison butler as early as this morning on all 11 toons and still have my account. The fact that he has not ran his Honor buddy since the before the patch and i have as early as today tells me this has been something they detected prior to the patch (and or they are behind on reviewing people's reporting of bots).

Combat Routines is the key here - NOT garrison butler otherwise i would be gone too. No more botting for me.

 

ye and the same goes for razer naga synapse macro its the same as autohotkey and you can setup perfectkly 1 rotation button with just pressing 1 button on the naga and one for cooldowns aoe etc

 

Thanks for clearing that up for me.

But on the bright side, no ban yet. Have been botting alot on 4 other accounts the past weeks. No ban ther either... Yet...

 

i use routines on 4 of my 6 toons and no ban.

have been using them for about 4+ months now.

 

what othere affected?

 

Botted for Month and half..Level 2 toons to 100..Ran alot of BG's. 6 month ban...oh well. I had never botted before..I think this is effecting alot of people.

 

There is other bot that is pretty same as HB, some of his users also received same bans as ppl here (6month)

 

wrobot?

 

yea, mr. smartass, I know that there's other methods of being flagged. still, using a garrison bot is not time consuming (you don't bot that 24/7) and it is basically doing the same thing a human would do. I wouldn't know any "behavior" that is bot like when botting garrisons, thus having trouble seing what the flag could be, yanamsayin'?

 

> make attempt to detect honorbuddy
> save up a whole bunch of bans in case the detection doesn't work/gets caught by tripwire
> detection didn't work, lets unleash the stored up bans to make people think they are related to the detection attempt

am i really the first one to point this out