As Lvl 5 Orc-Warri he swim to Ratchet and wants to get all the Lvl 15 Quests like QuestName="WANTED: Cap'n Garvey" QuestId="895"... Not questing in startzone Last Quest's was: Moving closer to Clattering Scorpid -Face the target -Strike Looting Clattering Scorpid Moving to Type: QuestPickUp Moving closer to Sand Shark -Strike
sorry about that. seems in fixing one bug, i inadvertently added another. fixed. reuploading within 3 minutes of this post.
if you have any questing profiles above level 20 that you'd like to contribute please do and I'll put credit in the main post. Make it above 25 cuz Im almost done here with 25
Had a lvl 4 undead lock that I tried to use this on. He ran all the way back to the beginning and kept clicking on an npc that had a quest I had already completed and turned in instead of pick up where I am at. So then I decide to roll another lock lvl 1. He did fine up until the quest where you have to go hear the story of 3 NPCs. At that point HB crapped out and gave an error: "Unable to compile CustomBehavior for tag: <CustomBehavior QuestId="24960" File="TalkToAndListenToStory" NpcId="49231" /> Honorbuddy stopped" I put all the CS files in the Quest Behaviors folder and I'm running the latest version of HB. Let me know if I missed something as its totally possible. I haven't run a bot since Glider.
Sorry about that. Thank you for letting me know. I believe I fixed it. Try to download and use again and let me know. Thanks!
Helping with testing: <PickUp QuestName="Samophlange" QuestId="894" GiverName="Sputtervalve" GiverId="3442"/> Could not find quest giver NPC with ID 3442 in database. Could not create current in quest bot! Sputtervalve - NPC - World of Warcraft The bot stops in Kabestan
uh, ya, so he rode the zeppling to org.. now he's running to ratchet to pick up WANTED: Cap'n Garvey - Quest - World of Warcraft problem is, you have to be 14 to get that quest and i'm lvl 10
just looking ast the profile, <If Condition="(Me.Race == WoWRace.BloodElf) || (Me.Race == WoWRace.Tauren) || (Me.Race == WoWRace.Troll) || (Me.Race == WoWRace.Orc) || (Me.Race == WoWRace.Undead) && (Me.Level = 10)"> should the "&&" be there? should it just be "&&"?
yeah that was a mistake i added when i was fixing another bug. i forgot to remove it. but no, it should be neither. "&& (Me.Level = 10)" is an unnecessary predicate, as checkpoint will handle it and it just seems to confuse the bot. try it now i updated it with that line removed.
but just for your own educational reference, the reason & is there is because it's within a <> and thus must be coded thusly. Nevertheless, doesn't work, and unnecessary, so removing it is the best bet.