What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Honorbuddy 2.0.0.3740 Discussion Thread

Status
Not open for further replies.
It worked perfect yesterday, today it can't inject anymore.
Logs attached.

edit: will post on bug trackers aswell.

Make sure you are using DX9,

/run print(GetCVar('gxApi'))
open the chatbox in wow copy paste that press enter.
If it prints D3D9 ure all good if it says D3D11 you have to open your Config.wtf file and edit this row:
SET gxApi "D3D11"

Make sure it looks like this:
SET gxApi "D3D9"

 
Thank you, it seems to work now. This is the reason i like forums :)
 
Currently the bot is attacking actual players when it cannot find mobs. This is especially a problem when near neutral towns with guards. Is there an option I'm not seeing to turn this off?

Anyone have any insight on this? It's not profile related.
 
I'm trying to login to honorbuddy but keeps telling me auth failed, i'm using correct login details, it also says auth failed on test login, any help please?

Edit: re-downloaded honorbuddy and now works.
 
Last edited:
I've read many pages from this topic (have to admit not all).
I would like to make a suggestion to split up the different "sub" bots to their own topics.
I'm interested in the behaviour bots underneath HB (like the BG bot and another upcoming bot for RaF that was not quite ready as I read Nesox's comment), but can't find any specifics on the changes or additions they bring us.
Would it be possible to split the behaviour bots to the plugin section like what's done with IB (I realize that IB is a release not done by the HB team but nonetheless).

I would appreciate it to be able to read on specifics and changes on the behaviour bots underneath HB.
Would give it more overview and also attention specifically to this (and possible bug reports, tests and unintended behaviour etc).
Thanks, LiquidAtoR.
 
Couple things;

1. The bot seems to be targeting/going to fight the next mob before it's done looting.

^^ This ^^

I have this happening a lot. On Druids, Shamans, Rouge and Pally. Looting seems slower when you play by hand. Maybe blizz put in some kind of delay to mess with us? :-)
 
From a longtime pvper I just want to congratulate you guys for the new bet pvp bot, it's quite a masterpiece, keep up the hard work lads! ;)
 
For the new BG Bot, two things:

1) Can we get it to randomize where it stands when it goes to the gates (like in AB). That way it's not always at the same spot.

2) Can the targeting be weights to handled so that it tries to go after the healers first? Or is that fully CC driven?
 
For the new BG Bot, two things:

1) Can we get it to randomize where it stands when it goes to the gates (like in AB). That way it's not always at the same spot.

2) Can the targeting be weights to handled so that it tries to go after the healers first? Or is that fully CC driven?

The spot it wait's at is random.
 
The spot it wait's at is random.

The new pvp bot is pretty nice.

only problem I saw with it was in AB where horde had stables and my dk kept spawning in ally base.

It'll say running to blacksmith but ran close to stables and attacking people there getting himself killed over and over making it look pretty obvious.

Was wondering if we could get it to take a wider route around stables in that kind of situation.
 
i tested the new version and wanted to lvl a 45 warri. first everything was nice but after i changed the resting % from about 30% hp to 75% the toon does not rest at all?? where is the problem?
 
Did you guys add random jumping? Seems to be doing this at odd times (when attempting to mount a few times). Also did something get changed with looting? While running an Uldum Volatile Air profile using convalace pally cc it takes off for a few seconds 60% of the time then does a 180 and loots looks very bottish. Thanks in advance for your reply.

I've reported these same issues in the bugtracker, let's see if they get fixed.
 
I've reported these same issues in the bugtracker, let's see if they get fixed.

This is caused by the stuck handling code. It's near the top of our to-do list.
 
Wow, i generaly whine on little stuff you keep forget but now you listened and properly fixed the craps about npc being engaged by others ( exemple a npc engaged by another npc ) which was making the bot stand forever, this is so much more efficient for questing now. 3 cheer up to you guys for that fix, it was a hells while it lasted.

Overall i didnt saw much problem beside some hick up related to skinning ( trying to skin a mining mob as exemple til it despawn) and some problem related to mesh that i reported directly to MaiN.

Is there a way now to accept a quest from item in our bag ? thats about what i am lacking to finish my kick ass quest profile.

Lets me know if there is a way right now or when this could be implented or if its planned to be eventualy.

Thx

Zuruss
 
for some reson bot doesnt mount anything... but in options mounting is turned on, and auto detect is on...
 
Just my two cents, i like were the bot is going it seems like once the bugs are cleaned it will be by far an upgrade over the previous pvp bot.

Noticed while in eots, i jump from horde spawn down and loose 50% hp, stop and heal then mount and do 3-4 circles on the spot then run off.... this looks a bit silly :) but i can wait for the next version.

Cheers for the great release! (i can start the bot without falling to my death yay)
 
Im having some problems in eots when bg starts hes trying to get unstuck when waiting for gate . runs in a circle before the bg starts

Not always like this, BUT when it does happend it looks RLY lame and says report me in my forehead...
 
Last edited:
Im having some problems in eots when bg starts hes trying to get unstuck when waiting for gate . runs in a circle before the bg starts

Not always like this, BUT when it does happend it looks RLY lame and says report me in my forehead...

same here, also i get stucked when he jumpes down from the start point he fraks out and want to unstuck.

will report this on bugtracker after a few runs.
 
Status
Not open for further replies.
Back
Top