TLDR: People getting banned, no one knows why, wait for Honorbuddy team to comment
/thread
TLDR: People getting banned, no one knows why, wait for Honorbuddy team to comment
Its because the navigation in the Garrison was never fully workingHi
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
Wats strange is the Garrison Botbase I'm using (not mention any names) hav had perfect navigation from day 1Its because the navigation in the Garrison was never fully workingAnd 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.
To me it looks like the connection is the CRs, perhaps something to do with how many commands they send to the game per second?
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.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????
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.
Thanks for clearing that up for me.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 ...
Also guys dont forget, that users of another bot also received same bans. It is not only HB problem.
There is other bot that is pretty same as HB, some of his users also received same bans as ppl here (6month)what othere affected?
There is other bot that is pretty same as HB, some of his users also received same bans as ppl here (6month)
If you think being reported is the only way for detection, then please just never use HB again. Explain how people running 5 man dungeon teams get banned if the only way to get detected is through reports.