What's new
By:
  • 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.
w00tsauce said:
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!



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.
Click to expand...

Stable just means it never or only rarely crashes. It doesn't talk to the point of bugs other than if they are crash bugs.
 
ajgoodrich said:
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!!!
Click to expand...

Questing is I don't know how many times this has to be mentioned (BETA). You should never leave a beta product unattended. Baby sitting is required.
 
I'm having the exact same problem as fpsware, it collects quests, completed their objectives, but then just stands at the turn-in, spamming the window as show in fpsware's movie.
Besides, awesome release and great bugfixes :)
 
can anyone post a fix for the issue of not being able to open HB cause of the styx issue..?
 
Holy crap. The QuestOrderMaker tool you all included with this release is awesome!
 
Its not always emptying bags / selling at the vendor. Character is currently grinding with full bags.
 
First and foremost, I APPRECIATE what has been fixed thus far. It's much more stable in my eyes then the previous version. I THANK YOU for doing this!!!

However I have some bugs... and here's the bad news...


Bugs found while in questing mode:

1. Same turn in error. As posted before: http://www.youtube.com/watch?v=06-hen2mn1Q Same thing happens to me on all quests.

2. Doesn't use objects in bags on corpses/items on the ground.

3. NPC's that aren't "Characters" but more like rocks/items... Aren't selected. The bot will just mount up... run into object... jump off mount... run into it again, over and over. (This looks like the same bug as #2 pretty much.)

4. Get's stuck often in navigation. Doesn't find a way out when it has an option to do so. Jumping/Moving/Shifting, finding a new route.

5. Also there is a problem sometimes when it dies... It seems though it doesn't know it did and doesn't resume functions of movement/questing etc... because it's dead. Just sits there.


Other than that... I think it's flawless! :)
 
Last edited:
Two problems.

#1: (this is an example, since the exact text from my original log was in a log file that was too big to upload)

10:19:02 PM:16] Activity: Combat
[10:19:02 PM:72] Changed POI to: Type: None, Loc: <0, 0, 0>
[10:19:02 PM:237] Activity: Combat
[10:19:02 PM:324] Changed POI to: Type: None, Loc: <0, 0, 0>
[10:19:02 PM:479] Activity: Combat
[10:19:02 PM:539] Changed POI to: Type: None, Loc: <0, 0, 0>
[10:19:02 PM:701] Activity: Combat
[10:19:02 PM:764] Changed POI to: Type: None, Loc: <0, 0, 0>
[10:19:02 PM:922] Activity: Combat
[10:19:02 PM:983] Changed POI to: Type: None, Loc: <0, 0, 0>
[10:19:03 PM:149] Activity: Combat
[10:19:03 PM:209] Changed POI to: Type: None, Loc: <0, 0, 0>
[10:19:03 PM:474] Activity: Combat
[10:19:03 PM:545] Changed POI to: Type: None, Loc: <0, 0, 0>
Click to expand...

And #2:

Directly before that, the bot will finish combat and then get an add, get beat on, and never turn to face what's attacking him. It attempts to attack over and over, but it's not facing the target. This shows up multiple times in the log, and if I catch it, I'll right click on what's attacking him to fix it. Sometimes it seems to be deselecting the target and then continues to get beat on. Obviously without babysitting him, it leads to death. This happens at 10:51 in the log I uploaded. At 10:53 I right click on the mob to turn him.

#3: Sometimes I click Start, and then he'll sit there indefinitely. If I stop and start again, he heads off.

This is using Mordd's Cimmerian 2.1 Beta 4, and Peaso's Horde Hellfire QuestOrder 60+ WIP, in questing mode. Please let me know if I can provide further details.

EDIT: It won't take my full log, so had to rename and start again. I'll post the log once I get all issues to repeat.
 

Attachments

Last edited:
Inactivitytimer fail? Set it to pvp mode in orgrimmar pvp place like I always do and got booted.... My bad if you know about this, but it kinda makes botting useless for me (trying to gear my druid for gearscore so I can get into icc)
 
Anybody fixed or have a fix for "Styx.Logic.Pathing.Navigator" error?
 
peteyboy23 said:
EDIT: It won't take my full log, so had to rename and start again. I'll post the log once I get all issues to repeat.
Click to expand...

Text files compress really well. You'll be able to fit a huge .txt file into a .zip file that you can upload to these boards without much difficulty.
 
Xeno said:
Inactivitytimer fail? Set it to pvp mode in orgrimmar pvp place like I always do and got booted.... My bad if you know about this, but it kinda makes botting useless for me (trying to gear my druid for gearscore so I can get into icc)
Click to expand...

You're going to get PvP gear to get into an endgame PvE instance?
 
About the quest turn ins... from what i've seen the bot copes with that when there's only a single window that allows you to click "Complete Quest" right away, but if there are 2 windows, one with a question mark (exacly like some guy posted above http://www.youtube.com/watch?v=06-hen2mn1Q ) then it's stuck.
[22:39:30:508] Activity: Turning in quests at quest giver Spirit Talker Snarlfang
[22:39:31:532] interact: 0x2B1343F8
[22:39:31:613] interact done: 0x2B1343F8
[22:39:32:825] Activity: Turning in quests at quest giver Spirit Talker Snarlfang
[22:39:33:876] interact: 0x2B1343F8
[22:39:33:956] interact done: 0x2B1343F8
[22:39:35:179] Activity: Turning in quests at quest giver Spirit Talker Snarlfang
[22:39:36:225] interact: 0x2B1343F8
[22:39:36:292] interact done: 0x2B1343F8
[22:39:37:621] Activity: Turning in quests at quest giver Spirit Talker Snarlfang
[22:39:38:251] interact: 0x2B1343F8
[22:39:38:323] interact done: 0x2B1343F8
Click to expand...
here's a log from such an occurance. I was running [Horde] 68-80 Ultimate Questing profile, that's using ForcedQuestList
 
supersonic said:
About the quest turn ins... from what i've seen the bot copes with that when there's only a single window that allows you to click "Complete Quest" right away, but if there are 2 windows, one with a question mark (exacly like some guy posted above http://www.youtube.com/watch?v=06-hen2mn1Q ) then it's stuck.

here's a log from such an occurance. I was running [Horde] 68-80 Ultimate Questing profile, that's using ForcedQuestList
Click to expand...

I had this exact same thing happen to me when I was testing out the updated questing capabilities.
 
Same here, everything works great up until there are 1 window ahead of the complete quest button.
Thanks for a great release, this fixed so many bugs from the last one:)
 
Status
Not open for further replies.
Back
Top