The toon had just finished a quest, "an ambitious plan" in hellfire peninsula, and when it arrived at its destination, it abandoned the quest to accept it again!
Profile: [Fly][N - Quest] Hyjal 80-82 [Kick] Description: Bot not use the Portal Profile Code: Code: <If Condition="HasQuest(25928) && IsQuestCompleted(25928)"> <RunTo X="4676.442" Y="-3682.449" Z="697.7275" /> <CustomBehavior File="WaitTimer" WaitTime="2000" /> <CustomBehavior File="FlyTo" DestName="Turnin Quest" X="4477.372" Y="-2718.52" Z="1101.165" /> <TurnIn QuestName="Tortolla's Triumph" QuestId="25928" TurnInName="Tortolla" TurnInId="41504" /> <PickUp QuestName="The Ancients are With Us" QuestId="25653" GiverName="Tortolla" GiverId="41504" /> </If> Here the Log: Code: [19:28:33.914 D] Compiling expression 'HasQuest(25928) && IsQuestCompleted(25928)' @ line 2438 [19:28:33.956 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedMoveTo. [19:28:33.956 D] Goal: Moving to <4676.442, -3682.449, 697.7275> [19:28:37.113 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedMoveTo. [19:28:37.113 D] Goal: Nothing [19:28:37.113 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. [19:28:37.113 D] Goal: WaitTimer-v1085: "In Progress (no associated quest)" Waiting for 2s [Ref: "[Fly][N - Quest] Hyjal 80-82 [Kick]($Rev: 2166 $)" @line 2440] [19:28:37.113 D] Activity: Wait time remaining... 2s of 2s. [19:28:37.675 D] Activity: Wait time remaining... 1s of 2s. [19:28:38.194 D] Activity: Wait time remaining... 0s of 2s. [19:28:39.166 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. [19:28:39.166 D] Goal: Nothing [19:28:39.166 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. [19:28:39.166 D] Goal: FlyTo-v1129: "In Progress (no associated quest)" Flying to Destination: Turnin Quest (<4477.372, -2718.52, 1101.165>) [Ref: "[Fly][N - Quest] Hyjal 80-82 [Kick]($Rev: 2166 $)" @line 2441] [19:28:39.167 D] Behavior flags changed! All -> 0x0000005B [19:28:39.193 D] Activity: Loading Tiles [19:28:39.193 D] Loading Kalimdor_38_22 [19:28:39.328 D] Could not find portal to take. [19:29:17.338 D] Updating repair cost for current equipped items. New value: [1g93s45c] [19:29:17.341 D] Could not find portal to take. [19:29:39.329 D] Garbage collected 2 nav tiles [19:29:39.329 D] Loading Kalimdor_39_23 [19:29:39.485 D] Could not find portal to take. [19:30:39.500 D] Garbage collected 1 nav tiles [19:30:39.500 D] Loading Kalimdor_39_23 [19:30:39.657 D] Could not find portal to take.
Hi, Tumbum, and thanks for this log. HB-364 was supposed to repair this problem. I've opened HB-445 ("With .721... Could not find vendor: ' [0]' blacklisting!"), and linked it to HB-364 as unresolved. I've attached the information you have provided here to the new issue. cheers & thanks again, chinajade [size=-2]Ref: Tumbum's problem report w/log[/size]
Hi, Tumbum and MaxMuster, We've captured the issue to Known Bugs List: Cata 80-85, and will have to visit the problem with the specific quest behavior the next time we're through the area. cheers & thank you both, chinajade [size=-2]Ref: Tumbum's problem report w/log[/size] [size=-2]Ref: MaxMuster's follow-up report[/size]
Hi, ---TreMolitE---, and thanks for the log. // We see you failing to go through the portal to start the encounter... [10:51:36.638 D] Goal: GoThruPortal-v1190: "In Progress (no associated quest)" Moving through Portal [Ref: "[Fly][N - Quest] Hyjal 80-82 [Kick]($Rev: 2166 $)" @line 3190] [10:51:36.639 D] [GoThruPortal-v1190(debug)] State_MainBehavior: MovingToStartPosition [10:51:36.651 D] Activity: Moving to Portal [10:51:36.652 D] [GoThruPortal-v1190(debug)] State_MainBehavior: MovingToPortal [10:51:36.695 D] Behavior flags changed! All -> 0x00000059 [10:51:36.695 D] [GoThruPortal-v1190(debug)] Portal Entry Timer Started [10:51:36.696 D] [GoThruPortal-v1190(debug)] Entering portal via <4329.553, -3294.315, 1037.715> [10:51:42.299 D] Inserting Cenarius [Gossip, Questgiver] into the database! [10:51:46.727 N] [GoThruPortal-v1190(warning)] Unable to enter portal within allotted time of 10s The log clearly shows you having problems trying to go through the portal. We've captured the issue to Known Bugs List: Cata 80-85, and will have to examine the issue the next time we get a toon through the area. As a work-around, just do the quest manually, turn it in, step back outside the portal, and start Honorbuddy again. Your log also shows some other disturbing things: What looks like a damaged Honorbuddy installation: [07:19:37.443 N] Compiler Error: error CS1508: Resource identifier 'Resources.resources' has already been used in this assembly An unreasonable number of these: [10:43:21.848 D] (Singular) (Singular) reset target timer to 00:00:20 It may be time to think about a 'clean install'. Instructions here: HelpDesk: "Clean installing" Honorbuddy cheers, chinajade [size=-2]Ref: ---TreMolitE---'s original post w/log[/size]
Hi, Tumbum, and thanks for the log. I see nothing here that is related to a problem with the profiles. This looks like a problem with your installation, since all your plugins and parts of Honorbuddy appear to be affected. I have never seen these errors with .721. However, .722 has been out for a while, and has solved a lot of problem. You might try upgrading and see if that will clear your problem. cheers, chinajade [size=-2]Ref: Tumbum's original post w/log[/size]
Hi, Shipley, and thanks for the log. [18:01:21.877 N] Honorbuddy v2.5.9088.718 started. The current release of Honorbuddy is .722. Let's try upgrading first, and see if the problem persists. This log is not much help, otherwise. As, the log stops after Honorbuddy is initialized, but before any attempt is made to run a profile. cheers, chinajade [size=-2]Ref: Shipley's original post w/log[/size]
Hi, Tumbum, It appears the issue is caused by a WoWclient issue with the quest. For more information, please see the comments here: Madness - Quest - World of Warcraft. In the meantime, we've tried to address the problem in v3113 when it happens. We've no way to test the code modifications, however. cheers, chinajade [size=-2]Ref: Tumbum's problem report w/log[/size]
Hi again, Kaotic184 and thanks for the follow-up and log, I've no explanation for why this is happening to you, unless your toon's quest state has somehow gotten damaged. A corrupted cache is by far the most frequent cause of the problem, but there are other ways a toon's quest state can be damaged also. This article should outline all known causes and work-arounds: HelpDesk: Quest giver is not offering expected quest Sorry for the inconvenience. cheers, chinajade [size=-2]Ref: Kaotic184's follow-up post w/log[/size]
Hi, Dayloon, and thanks for the log. The log terminates before the error message you cite. The best we can offer at the moment is to see if this article will help you sort the issue: HelpDesk: Quest giver is not offering expected quest. cheers, chinajade [size=-2]Ref: Dayloon's original post w/log[/size]
Hi, Methodone, and many thanks for the log. You've got a couple of things going on. Your first problem: [00:16:48.469 D] Activity: Downloading Mesh... You've got a newly installed Honorbuddy, and Honorbuddy is downloading navigational mesh files from a BosslandGmbH server and caching them locally. Once you get the meshes, this should no longer be a problem again until mesh updates are pushed. While meshes are downloading, Honorbuddy has a bad habit of just 'standing around'. The toon won't even defend itself while this is happening. This is not a problem with the profile, and there is nothing the profile can do to abate the problem. Just be patient, and your mesh cache should be completed (in pieces) over time, and the problem will go away naturally. Your second problem, is your Honorbuddy is mis-installed: [00:07:39.870 D] Executable Path: E:\Honorbuddy.exe You have installed Honorbuddy to the root of a Windoze disk, and this is very bad. Instead, you should install it to a sub-folder like E:/Honorbuddy/. This is probably why your Combat Routine (Singular) is failing with lost of these messages: [00:17:10.546 D] (Singular) (Singular) [WoWRedError] Spell is not ready yet. [00:17:10.546 D] (Singular) (Singular) [CombatLog] SPELL_CAST_FAILED Arcane Shot#3044 failure: 'Not yet recovered' To correct this problem, you will need to do a 'clean install' of Honorbuddy. This article will help you do that: HelpDesk: "Clean installing" Honorbuddy Also, you probably want to give one of the installation guides a look. Your choice, text or video: CodenameG's excellent [VIDEO] How to Setup HonorBuddy. (narrated) Tony's excellent A quick Hb guide/presentation for a fast setup cheers & welcome aboard, chinajade [size=-2]Ref: Methodone's original post w/log[/size]
Hi, Lickalime, Kmica is spot on with this. You can find a concrete example of what you seek in the HelpDesk: Questing profiles and the Loremaster achievement article. cheers & happy hunting, chinajade
Hi, Wiedst, For assistance with problems like this, we really must see the log file where the problem occurs. Ref: [Guide] How to attach your log But alas, the news is even worse. The German courts have enjoined BosslandGmbH and its employees from allowing German users from using the Questing and Gathering capabilities provided by Honorbuddy. You can find more information here: Honorbuddy Deutsche Version - Pressemitteilung In short, we will not be able to assist you with questing problems. Also, any attempt to use the BosslandGmbH forums to circumvent the court order is a bannable offense. Please do not make that mistake. You can find more information about that here: HelpDesk: What will get my BosslandGmbH forum account banned? cheers & sorry we are forbidden to help, chinajade
Hi, Daarno, and thank you for the log. That quest is a bit glitchy. What happens is... The questgiver gives you a Sanctified Crystal item to use for the quest. The Sanctified Crystal is consumed on use?successful or not. When using the item on the Voidwalker, the Glowing Sanctified Crystal takes several seconds to spawn after killing the Voidwalker. Sometimes, the Glowing Sanctified Crystal doesn't spawn at all. If the Glowing Sanctified Crystal doesn't spawn, we have to go back to quest giver to get another one. We abandon the quest when returning to the quest giver to prevent subsequent glitches. If you actually saw the quest marked as 'complete', then the WoWclient was slow in doing so. Honorbuddy had already made its decision to return and try again. This can happen if your connection is laggy. Either be patient with the profile, or do the quest manually, and start Honorbuddy again. cheers, chinajade [size=-2]Ref: Daarno's original post w/log[/size]
Hi, Frostyforty, If you need assistance, please see the guide for Reporting Problems or Seeking Assistance. We will be unable to help you with problems like this without a log file that captures the issue. cheers, chinajade
Thanks for the problem report w/screenshot, MaxMuster. We've captured the issue to Known Bugs List: Cata 80-85, and will need to get a toon back through the area to examine the problem. cheers, chinajade [size=-2]Ref: MaxMuster's problem report w/screenshot[/size]