[Release] Honorbuddy 2.0.0.3182 - Updated for wow 4.0.3.13287

thanks for the info. but putting that aside is this something that can get looked into???

 

This version was running fine just up till today, now i keep getting

[18:34:52:70] Attached to WoW with ID 5148
[18:34:52:70] Loading Honorbuddy 2.0.0.3182 settings.
[18:34:54:208] Authenticating..
[18:34:55:116] Could not connect to the authentication server. It may be too busy to process your request. Please wait a few minutes and try again!
[18:34:55:117] Authentication failed.
[18:35:11:361] Authenticating..
[18:35:12:320] Could not connect to the authentication server. It may be too busy to process your request. Please wait a few minutes and try again!
[18:35:12:321] Authentication failed.
[18:35:26:754] Authenticating..
[18:35:27:438] Could not connect to the authentication server. It may be too busy to process your request. Please wait a few minutes and try again!
[18:35:27:439] Authentication failed.

Tried a new install, tried friends accounts. I get this error on everything.

 

I got a problem, this happends when i try to start honorbuddy... You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid WoW instance to use Honorbuddy.

SOme1 know what to do??

 

I have the same problem with servers starting and not working. I logged in all in finally but forgot to install a CC so i closed HB again, and now its not workin...!!!! And it says wait a few minuts...nono i have been waiting for 1? hour and says the same over and over again. It starts to annoy me, anyways good job with all the updates HB admistrators.

 

WTB an increased harvest range in honorbuddy, as it is now you need to walk quite close to the herb/mine for him to bother going gather it, isnt really efficient if i need to quest/grind level and then spend 2-3 h using GB method to harvest to pick up where my bot should be for his level, plz either add an option for us to increase it or do it fixed inside the bot, thx.

Zuruss

 

that means for now i have to type in my complete list of items with every new hb version until auctioneer wow.exe thing is out?

 

hey dev's now im getting this error.
be appreciated if i can grab some assitance

Code:

[10:35:03 AM:238] StyxWoW.AreaManager.CurrentGrindArea is null
[10:35:09 AM:16] System.Threading.ThreadAbortException: Thread was being aborted.
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Styx.Logic.Targeting.a(Delegate A_0, Object[] A_1)
[10:35:09 AM:17] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.Logic.Targeting.a(Delegate A_0, Object[] A_1)
   at Styx.Logic.Targeting.Pulse()
[10:35:09 AM:19] Stop Button pressed. User has stopped the bot.

full log attached
thanks in advance.

 

Worked fine till now

It attaches to wow, and recognizes everything but will not move. The navigation tab says it failed to connect to mesh server.

 

Old version. Grab the latest

 

Could not connect to the authentication server. It may be too busy to process your request. Please wait a few minutes and try again!
Authentication failed.

I keep getting this message everytime i try to log into Honorbuddy why is that? i have been trying for days now and still get the same thing. what is going on? why is it doing this.

 

ㅜㅠ

영문판 접속이 안되네 ㅠㅠ
미치긋네

 

HB fatal error:

CC:
http://www.thebuddyforum.com/honorbuddy-forum/classes/paladin/12550-simple-70-holy-pve-cc.html

Instancebuddy in the Halls of Stone.

Can any of the devs take a look at this?

Log:

 

I'm not even gonna comment on that! .. oh wait...