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

[Stable] Honorbuddy 1.9.5.7 - Lots of Bugfixes/InactivityTimer

Status
Not open for further replies.
awesome work. very nice to see the changelog included.

downloading it now.
 
I've had one issue so far, I had it a few times in the last version. Basically, it seems to run around, jump, run around, jump etc. when trying to res. The button is free to click, but it doesn't. Seems to happen if there are lots of mobs around. Could it just res anyway, run a way for a bit, then fight as usual? That way if it dies again there should be a suitable res spot.
 
I believe i am having issues with the RAF Combat Assist Option. He is not assisting, all he does is follow and targets but does not attack.

1.9.5.7
ShamWow
Horde-1-60-Modified

Code:
[8:34:14 AM:190] %   Exiting Combat
[8:34:14 AM:465] Activity: Combat
[8:34:14 AM:517] %   Entered Combat
[8:34:14 AM:586] %   - status [me]:  h/m:100.0%/100.0%, melee:1, range:0, rooted:False, immobile:False, silenced:False
[8:34:14 AM:633] %   No Current Target and can't find adds -- why still in Combat()
[8:34:14 AM:680] %   Exiting Combat
[8:34:14 AM:962] Activity: Combat
[8:34:15 AM:20] %   Entered Combat
[8:34:15 AM:64] %   - status [me]:  h/m:100.0%/100.0%, melee:1, range:0, rooted:False, immobile:False, silenced:False
[8:34:15 AM:132] %   No Current Target and can't find adds -- why still in Combat()
[8:34:15 AM:177] %   Exiting Combat
[8:34:15 AM:653] Activity: Combat
[8:34:15 AM:725] %   Entered Combat
[8:34:15 AM:771] %   - status [me]:  h/m:100.0%/100.0%, melee:1, range:0, rooted:False, immobile:False, silenced:False
[8:34:15 AM:816] %   No Current Target and can't find adds -- why still in Combat()
[8:34:15 AM:881] %   Exiting Combat
[8:34:16 AM:150] Activity: Combat
[8:34:16 AM:208] %   Entered Combat
[8:34:16 AM:253] %   - status [me]:  h/m:100.0%/100.0%, melee:1, range:0, rooted:False, immobile:False, silenced:False
[8:34:16 AM:311] %   No Current Target and can't find adds -- why still in Combat()
 
Any sign of IoC fix ? There were a couple of threads listing the problems last weekend. It is thought the problem was with HB rather than the profile.
 
Awesome. Gunna give this a try. I really wish you would stop adding [Stable] to the releases. Even if they are stable. Majority of the time there are still a lot of bugs and the new people get the wrong ideas when they see [Stable] and see that it clearly isnt.

Still tho, thanks for this!

Any sign of IoC fix ? There were a couple of threads listing the problems last weekend. It is thought the problem was with HB rather than the profile.

Good question. Its not longer call of arms so the ques dont pop as fast, but I will test later. I submitted a bug report on bugtracker about it a few days ago too. Just glad its no long Call of Arms for IoC.
 
Last edited:
Trying this now, but when I try to use the grind profile I had been using, the debug log is spammed with this:

Code:
[SIZE=1][COLOR=#000080][SIZE=1][COLOR=#000080][1:40:46 PM:48] StyxWoW.AreaManager.CurrentGrindArea is null
[1:40:46 PM:55] NeedToMoveToTarget?
[/COLOR][/SIZE][/COLOR][/SIZE]

Whats the quick fix?
 
sometimes the log just says: Pull Blacklisted and the bot stops fighting (getting killed)
I'm deeply sorry to tell you that, but the bot is still not usable for me as it's being killed ~every 5 minutes because of this bug.
I can't use the bugtracker to report this, because it wants me to choose a build but there is none.
 
Last edited:
what do i have to rename? ive looked all over the folder and i see nothing that i should change into " Honorbuddy.xml "..
 
The type initlizer for 'Styx.logic/Pathing.Navigator' threw an exception

tried to change the stytlesettings it just re-makes everytime i start up =\

Trying this now, but when I try to use the grind profile I had been using, the debug log is spammed with this:

Code:
[SIZE=1][COLOR=#000080][SIZE=1][COLOR=#000080][1:40:46 PM:48] StyxWoW.AreaManager.CurrentGrindArea is null
[1:40:46 PM:55] NeedToMoveToTarget?
[/COLOR][/SIZE][/COLOR][/SIZE]

Whats the quick fix?

what level are you and could you attach the profile are you using?
 
what level are you and could you attach the profile are you using?

I'm level 68 at the moment, the problem was coming from a profile that I had modified from 58-68 to use at 69, and I forgot to adjust the MaxLevel tag in one of the subprofiles.

My bad.
 
Trying this now, but when I try to use the grind profile I had been using, the debug log is spammed with this:

Code:
[SIZE=1][COLOR=#000080][SIZE=1][COLOR=#000080][1:40:46 PM:48] StyxWoW.AreaManager.CurrentGrindArea is null
[1:40:46 PM:55] NeedToMoveToTarget?
[/COLOR][/SIZE][/COLOR][/SIZE]

Whats the quick fix?

Your profile 'ended', or doesn't have anything for you to do at your current level. This should have been handled better, but that's the cause of the message.
 
Your profile 'ended', or doesn't have anything for you to do at your current level. This should have been handled better, but that's the cause of the message.

i was gonna say that :p
 
Your profile 'ended', or doesn't have anything for you to do at your current level. This should have been handled better, but that's the cause of the message.

Yep, I figured it out when I was going back over the profile and noticed I forgot to adjust one of the MaxLevel tags to my current level. Thanks guys.
 
[4:29:01 PM:502] Lua failed! Status: 
[4:29:01 PM:564] Changed POI to: Type: None, Loc: <0, 0, 0>
[4:29:01 PM:799] Changed POI to: Type: Sell, Name: Morg Gnarltree
[4:29:02 PM:158] Lua failed! Status: 
[4:29:02 PM:252] Changed POI to: Type: None, Loc: <0, 0, 0>
[4:29:02 PM:471] Changed POI to: Type: Sell, Name: Morg Gnarltree
[4:29:02 PM:830] Lua failed! Status: 
[4:29:02 PM:908] Changed POI to: Type: None, Loc: <0, 0, 0>
[4:29:03 PM:143] Changed POI to: Type: Sell, Name: Morg Gnarltree


Nooooooo!
 
Its failing to turn in quests 100% of the time. It spent the 5 minutes opening and closing the quest turn in dialog at a quest giver. I've experienced this will 2 different characters.

Here is a video of this bug in action:
http://www.youtube.com/watch?v=06-hen2mn1Q

Here is another video of quest turn in bugs. This time it runs to and fro, it left this for 5 minutes while I made a coffee just to make sure it would not eventually turn in the quest:
http://www.youtube.com/watch?v=CSZYn0_Ubig

The above bugs make unattended questing impossible.

Retreiving corpse 'bounced' backwards and forwards for a minute or two before clicking the button.

RAF (DPS role) appears to be problematic, more so than previously. It will sometimes just stand there doing nothing while the leader is running away. It does not always follow the leader. And it does not always assist in combat, it sometimes goes a few fights without even casting a spell. There log simply says:

[8:31:29 a.m.:901] Activity: Moving to leader
[8:31:30 a.m.:198] Activity: Moving to leader

There are many times its simply not moving, the navigation log shows the below errors. There are pages upon pages of errors like this:
Could not generate path from <2886.716, 959.9519, 116.671> to <1, 1, 1> (end)!
Could not generate path from <2907.582, 962.3593, 117.3115> to <1, 1, 1> (end)!
Could not generate path from <2922.902, 956.0065, 121.6764> to <1, 1, 1> (end)!
 
Last edited:
I died!
There are 4 hostile mobs.
Moving to Type: Corpse, Loc: <3162.601, 5880.843, 98.24308>
Clicking corpse popup...
Moving to Type: None, Loc: <0, 0, 0>


Didn't realize it died. It was fighting and moving, but the over all "smartness" of it degraded. It's out killing Rhinos in Borean Tundra. I used the profile generator also included in the .zip.
Its getting the problematic message above. So I think it's broke. It ran all but 5 mins before it did not realize it was dead.

It did however recover itself. Elder Atkanok or something he's a rock out in borean tundra near the quarry quests. It kept running into the rock/npc. And didn't target him. I see this as an issue as he's/it's a quest giver!

HELP! :( I had to manually accept the quest and restart HB to get it to work again. Babysitting sucks!!!
 
Last edited:
CHANGE - Mesh folder path now has a default location at C:\Users\CurrentUsername\AppData\Local\HonorbuddyMeshes.
CHANGE - Mesh folder path will now be created, if it doesn't already exist.

Doesnt work. HB still asks for a Mesh Path on Win7
 
Status
Not open for further replies.
Back
Top