Questing errors

Been having trouble with three separate quest profiles, they all stop like this.
Is this a bot issue or a profile issue? (been using kicks cata profiles), and is there a fix?

Code:

[04:01:44.511 D] Compiling expression '((HasQuest(26537)) && (IsQuestCompleted(26537)))' @ line 1116[04:01:44.705 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[04:01:44.710 N] Could not find quest giver NPC with ID 43168 in database.
[04:01:44.710 D] Stop called!
[04:01:44.710 Q] Bot Stopped! Reason: Could not create current in quest bot!
[04:01:44.718 D] Activity: Honorbuddy Stopped
[04:01:45.731 D] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.CommonBot.TreeRoot.()
   at Styx.CommonBot.TreeRoot.()
[04:01:45.733 D] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.CommonBot.TreeRoot.()
[04:01:45.731 D] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.CommonBot.TreeRoot.()
   at Styx.CommonBot.TreeRoot.()
[04:01:45.733 D] System.Threading.ThreadAbortException: Thread was being aborted.
   at Styx.CommonBot.TreeRoot.()

 

Found a sort of fix I guess, take the ID given in error (43168), go to Gravel Longslab - NPC - World of Warcraft, find where it is and pick up the quest manually, restart bot - Seems to work for now.

 

Hi, Squeese,

Good show on the fix!

I'd contact the profile writer and let him know the quest, and the X/Y/Z of the NPC needed. The profile writer will need to add an X/Y/Z to the Pickup line in the profile.

Honorbuddy has a lot of NPCs locations already accessible to it. But like with anything, the location database is not perfect. It supplements the database by adding missing NPCs within 50 yards or so of you, as you travel the world. Alas, if the NPC is in a section of the world that has yet to be travelled, it won't know where the NPC is.

Profile writers 'help this out' by providing the X/Y/Z of the NPC in their Pickup lines. If you inform the profile writer of the problem (and provide the quest and location specifics), hopefully someone else won't have to suffer through the same problem.

cheers,
chinajade