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

[Stable] Honorbuddy 1.9.5.9 - Spirithealers/UseItem/Bugfixes

i thought this was gonna be fixed but since it hasnt it still is doing the "NeedTomovetotarget" spam making it look like a bot. i would up load my log but sadly it's too long.

edit: Level 5 Alliance warrior is the toon I've received the problem on
 
Last edited:
Need to have enabled loot chest , to have the bot actualy pick up stuff while doing quest......shouldnt have to unless thats intended ?

( btw for your repair problem which mine doesnt have that problem, there is lots of addon for it meanwhile they fix it )


Zuruss
 
Last edited:
If you are botting with a caster class the bot does not recognize when the target is not in the field of view and tries to attack it for hours...
 
how do I install this? I mean, I have the last version of HB and I dont want to remove all my meshes, profiles CC's etc, can I like "upgrade" instead of reinstall? ><
 
how do I install this? I mean, I have the last version of HB and I dont want to remove all my meshes, profiles CC's etc, can I like "upgrade" instead of reinstall? ><

Its always best to install a new HB.

Move your mesh folder to the Core bot folder, and then link from the bot to that folder, (of if your useing a new the latest ver, the meshes will be stored in a location that all the following versions will look for meshes).

I use the folloing setup -

Code:
\WowBots
     \Gatherbuddy\ all gb stuff in here
     \Honorbuddy\
                        \HB Mesh
                        \Profiles
                        \HB 1.9.5.9 - 1
                        \HB 1.9.5.9 - 2     
                        \HB 1.9.5.9 - 3
                        \HB 1.9.5.7 - 1
                        \HB 1.9.5.7 - 2
                        \HB 1.9.5.7 - 3

All HB's use the same mesh folder, and same profile folder, this is fine and works well with running multiple bots from the same mesh, im always runnign 2 or 3 bots at same time.

The only thing you then need to copy over is the CC's into each bot, and the PLUGINS.

So I normally set 1 up then copy and paste the HB core folder and then rename them 1,2,3 to I know which is which.
 
Last edited:
If you are botting with a caster class the bot does not recognize when the target is not in the field of view and tries to attack it for hours...

What CC are you using? If it's a default one, let me know which and I'll upload a fixed one for you.
 
No I'm not using a default one, it is skiWarlock v4.03, but I will repost the bug in the correct section or otherwise people will get mad at me again.
 
Suggestion: When I get stuck on a fence, mailbox, or anything really... all the bot tries to do is dismount, which has basically never succeeds in getting unstuck. Would be nice if it would try some more random movements/jumps. For example, move backwards, walks sideways a bit, loop around.... stuff like that. Also, if it reports stuck for too long, would be nice to have an option to hearth or close down HB/WoW.
 

Attachments

Suggestion: When I get stuck on a fence, mailbox, or anything really... all the bot tries to do is dismount, which has basically never succeeds in getting unstuck. Would be nice if it would try some more random movements/jumps. For example, move backwards, walks sideways a bit, loop around.... stuff like that. Also, if it reports stuck for too long, would be nice to have an option to hearth or close down HB/WoW.

Or even try jumping. Most stucks can be resolved with just a single jump.
 
There is a problem with the bot doign PickUP and TurnIns. It never pulls mobs in its path, it just face pulls. It will literally mount up, and be on its way to PickUp/TurnIn and it will try to ride through mobs it's level - the only reason it stops for combat is because the mob attacks it. It should, in my opinion recognize that there are dangerous mobs in the way, and stop and kill them intentionally. Too many times now I've watched my bot facepull 7-8 mobs because it was being stupid and just ran right into them, when if it would have just stopped, and pulled like it should it would have handled them just fine.

edit: meh.. its not just pickup and turnins, its also facepulling while on its way to complete an objective. it's just not pulling how it should. kill between hotspots is on, and its just not working.

edit: like when it's doing a quest. say, kill x amount of mob Y. well, there happens to be other mobs around in that area, than mob Y, so on the way to pull mob Y - the bot unintentionally pulls mob Z, often resulting in death.
 
Last edited:
Bot is constantly getting attacked by lower level mobiles (in grinding mode) and wont attack them back, luckily as its a pally ret aura slowly grids them down, but otherwise this would be a disaster.

Edit - Forgot to say this is only when im Mounted. (Yes I have turned off all plugins apart from erefreshment)

Pull range is set to 5m as im on a levelling mining/herb profile.




View attachment 13-09-2010 Log.txt
 
Last edited:
Argh -- I just reinstalled my OS because all the services stopped functioning.

Just instaleld .net 3.5 trying to run honorbuddy. Instant crash
"Styx.Logic.Pathing.Navigator" threw an exception.
[1:21:25 PM:258] Attached to WoW with ID 4808
[1:21:25 PM:260] Loading Honorbuddy 1.9.5.9 settings.
[1:21:25 PM:262] Creating settings directory.
[1:21:33 PM:32] Attached to WoW with ID 4808
[1:21:33 PM:34] Loading Honorbuddy 1.9.5.9 settings.
[1:21:52 PM:670] Attached to WoW with ID 4808
[1:21:52 PM:672] Loading Honorbuddy 1.9.5.9 settings.

This is the full log file.

Please... save meh =/.
 
I've just started to do pvp (SOTA) with this version, running dk atm, profile works great doesn't get stuck on the gates anymore but it seems to not pick up that the gates are up or down still. Any idea when we can expect a fix for that as its a big issue if pvping.
 
Something I noticed with the new Ress at Spirit Healer feature. When it Ress', it doesn't wait out the sickness timer, just ress and go. It should wait out the timer if it can, otherwise it just runs back out and gets squashed again. Also, it appears to be double looting. It kills, the mob, loots it, then tries looting again and get's a Lootable isn't lootable...blacklisting message.

Logs attached

We intentionally did not add this into the core. CCs should be responsible for handling this (certain classes can still grind with res sickness, others can't). If the default CCs aren't handling this, then it's a valid issue.

Something I noticed today while questing in Terokkar Forest. The profile I'm using (HordeQuest Project Hellfire 60+) doesn't have vendors defined and I have selected 'Find Vendors Automatically' in bot settings. There's a repair mob my character keeps running to (Horvon the Armorer), but he is only available after completing a quest chain which I have not done. Would that be an HB issue or a profile issue? Can I just blacklist the repair npc in the profile? How would I do that?

Thanks

Please give me the ID of the vendor, and we'll remove it from the database. As we've said; it's not perfect, but it works 90% of the time!

I downloaded Honorbuddy 1.9.5.9.
I started an Orc hunter and it seems HB is counting the # of open slots in my quiver as part of the free bag space and it wouldn't sell items in the bag until I filled all of the open spaces in the quiver too.

This is a known bug. And as everyone will tell you; don't use a quiver. Use a regular bag. (Quivers do basically nothing now!)

Its looting chests when I've set it to NOT loot chests. My current grininding area is causing numerous deaths as a result of this.

I can't reproduce this. Catch me on IRC/MSN.

I am leveling a DK using the Cimmerian 2.4 + 100% stable leveling profile I've been used for like 5 characters.

with this version my toon start to equip grey items and weapons - it's quite funny to see it fighting with grey 1hand like 3 minutes after I turned it on.

also - and it's look kinda weird - mobs killed by me appears to be lootable but it's impossible to loot them - the cursor changes to looting one but it's gray.
I can't loot even manually. After relog into game cursor turns colored and I can normally loot the corpses.
But toon standing for few minutes near each new pile of killed mobs... damn it's so scary as it's sooo bottish.

well it's evoidable by turning off looting. it's kinda sad but it's ok.

Also it's kinda frustrating that the same happens with vendor repair buttons which leads to situation where my toon tries to repair like for a 5 hours in a row.

Another issue it's like 3-5 second delays between actions - for example it dismounts and start to fight with a huge (4-7 seconds) delay after being attacked.
While running to corpse it can stand still for 10-12 seconds etc.
Looks kinda weird.

And btw I have quite fast PC, it's not because of it I guess.

Check the AutoEquip settings. Chances are; they're wrong!

As for the issue with things appearing lootable, but not being lootable: this seems like an issue on your side, and not an issue with the bot. WoW screws up like that sometimes, and it's a known bug. (Been there for quite a few years now)

As for long times between actions... I can't really say much. I haven't seen it stand around longer than 3s (and that's usually during a fairly long loop of Lua). Which CC are you using?

There is probably a bug already reported but prefered to mention it anyway, while mounted sometime when the bot get attacked, it wont unmount and get killed unless your lucky and you get smashed off your horse, plz fix coz its annoying and cause shit load of deaths.

Second problem is, i would like to see implented a real unstuck feature not some craps ( sorry for the words ) method where the bot trying to click to move on a side.....itsnt reliable at all, pershap its time to add a keyboard method unstuck feature, when you get stuck OFTEN on a edge of ramp, stair etc.... the bot cannot seem to unstuck with the current method where it try to click infront, sometime it try to click to move on the side but still itsnt enough. I am up to 7 unstuck that i had to do manualy on a edge of stair while leveling 1-22 quest order profile, add to this the comon bugs related to it, we sure doesnt need to have to watch the bot over this due to the lack of a real unstuck method that could be so easily implented in honnorbuddy, a move backyard never hurted on a unstuck method ( when it is stuck for too long as exemple ) or a move to previous click to move.....

Also while i am on it, gatherbuddy unstuck method regressed over the last few months, it used to be so good at unstucking and so fast, now when you face a big tree it will often try to go through the tree for many mins til the blacklist get over it, which i dont have to mention coz a loads of unwanted blacklisting of node.

Thx

Zuruss

We'll be working on a new unstuck system in later releases. As for now, just blackspot the problem areas.

This is not a GB support thread. If you have issues with it, please post them there.

It would be appreciated if the bugtracker would be fixed so we can have a proper overview again when reporting.
I reported this issue 2 pages ago along with a RaF bug I found.
A reply or confirmation has yet to come.

Thanks, Liquid.

Fixed the bugtracker. As I stated in a previous release thread, it has issues when adding new builds. (The permissions don't get correctly set for some odd reason)
 
Last edited:
I'm having a rather annoying issue at the moment :)

I'm running a 47 mage with Mephile's CC and Hawker's 1-60 QO profile, now what's happening is I keep getting messages about corrupt meshes lately. I've tried deleting the entire folder, I've tried deleting only the azeroth folder, but all that happens is that HB redownloads them and I'd still get the error afterwards. When I go to check the mesh he's saying is corrupt (a different one each time), the file isn't there. So for example "It appears azeroth31_30 is corrupt", I go check and it's not there.

Hoping for a swift reply, as for the rest very nice release!

EDIT: I'm not having this issue in northrend, so maybe it's really the eastern kingdoms mesh that corrupt. My current zone is Badlands.
 
Last edited:
Fixed the bugtracker. As I stated in a previous release thread, it has issues when adding new builds. (The permissions don't get correctly set for some odd reason)
Thank you.
The RaF Raid bug I encountered, is now properly posted on the bugtracker.

Regards, LiquidAtoR.
 
I'm having a rather annoying issue at the moment :)

I'm running a 47 mage with Mephile's CC and Hawker's 1-60 QO profile, now what's happening is I keep getting messages about corrupt meshes lately. I've tried deleting the entire folder, I've tried deleting only the azeroth folder, but all that happens is that HB redownloads them and I'd still get the error afterwards. When I go to check the mesh he's saying is corrupt (a different one each time), the file isn't there. So for example "It appears azeroth31_30 is corrupt", I go check and it's not there.

Hoping for a swift reply, as for the rest very nice release!

EDIT: I'm not having this issue in northrend, so maybe it's really the eastern kingdoms mesh that corrupt. My current zone is Badlands.

I'm having the same issue in Kalimdor. It seems the new inactivity monitor is causing the problem. When I delete the mesh folder it has to redownload everything for the zone which can take some time. After 10 mins, WoW exits and seems to cause HB to hang on download, thus corrupting the mesh file. I found by changing the timout value in StyxSettings.xml to something longer (60) this problem went away becuase it was able to download all the required mesh files without timing out and hanging
 
Back
Top