Got a quick question, using a level 85 warrior to run Gundrak, however the CR seem to never use Bladestorm. What doesn't the bot use it?
Wondering if there is a way top prevent Guardian druid from using healing touch? I have set DPS Off-Heal Allowed to False. I have set Healing Touch to 0.
View attachment 9228 2014-09-06 22.56.txt running a gundrak farm profile and at mark [06:12:00.280 D] the bot get's "stuck" it's not physically stuck but rather at the point the profile seems to break and won't work until i aggro another mob manually. Posted in the profiles thread but we think it's unrelated to the profile itself. This happens often within 1-2 hours for overnight farming, but it can also not happen at all, or happen at different times into the farm. Currently using a fresh HB install and set the log to verbose to gather more info
Klikkoklakk, Thanks for the post. Your description does not match the result of my testing and not enough information is provided to research it further. Please see Reporting Singular Bugs (click here). and I will be glad to look into those issues for you. Thanks and good luck with your Shaman, Bobby53
Thanks for the post, but the description doesn't match the results of my testing and there is not enough info provided to research for you. Please see Reporting Singular Bugs (click here). Once that info is available I can look into this further for you, Bobby53
Edsaxe, Thanks for the post, but there isn't enough info to advise. Please follow the steps in Reporting Singular Bugs (click here). With that info available I can better respond to your question. Thanks for the post and good luck with your Druid, -Bobby53
will5757, Thank you for the post with the log attached and the timestamp of the issue you observed! Based on the log file results and your description I see the following entries relevant to your question: Code: [06:12:00.279 D] [InteractWith-v1597(debug)] WaypointVisitStrategy set to Random[06:12:00.280 D] Goal: InteractWith-v1597: In Progress (no associated quest) Interacting with Altar of Slad'ran [Ref: "Gundrak - Optimized Gold Farm - Heavy Pulls" @line 535] [06:12:00.280 D] Inserted new hook [Combat_Only @0] 19543409-5dff-4a4e-8981-bca11dcbfce3 [06:12:00.280 D] Inserted new hook [Death_Main @0] 3cf8666c-b914-4623-a991-907b3ccca9a5 [COLOR=#ff0000][B][06:12:17.502 N] (Singular) info: 20 seconds since Questing BotBase last called Singular[/B][/COLOR] [06:12:37.568 N] (Singular) info: 40 seconds since Questing BotBase last called Singular [06:12:57.634 N] (Singular) info: 60 seconds since Questing BotBase last called Singular [COLOR=#808080][I][B]... lines for next 29 minutes deleted to save space ...[/B][/I][/COLOR] [COLOR=#ff0000][B][06:41:41.879 N] (Singular) info: 1784 seconds since Questing BotBase last called Singular[/B][/COLOR] [06:41:57.673 N] (Singular) [WoWRedError] You can't logout now. Singular is a Combat Routine. It is a component that is used by the BotBase (as well as QuestBehaviors and sometimes Plug-ins) to attack or heal. This allows the BotBase to be insulated from having to know what spells and abilities the current character has -- it can simply say "go kill this target". Additionally, the BotBase must call the combat routine repeatedly until it does not want the combat routine to continue doing that task. In other words, the Combat Routine does not get to decide when its Pull or Combat behaviors are called, it can only react when they are called. To help troubleshoot situations like you described, I added code to Singular to detect when it hasn't been called for the prior 20 seconds. The log messages highlighted above show that Singular was not called for almost 30 minutes before the inactivity timer logged out. Based on this it is an issue with: 1. InteractWith - not sure if the interact failed and it did not detect this so the profile was stuck waiting for something to occur which never does 2. Questing Profile - either is not specifying the correct parameters to InteractWith QB or questing profile logic after the interact may not be correctly detecting the situation that occurs Hope that helps -Bobby53
Bobby53, When using Tyrael (non-movement botbase) the Singular will open try to move a little, can this be disabled? [Singular] MoveToSide: moving diagonally Right for 1.6 yds
Hello, I was redirected here from Azyuls' thread for Dungeon farming. The issue happens right before I die, and then i get problems since the script doesn't have dungeon revive support. Thing is that the bot just bugs out and I suppose the mobs beat me to death. [16:18:52.133 N] (Singular) FaceTarget: facing since more than 5 degrees [16:18:52.134 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.134 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.201 N] (Singular) FaceTarget: facing since more than 70 degrees I've attach the log files, Azyul is pretty certain that this is a Singular issue. Two of the files are my Frost mages' specific logs, one is general log. Thanks in advance
Greeting, got a small suggestion, if you could add the option to use Disorienting Roar as a druid? When 3 or more mobs are in 10 yards from you.
Moronko, Thanks for the log files. Not quite sure what is meant by a general log. If details needed regarding what should be submitted please see Reporting Singular Bugs (click here). A bit unclear what you mean by bot bugs out. In looking at the log files, there are a number of messages regarding facing: Code: [16:18:51.356 N] [Singular] Switching to BotPoi: Mutate Horror.2038![16:18:51.390 N] [Singular] MoveToSide: moving diagonally Right for 1.3 yds [16:18:51.807 N] (Singular) <<< ADD >>> CurrentTarget now: Mutate Horror.2038 h=100.0%, maxh=15718, d=2.1 yds, box=1.0, player=N, hostil=Y, faction=1692, loss=Y, face=N, agro=Y, pagro=Y, IsBotPoi=Kill, TargetIndex=1 [16:18:51.808 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:51.808 N] (Singular) FaceTarget: now facing Mutate Horror.2038 [16:18:51.877 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:51.877 N] (Singular) FaceTarget: now facing Mutate Horror.2038 [16:18:51.939 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:51.939 N] (Singular) FaceTarget: now facing Mutate Horror.2038 [16:18:52.001 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.002 N] (Singular) FaceTarget: facing since more than 5 degrees [16:18:52.002 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.003 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.068 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.069 N] (Singular) FaceTarget: facing since more than 5 degrees [16:18:52.069 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.069 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.133 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.133 N] (Singular) FaceTarget: facing since more than 5 degrees [16:18:52.134 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.134 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.201 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.202 N] (Singular) FaceTarget: facing since more than 5 degrees [16:18:52.202 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.203 N] (Singular) FaceTarget: facing since more than 70 degrees [16:18:52.274 N] (Singular) PetsCurrentTarget: changed to: Laj.1FF9 h=90.2%, maxh=169740, d=4.7 yds, box=3.0, boss=N, trivial=Y, player=N, attackable=Y, neutral=N, hostile=Y, entry=17980, faction=16, loss=Y, facing=N, blacklist=N, combat=Y, flying=N, abovgrnd=N, IsBotPoi=Kill, TargetIndex=1, tagme=Y, tagother=N, tapall=N [16:18:52.277 N] (Singular) FaceTarget: facing since more than 5 degrees [16:18:52.345 N] (Singular) FaceTarget: facing since more than 5 degrees [16:18:52.408 N] (Singular) .... [Combat] h=48.3%/m=100.0%, pet=56.7%, fof=0, brnfrz=0, ttd=-1, th=100.0%, dist=2.1, melee=True, [B]face=True,[/B] loss=True, fboltstks=0, livbomb=0 There really isn't code that can "bug out" regarding facing which are the messages cited. If your character is not facing the current target and combat routine movement is enabled, then it will face the target. Facing is based upon HonorBuddy API responses on whether it is facing and requests to face when we arent. The one thing I see is the MoveToSide behavior being invoked where it tries to gather all mobs attacking your character in front. Have added a setting in next release to disablethe move sideways behavior. -Bobby53
Abyssiion, Cast of Disorienting Roar is already used. Cast if Health < 40% and 3+ mobs in combat with you. -Bobby53
Well when I said it bugs out I ment that something happens with it that causes it to die.. I've never seen what actually happens, just at some point, while farming botanica, it mounts up and goes to the ledge of hellfire peninsula (on the ground mount yes..). We figured out that it is a Singular problem, since something happens in combat that makes my character die and there is no dungeon death support in that script.. Still it doesn't happen to the other people, so I'm wondering is there a fix or something? Anyways Azyul told me that showing you the logs and saying that this happened right before I died is enough.. He is also pretty certain that this is a singular issue. I hope you can help..
Moronko, Am not clear on which problem is being described here. Mounting up and riding to the ledge of HP is done by the botbase or the questing profile, not the combat routine. If that is another problem that needs to be researched I recommend posting back with the profile author or in HonorBuddy Support. As for the bugging out issue, the only thing I see in the logs in proximity to the characters death are several attempts to Move Sideways to gather mobs in front. There are some refinements to this behavior in the next release, but for now you can click Class Config and try setting "Keep Melee Mobs Front" to 'false'. Next release also includes improvements to Frost Mage Solo behavior that should improve kills and survival. Look for that to be posted soon. -Bobby53
Bobby, I'm simply saying that because of my hero dying inside of instance this thing with riding ground mount from Netherstorm to the ledge near Black Portal occurs. It's caused by no support for "INSIDE INSTANCE DEATHS" in the Dungeon farming script. I'm trying to ask you how to prevent my hero from dying inside of the instance, because something obviously happens when a 90lvl fully prideful geared mage dies in Botanica(lvl 70 Normal Dungeon). I did try to set "Keep Melee Mobs Front" to false before I posted here, with no positive results. So I ask you, if you could, please tell me how to prevent my hero from dying inside of Instance. And yes,this didn't use to happen until 4-5 days ago. I tried reinstalling HB but it didn't help. Thanks in advance.
Heya! I just tried and see if it used when below 40% while having 3+ mobs on me. It did not cast disorienting roar. Was testing it inside a dungeon with Azyul's Gundrak profile Here is a log: View attachment 3380 2014-09-23 17.30.txt Can you see why it doesn't cast Disorienting Roar?
