What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

mh66 said:
When upgrading Garrison to next stage, char had not enough resources and stood there for some while. Would it be possible to get resources from box when not having enough prior to builidng next stage?
Click to expand...
Yea, this would be possible.
Do you not have a log for when this happened?
 
r0x0r said:
This is my first alliance char, Night Elf Veng.

For some reason the character stops to move and stays idle after completing some quests, then i have to manually move him or finish the quest / bonus objective and it will continue running the profile, after x time it will do it again.

This is the latest log file
Click to expand...
The log doesn't show that any errors are happening, but I do see where the KillUntilComplete behavior stood still for 4minutes.
Have you tried a fresh installation?
 
Gordohorda said:
Anyone help me on this error: [Compiler Error]: C:\Users\Gordo\Desktop\que nao vai da oq\Quest Behaviors\QuestBehaviorCore\Utility\Query_Database.cs(23,22) : error CS0234: The type or namespace name 'Database' does not exist in the namespace 'Styx.CommonBot' (are you missing an assembly reference?)
Click to expand...
This is not a profile error.
Do a fresh install of your bot and it should work again.
 
chainapockets said:
Sometimes the Stormheim profiles gives me randomly the error , doesn't matter if i stand in Monk Hall, in Dalaran, in front of the Flightor in Dalaran oder in Stormheim.
Got this error yesterday, after 100x reloads it worked, now the same again.

after doing 1-2 quests manually, it works.
Click to expand...
It was stuck on a quest then - I'd need a log to see why it was.
There may have been a bad coordinate somewhere.
 
hojthemoose said:
No matter what zone i am in bot goes to an area and just farms mobs. Have active quests i can do and even run to them and click bot to start but just mounts up and runs across map to farm mobs.
Click to expand...
There's no way I could fix this issue without a log.
 
garoboldy said:
Anyone have stats on 100-110 timeframe?

- Duration
- Stops/Starts
- Bugged Quests (needing manual assistance)
- Classes used
Click to expand...
So far I've only recorded two of my testers.

1) Night Elf - Demon Hunter, Havoc - 19hours for 98-110. Only stucks was it Fel Rushing off mountains.

2) Alliance Pandaren - Monk, Windwalker - 20hours for 100-110. Only stuck was in Highmountain which was near a big ship. I've added a blackspot that will fix that.

These testers run 24/7 under my supervision, so there was no stops.
 
I have a feeling you are probably aware, but hit 110 in Stormheim, and then loaded the Suramar quests, and it takes my Warlock to Exodar to fight some more demons. The path it takes around Exodar, to click the portals is terrible. Is this a profile issue, or bot mesh issue? This scenario is full of demons, non-stop walking all over the place, and basically the bot gets caught in an infinite fight loop because demons don't stop. Typically after a while, you'll just die from too many of them.

Scenario: In Defense of Exodar
 
Nonary said:
I ran into many issues with my warrior last night with it trying to fly into Warsong Keep in Borean Tundra. it would get stuck for hours shifting between one point to another. I've attached the log, but curious to know if it was a profile issue or just something wrong on my end.
View attachment 213870
Click to expand...
There's strange errors being thrown in your log.
I believe this may have been an issue with the bot's navigation system - and it should be fixed for the next update.

The only thing I could suggest at the moment is try a fresh install.
 
Rogue said:
[Flightor] Mount up failed unexpectedly. Blacklisting current location.
[Flightor] Mount up failed unexpectedly. Blacklisting current location.

Only with my lvl 100 Paladin when I start questing in legion, all other toons are ok !
Click to expand...
Start your Paladin in your Paladin class hall.
 
Lipstick said:
[02:43:54.706 N] Honorbuddy v3.0.16279.860 started. [02:43:54.940 D] Reloading - Pastebin.com

Log in the pastebin

Here's a log from a clean install of HB: [02:50:10.331 N] Honorbuddy v3.0.16279.860 started. [02:50:10.543 D] Reloading - Pastebin.com
Click to expand...
This seems to be a new issue brought on by Honorbuddy 3.
H3 has issues with water sometimes - and the treasure it's getting stuck on is: Adventurer's Sack

If you manually get this treasure and start the bot again - it should work.
In the mean time, I'm looking to remove this treasure from the profile until better navigation logic can be added for it.
 
Guile said:
Hey Echo.

I see this issue has been posted already.

Toon wants to do a quest that has already been done.



I ran the profile through buddy store and also downloaded the profile and ran it manually.
Click to expand...
In-game, can you type: /dump IsQuestFlaggedCompleted(34948) and tell me what it returns?
 
kkloeskes said:
Hello

profile worked fine from 91-108, but now it says nothing more to do..
I tried to manual load something but it always says the same. He was startung at Stormheim. Finished all other before.

[LoadProfile-LoadPr(info)] Loading profile 'Legion\Auto-Loader.xml'
Changing current profile to Legion Auto-Loader ($Rev: 5593 $)
[LoadProfile-LoadPr(info)] Loading profile 'Class Hall Loaders/[N-Quest] Priest [Echo].xml'
Changing current profile to [N-Quest] Priest Class Hall Loader [Echo] ($Rev: 5652 $)
Bot stopping! Reason: Nothing more to do.
Click to expand...
Currently the auto-load logic for the class hall profiles isn't all that great.
You may want to load the questing zones manually.
 
Morx said:
I have a feeling you are probably aware, but hit 110 in Stormheim, and then loaded the Suramar quests, and it takes my Warlock to Exodar to fight some more demons. The path it takes around Exodar, to click the portals is terrible. Is this a profile issue, or bot mesh issue? This scenario is full of demons, non-stop walking all over the place, and basically the bot gets caught in an infinite fight loop because demons don't stop. Typically after a while, you'll just die from too many of them.

Scenario: In Defense of Exodar
Click to expand...
When I set this up, I didn't specifically specify a path.
There's just a few hotspots with a very high collection distance to detect the portals with.

This is typically my method of handling farm zones because it cuts down on bot-trains dramatically and every path is never the same.

I've not really been able to test this on multiple characters yet, but the characters I did test it on didn't have much issue.
It could have been that the path you got wasn't all too great.

What spec was your Warlock?
I can send a Warlock tester to there to see if it has similar issues.
 
Trying to start @ Azsuna but it gives me this error...Any ideas?

[Compiler Error]: C:\Honorbuddy\Quest Behaviors\Misc\DMFR_Tonk.cs(322,38) : error CS0117: 'Navigator' does not contain a definition for 'GeneratePath'
[Compiler Error]: C:\Honorbuddy\Quest Behaviors\Misc\DMFR_Tonk.cs(355,37) : error CS0117: 'Navigator' does not contain a definition for 'GeneratePath'
 
Alex1098 said:
Trying to start @ Azsuna but it gives me this error...Any ideas?

[Compiler Error]: C:\Honorbuddy\Quest Behaviors\Misc\DMFR_Tonk.cs(322,38) : error CS0117: 'Navigator' does not contain a definition for 'GeneratePath'
[Compiler Error]: C:\Honorbuddy\Quest Behaviors\Misc\DMFR_Tonk.cs(355,37) : error CS0117: 'Navigator' does not contain a definition for 'GeneratePath'
Click to expand...
The quest behavior DMFR_Tonk is not an official quest behavior, and it's what's giving you issues.
Delete this file from your Honorbuddy\Quest Behaviors\Misc folder and it should work again.
 
EchoTiger said:
When I set this up, I didn't specifically specify a path.
There's just a few hotspots with a very high collection distance to detect the portals with.

This is typically my method of handling farm zones because it cuts down on bot-trains dramatically and every path is never the same.

I've not really been able to test this on multiple characters yet, but the characters I did test it on didn't have much issue.
It could have been that the path you got wasn't all too great.

What spec was your Warlock?
I can send a Warlock tester to there to see if it has similar issues.
Click to expand...
Was Affliction Warlock, but I don't think this zone is tuned very well. You go here as a result of the Falling Star quest I believe, and when I went here on my 104 Hunter I finished the whole thing in very quick time. On both 110 Warlock and Shaman, both had a lot of troubles, and died 10+ times to complete it. This is even without bots. So many demons, so many adds, it's just really hard at 110, in bad 790'ish gear.

The path mine took was from Priest Velen, it went off to the left of his big bubble, through a small corridor. 3 Demons path through there, and there's also an elite demon that is close by as well.
 
You must log in or register to reply here.
Back
Top