Blah when I tried it this morning it gave me auth failed, no auth servers available , so I upgraded to the latest.. will have to find a old zip file somewhere I guess..
1.9.6.0 gives of an error (was fine just a few hours ago) 1.9.6.1 gives this Authentication failed. Authenticating.. Auth - No avaible servers online. Authentication failed. 1.9.6.2 - is dodgy Can I use honorbuddy pls? End user is tired of constant bugs
Wasn't sure where else to post this, but I'm using HB 1.9.6.1, and any time I try to start running it with ANY profile, I get "Value cannot be null. Parameter name: source" in the log, and I posted the debug log as an attachment.
I've been getting 132 errors ever since the release. Research shows that there's no reliable cause of a 132, but I've been getting it consistently since I've updated. Anyone else?
- Crashes... - Can't use any warlock class... - Must load twice the profile each time or it will use the old one... Not working great for me !
Is that possible for you guys to really give a focus on the mesh bug ? or whatever cause the bot to jump like a frog from time to time, i go out and smoke a cigg, come back and the bot is in a kind of corner jumping over and over insteand of blacklisting his current path and creating a new one, is that hard to actualy detect the bot jumping 150 time in 5 min on the same hotspot ? also you have a diff bug where the bot hang between 2 click to move and jumping from time to time...... The evolution of the bot is amazing guys really 3 cheer up but everytime i launch the bot its a guess if i dont fully watch it, at lvl 72 jumping like a frog right by 2 person cost me nearly 70 buck + the time lost coz no matter what i be reported and risk to be warned/banned within few days/week which make it worse...., if you need 10$ buck from everyone willing to pay a darn extra for someone to fix that bug and release a kind of private version where this craps wont happend lets me know i be in.....coz this bug is in since too long really... sorry to be a little hard atm, but everytime i see this happend 1-2 time daily while questing leveling, i wanna pull my hairs. Zuruss
Things that i notice: - Kills Mobs only if i get Aggro, does not pull Mobs active/at all. Old HB1/HB2 farmed an area so clean you could eat from it (>.>) - Skinning-Blacklisting is WAY to aggressive, losing tons of leather because mob gets blacklisted after a _nanosecond_ of looting - Mounts/Dismounts randomly for no reason ATM this Bot spends more time with running randomly than with killing shit. It's really annoying. View attachment 24.09.2010_09_26 Log.txt
Your error mate bot works fine - [09:27:07:386] GroundMountFarmingMode: True Uncheck the tick box for this and all will be well mate.
I read that advice from you in another thread already (yeah, i actually use the search function before posting) In that log it's enabled but i had several runs without that box checked and the only thing it changes is that it's now fighting what it has aggroed instead of just running off. I don't know if you have used the old fashioned HB (6-8 Month in the past from today)... That one was active targeting and assaulting Mobs like a player would do. Am i using way to less hotspots to make it work properly? Do i really have to bodypull evey single mob before the bot starts attacking it? I took a break from wow and botting the last 6 month, maybe i've missed something. I attached the profile i am using atm, maybe my profiles are to "old fashioned" in the way i created them.
Is a Felblade Doomguard part of Faction 14? Normally you need to have the faction of the things you want to kill in the profile. You have only faction 14 in the profile. You can find out the faction of a creature by targeting it and pressing Target Info from the Profiles and Meshes Tab.
Wow, you're right. I am using the HB Profile Creator from the FOrums and it marks these mobs as faction 14... very strange. HB marks them as 90 and it actually works fine now. Thanks m8. YOU SAVED MY DAY! +rep!
I thought i read somewhere (shortly after this was released) that a new build to replace this buggy one was due yesterday ??
