Profile: [Fly][N - Quest] Uldum 83-85 [Kick] Quest: Core Access Codes - Quest - World of Warcraft Description: Replace CombatUseItemOn with CombatUseItemOnV2. Replace: Code: <CustomBehavior File="CombatUseItemOn" QuestId="27777" MobId="46587" ItemId="62542" MobHpPercentLeft="100" NumOfTimes="200" MaxRange="19" X="-10986.97" Y="-2100.066" Z="172.7457" /> With: Code: <CustomBehavior File="CombatUseItemOnV2" QuestId="27777" ItemId="62542" MobId="46587" UseWhenMobHasHealthPercent="100" MaxRangeToUseItem="19" UseItemStrategy="UseItemContinuouslyOnTarget" X="-11035.2" Y="-2100.26" Z="172.8839" />
Hi, Slite62, and many thanks for the log. The profile was attempting to buy a ground mount for a Worgen, which obviously doesn't have any racial-based mounts to purchase. We believe the problem has been corrected in v3080. We are in the process of taking the 'learn mount' code out of the profile, and moving it in the MountHook behavior. Unfortunately, we have a foot in each camp at the moment, and that's how the mistake got made. cheers, chinajade [size=-2]Ref: Slite62's problem report w/log[/size]
Hi, Blandfx, Thank you for the update. It is possible you can work around the problem by doing the quest manually. If so, this article may provide some guidance in that respect: HelpDesk: Working around Bliz quest bugs cheers, chinajade
Thank you once again, MaxMuster! These changes have been folded into v3081. cheers, chinajade [size=-2]Ref: MaxMuster's problem report w/recommended repair[/size]
Profile: [Fly][A - Quest] LK 68-80 [Kick] Quest: Steady as a Rock? Description: Bot just stands there right at the pickup point of the quest item waiting 2 sec then 2 sec continuous. Saw 2 other bots stuck right there lol.
Hi, Neroner, and welcome aboard. We've no chance at assisting you with problems like this, unless you attach your full log that captures the issue. Please see the guide for Reporting Problems or Seeking Assistance. cheers, chinajade
Hi again, Neroner, and many thanks for the log. Here was the problem: [16:10:05.520 D] [InteractWith-v1188(debug)] No viable mobs in area. Excluded Units: Portable Seismograph [InCompetition(2 players within 20.0, expires in 89s)] The two players in the area with you were considered to be "in competition" for interacting with the Portable Seismograph. We tend to do this a fair bit, because "stealing another player's mob/object/whatever" gets you reported, and this is bad for your WoWaccount's health. The problem should've corrected itself in 90 seconds?once the timer expires, you interact with the object (competition or not). However, we went ahead and made some minor modifications to the profile where this shouldn't be a problem in the future. The Portable Seismograph will be considered a resource that it is harmless to compete for (especially since you deployed it). These changes are folded in to v3082. cheers, chinajade [size=-2]Ref: Neroner's original post w/log[/size]
Im having problem with mounting. Bot just runs everyplace and wont mount up. There is an error be thrown that I belive is the cause of it. [21:24:21.927 D] System.InvalidOperationException: Sequence contains no matching element at System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate) at Styx.CommonBot.FlightPaths.(WoWPoint , WoWPoint , XmlFlightNode& , XmlFlightNode& ) at Styx.CommonBot.FlightPaths.ShouldTakeFlightpath(WoWPoint start, WoWPoint end, Single travelSpeed) at Styx.Pathing.MeshNavigator.MoveTo(WoWPoint location) at Styx.Pathing.Navigator.MoveTo(WoWPoint location) at CommonBehaviors.Actions.NavigationAction.Run(Object context) at CommonBehaviors.Actions.ActionMoveToPoi.Run(Object context) at Styx.TreeSharp.Action.RunAction(Object context) at Styx.TreeSharp.Action..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.Sequence..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.Decorator..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.Decorator..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.Decorator..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.Common.HookExecutor.Run(Object context) at Styx.TreeSharp.Action.RunAction(Object context) at Styx.TreeSharp.Action..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.TreeSharp.PrioritySelector..() at Styx.TreeSharp.Composite.Tick(Object context) at Styx.CommonBot.TreeRoot.() [21:24:21.927 D] Clearing POI - Reason Exception in Root.Tick [21:24:21.927 D] Cleared POI [21:24:22.111 D] Changed POI to: Type: Hotspot, Loc: <-8705.345, -388.4914, 188.6454> View attachment 7548 2014-01-13 16.07.txt Also the only thing I changed recently is I learned faster flying yesterday. This started happening first time questing after I upgraded flight speed. Could just be conicidense though
Thanks for the answer... After the change it "semi-works" As in, every time I start the profile, it hearths to the trade district and then heads back to the area I was in and takes up where I left off
Hi, Slite62, Sorry that wasn't a "full" repair. In order to refine it further, we will need to see a new log of what is happening to you now. cheers, chinajade
Hi, Getmunch, and thank you for the log. As described in Reporting Problems or Seeking Assistance, this is obviously not a problem with the profile. You should open a new thread in the Support forum regarding this issue. Over there, they will need to see the whole log to conduct an analysis. cheers, chinajade [size=-2]Ref: Getmunch's original post w/log[/size]
Hi again, Slite62, and many thanks for the log! The problem this time is the MountHook quest behavior. And, we've opened HB-396 ("MountHook forces Worgens to hearth to SW unnecessarily"). Obviously, MountHook currently has several 'issues'. We can think of three possibilities: Just go buy a ground mount your Worgen can use. Any usable ground mount should do. Comment out all MountHook usages in the profile <!-- <CustomBehavior File="Hooks\MountHook" state="True" /> -->This line occurs several times in the profile, so be sure to snag them all. When the profile changes, you may need to do this again. We would recommend against pursuing this solution, if at all possible. Just live with the inconvenience for now Our guess is you are using an account that doesn't know any ground mounts at the moment. If so, this is what is creating the boundary condition that is not handled by MountHook, as we've never seen this problem before. cheers, chinajade [size=-2]Ref: Slite62's log[/size]
Hi Goal: Picking Up Quest - The Eastern Pylon : QuestID - 24721 : To - Ithis Moonwarden : ID - 38263 "This quest was marked obsolete by Blizzard and cannot be obtained or completed."
correct, this is a new account and the worgen hunter is the first char on that account. As for suggestion one, the only one a Worgen lowbie can use is the Swift Mountainhorse sold in Darnassus, and going from Stormwind to Darnassus at lvel 20 is a pain in the.. .well Suggestion two is doable, but I prefer not to mess with the profiles directly So, I'll just live with it for now Thanks for opening an issue for it though!
same with quest Goal: Picking Up Quest - The Northern Pylon : QuestID - 24722 : To - Gremix : ID - 38275 The Northern Pylon - Quest - World of Warcraft This quest was marked obsolete by Blizzard and cannot be obtained or completed.
Hi, Woofie, and thanks for the logs. We don't know where you're getting this information from, but it is simply wrong. WoWHead is showing both quests at intact and doable: Ref: The Eastern Pylon - Quest - World of WarcraftRef: The Northern Pylon - Quest - World of Warcraft You might try clearing your caches and see if that is the problem. This article will help you through that process: HelpDesk: Cache corruption problems The other possibility is a Bliz quest bug. This article describes a few ways that may clear the problem: HelpDesk: Working around Bliz quest bugs cheers, chinajade [size=-2]Ref: Woofie's original post #1 w/log[/size] [size=-2]Ref: Woofie's original post #2[/size]
Hello, I've been using Kick's for about a week now. It's been pretty smooth with just a little help from me along the way until now. I'm alliance in searing gorge, level 49. The bot is trying to do the quest "Recon Essentials". The bot always ends up going inside the caves in searing gorge and running into a pool of lava, effectively killing himself. It will then rez itself in the lava, only for the cycle to repeat. I have tried moving the bot to other locations and restarting, but it always ends back in the lava. Of course, I can do the quest myself, and I will, but it'd be nice to get it looked into for anyone else. Log is attached View attachment log.txt
Hi, Blackout44, and welcome aboard. If you need assistance, we will need the full log attached. Fragments are completely useless most of the time. cheers, chinajade [size=-2]Ref: Blackout44's original post w/log fragment[/size]