Honorbuddy v2.5.7280.629 - Patch 5.3.0.17116

Great work guys, you really pushed this one out this time. thanks!

 

is the DX11 bug fixed?

 

Hi, Thumped,

Actually, it looks like your profile is written that way. What's new is the warnings from Singular.

It looks like you've wrapped InteractWith in a While loop. When InteractWith is running it sets PullDistance to zero and controls target selection itself. When it is done, InteractWith restores the original pull distance. So, each iteration through the loop causes the double-change in PullDistance setting.

InteractWith has always been this way. What's new is the warning from Singular.

cheers,
chinajade

 

what bug? Ive been using DX11 just fine.

 

have blizz brought another patch out because i'm getting.

Honorbuddy v2.5.7280.629 started.
Logging in...
-------------------------------
You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
This version of Honorbuddy only supports WoW Build #17116
You are currently on build #0
-------------------------------

 

Yeah same here, would love a response or quick fix? US version here!

 

Working great for me.

 

mine is eu.

 

Actually READ​ the original post.

 

EU servers haven't updated yet. Don't use this version of HB until AFTER the patch.

 

honorbuddy .625 on DX11 worked fine but since .626 (.627, .628) it take forerver to login and initialize and the it crashes

View attachment 8832 2013-06-24 23.18.txt

 

working fine for me

 

Alex ~ when wow gets a patch (big or small ) 9 out of 10 times the bot will need an update.

You will get that no valid to attach when this happens.

When a new release is available the bot will auto update, you can watch the threads in "releases" (stable / beta) for news and a manual DL link to the updated bot.

The Devs have gotten in a nice habit of giving notice, freezing release threads, and posting the progress when the bot is down due to an update.

The update can take days or hours. Today, we didn't have to wait long at all!!!

Great job Devs and team - great communication and response!

 

Ive noticed an issue that i cant send a log for. If I log onto one session of wow and turn the bot on then log into another session of wow and then turn the bot on for that one. i am unable to click onto the 1st bot window nor is any logs showing up yet the toon attached to that wow is still moving and collecting.( Fyi both of these accounts are merged) . Now for the other weird part-- If i turn on one wow and then the bot for it and then log onto an unmerged account then turn on the bot i can click either bot window no problem. also if i open both wow merged accounts then open bots for them i can click the bot windows the only time one of the bot windows freezes or becomes unclickable is if i open one wow then bot and then the other wow then bot on a merged account. any ideas?

 

uppdated but now my key wont work . stuck on loggin. authentication failed

 

If you start the game and it patches. The launcher will start the 64 bit version of the game. Restart the game with 32 bit client and the test version will connect.

 

the download button now opens my winrar folder with a few random files and no folders -- a bug? it won't let me download the full test

 

U need to login to your account

Log On - Buddy Auth Portal

on session tab check kill to clear it out

 

View attachment 7072 2013-06-27 09.32.txt

 

I can't download from first post