Ruinit said:Here is a log of some of the issues I hope it helps. Bobby I have a larger log also, but it exceeds the 1mb limit so let me know if you need it.
<!-- if we have done warchief's command breadcrumb before, then use portal -->
<If Condition="!HasQuest(27721) && IsQuestCompleted(27721)" >
<CustomBehavior File="Message" Text="Using Mount Hyjal Portal" LogColor="Green" GoalColor="Green" />
Drewdenman said:But it still spams the board to pick it up. Also attached a log of starting the bot and it spamming the board.
I'm getting this. I've tried exiting and restarting. Here's my log.
Could not find quest giver NPC with ID 41068 in database.
Could not create current in quest bot!
[InteractWith(warning)]: Found attribute via its alias name 'GossipOption'.
Please update the profile to use its primary name 'GossipOptions', instead.
[InteractWith(warning)][ForcedDismount(warning)]: The 'QuestId' attribute's value may not be zero. For now, we allow it for purposes of backward compatibility; however, it will be ignored. In a future release, a QuestId of zero will be explicitly disallowed.
webhond said:[AbandonQuest(fatal) @line 1159]: Cannot find quest with QuestId(25303).
Fatal error. Stopping Honorbuddy
webhond said:[AbandonQuest(fatal) @line 2037]: Cannot find quest with QuestId(25514).
Fatal error. Stopping Honorbuddy.
[21:17:09:36] Compiling quest behavior from 'C:\Users\Laptop\Desktop\HB\Quest Behaviors\MountVehOnly.cs'
[21:17:09:738] Goal: MountVehOnly: In Progress
[MountVehOnly(warning)]: Found attribute via its alias name 'NpcMountId'.
Please update the profile to use its primary name 'VehicleMountId', instead.
weischbier said:I don't know why or what this causes. I always test Profiles with a fresh HB and its delivered CC and QB's.
Hi, bobby53.
Just started using your profile and it went great until i discovered this problem where it did stop the bot itself.
The quest that got "bugged" is "An offering for Aviana". The bot did just stop after did problem.
Quoting the problem.
I see a warning, and no errors--thus, no problems.
This profile was written before some stronger error checking went into Honorbuddy. Older profiles will frequently trigger these "warnings", but its not a problem. Have you read through the thread with the previous explanations of this?
What is you concern?
cheers,
chinajade