What Class+Spec are you?: Rogue, Sublety What 'context' is the bot in? (Instance, BG, Normal): BG What level are you?: 90 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? [Singular] LOGMARK # 3 at 15:59:55.281 What happened (be specific)? Even though it's set to STEALTH ALWAYS WHEN OUT OF COMBAT it doesn't do it - at all. Haven't seen it do it yet Did you attach a complete debug log? (choose one: YES or YES)
Bobby, Can you tell me a way to set up Singular to heal Wrathion for the legendary cloak quest? Singular heals a few npc's and friendly targets already I just want to add Wrathion?
Druid - Balance Questing in Plaguelands Toon cant choose who to kill first a Yellow or a Red Mob. Running crazy around between this 2 Mobs.
Giwin, Thanks for the diagnostic log and the anchor for the point you saw it. The problem is due to Singular using its Sap Adds logic prior to learning the Sap ability. This should only be occurring only for Rogues at Levels 10 and 11 encountering a target with another target within Sap Distance setting. The issue will resolve once hitting Level 12 or the user can disable the use of Sap during Pull on Adds by setting the Sap Adds Distance to 0. This issue will be fixed in the next release, -Bobby53
Logandros, Thanks for the post. The log file was created as: Code: [16:35:57.124 D] LogLevel: Normal so lacks the diagnostic info needed for me to research what occurred. Please also remember to set a LOGMARK at the point you see AOE fail. I wasn't seeing a problem with my Feral on AOE so providing that detail so I can research why it didnt work for you would be very helpful! -Bobby53
dmbardal, Thanks for the log files. When submitting a logfile regarding a problem you would like researched / resolved, please be sure to set the HonorBuddy Log Level to Diagnostic. All of the attached log files were created with: Code: [11:24:49.660 D] LogLevel: Normal which lacks the detail necessary. Please see the Reporting Bugs [CLICK HERE] for steps on creating a post which contains all the necessary info. As for logging out of HB and WOW, that is not something that your Combat Routine would do and would be controlled by HB, the BotBase, a Plugin, etc. Although the last line in the log is: Code: [11:45:04.857 D] (Singular) (Singular) info: 1201.3 seconds since BotBase last called Singular (now in OnBotStop) this is just an informational message from Singular saying if you get in a fight and your toon is not fighting back, it is because Singular wasn't being called. In the case of fishing, there wouldn't be a fight so this isn't an error (which is why the message is referred to as informational.) Also, 1201.3 seconds equates to roughly 20 minutes (rather than the 10 reported.) As I look at your HonorBuddy settings, you have the following in effect: Code: [11:24:49.660 D] LogoutForInactivity: True [11:24:49.660 D] LogoutInactivityTimer: 20 which would cause HonorBuddy to logout automatically after 20 minutes. To prevent that, click Settings & Tools and uncheck the Logout for Inactivity checkbox. Good luck with your fishing, Bobby53
It is supported, but I'll take a look at increasing the number of circumstances for its use in an upcoming release -Bobby53
HB3062F31, Thanks for the post. Unfortunately I think you meant to attach a different logfile, as neither the LOGMARK or the timestamp referenced in your post appears. I will run a subtlety in some BGs and see what I can determine, but if you have a chance to submit the logfile you described that would be very helpful. Thanks and good luck with your Rogue, Bobby53
Ruinit, I am actually looking at this already for another quest. It is supported but only when running a Healer Specialization and a group member has the Tank role. If that is the case, then the easiest way is to set the Focus to Wrathion and it will be included in the heal target list. I will be adding support for healing companions while solo in an upcoming release (not the next one posted, but likely the one after.) Thanks for the post and good luck with your quest line, Bobby53
tumbum, Thanks for the diagnostic log. I am assuming you are referring to the following sequence: Code: [06:14:46.847 N] (Singular) YourCurrentTarget: changed to: Overstuffed Golem.5FBA h=100.0%, maxh=4811, d=11.6 yds, box=3.9, trivial=False, player=N, attackable=Y, neutral=N, hostile=Y, entry=45851, faction=21, loss=N, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Kill, TargetIndex=1[06:14:47.168 N] (Singular) YourCurrentTarget: changed to: Plagued Swine.1276 h=100.0%, maxh=3432, d=28.4 yds, box=1.0, trivial=False, player=N, attackable=Y, neutral=Y, hostile=N, entry=16117, faction=7, loss=Y, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N [COLOR=#0000ff][06:14:47.330 N] [Singular] Switching to BotPoi: Overstuffed Golem.5FBA! [/COLOR][06:14:47.332 N] (Singular) MoveToLoss: moving to LoSS of Overstuffed Golem.5FBA @ 8.0 yds [06:14:47.462 N] (Singular) YourCurrentTarget: changed to: Overstuffed Golem.5FBA h=100.0%, maxh=4811, d=7.2 yds, box=3.9, trivial=False, player=N, attackable=Y, neutral=N, hostile=Y, entry=45851, faction=21, loss=N, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Kill, TargetIndex=1 [COLOR=#ff0000][06:14:47.781 N] (Singular) YourCurrentTarget: changed to: Plagued Swine.1276 h=100.0%, maxh=3432, d=32.8 yds, box=1.0, trivial=False, player=N, attackable=Y, neutral=Y, hostile=N, entry=16117, faction=7, loss=Y, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N[/COLOR] [06:14:47.943 N] (Singular) .... h=95.9%/m=99.8%, form:Moonkin, eclps=Solar, towards=Lunar, eclps#=100, mushcnt=0, th=100.0%/tm=100.0%, dist=33.8, face=False, loss=True, sfire=0, mfire=0 [COLOR=#0000ff][06:14:47.974 N] [Singular] Switching to BotPoi: Overstuffed Golem.5FBA![/COLOR] [06:14:47.976 N] (Singular) MoveToLoss: moving to LoSS of Overstuffed Golem.5FBA @ 6.1 yds [06:14:48.105 N] (Singular) YourCurrentTarget: changed to: Overstuffed Golem.5FBA h=100.0%, maxh=4811, d=6.1 yds, box=3.9, trivial=False, player=N, attackable=Y, neutral=N, hostile=Y, entry=45851, faction=21, loss=N, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Kill, TargetIndex=1 [COLOR=#ff0000][06:14:48.426 N] (Singular) YourCurrentTarget: changed to: Plagued Swine.1276 h=100.0%, maxh=3432, d=33.8 yds, box=1.0, trivial=False, player=N, attackable=Y, neutral=Y, hostile=N, entry=16117, faction=7, loss=Y, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N[/COLOR] If a BotPoi of PoiType.Kill is set, that is the Questing BotBases way of saying whatever else happens, kill this mob so Singular will set that as the current target (marked in blue). However, some other component is changing the current target (marked in red). I am not sure if it is the CollectThings quest behavior or one of the plugins you are running. Although Singular is reporting via a "YourCurrentTarget: changed to ..." message, it is informational only. So what is happening is Singular recognizes that the current target is not the PoiType.Kill, so it switches it. Another component then switches it back to the other target. The cycle then repeats itself. My recommendation is to disable all plugins and repeat this part of the profile. If it is still switching targets, the issue is the quest behavior. Thanks for the post and good luck with your questing, Bobby53
I tried setting him as the focus but it still fails to see his health drop. I am running resto druid so the object is to keep him alive but it's won't heal him, it sees him as a pet I think. Tried everything I can think of I am willing to test anything you want ... hehe To elaborate singular is trying to kill him, [Singular] Casting Wrath on Wrathion.E71E @ 61.5% at 20.2 yds
Ok, new Logfile. No WoW Addons, all disabled just Cava Plugin + shipped HB Plugins still the same, toon runs crazy around and switching Target very very fast. If its the QB who will help?
Ruinit, Thanks, but I will only be able to address the healing issue based on the info given. If it is targeting the mob, I'll need a log file of the incident created with the Log Level = Diagnostic setting in HonorBuddy. -Bobby53
I'll get you a log soon as the we get an HB update now that wow has been patched. Thanks Bobby Actually here's a log
Sorry I don't have a log because I've commented it out on my copy to fix for now, but CreateHolyFireBehavior is creating some pretty insane fps drops when attempting to cast (disc priest, so it's trying to cast Holy Fire), traces show each time it casts Combat takes up 300-400ms. Edit: actually of course I will have logs, they're just giant because of the traces, here's an example: Code: [21:51:20.253 N] (Singular) leave: CombatBuffs, took 13 ms[21:51:20.253 N] (Singular) enter: Combat [21:51:20.264 N] (Singular) ... enter: Combat.CreateDiscCombatNormalCombat.0 [21:51:20.266 N] (Singular) .... [Combat] h=100.0%/m=100.0%, combat=N, evang=0, archa=0, spiritsh=0, borrtim=0, inner=Fire, target=(null) [21:51:20.722 N] [Singular] Casting Holy Fire on Me @ 100.0% [21:51:20.724 N] (Singular) ... leave: Combat.CreateDiscCombatNormalCombat.0, took 459 ms [21:51:20.724 N] (Singular) leave: Combat, took 470 ms [21:51:20.725 N] (Singular) [WoWRedError] Invalid target [21:51:20.725 N] (Singular) [CombatLog] SPELL_CAST_FAILED Holy Fire#14914 failure: 'Invalid target'
Hey there, Especially when using solo Dungeon profiles or solo levelling as BloodDK (yeah, some people do that ) the bot does not buff Horn of Winter. It's easily fixed by adding Code: Spell.Buff("Horn of Winter", ret => !StyxWoW.Me.HasAura("Horn of Winter")), somewhere in the #region CombatBuffs part of the Blood.cs file in the Death Knight folder. Would love to see it implemented in the next HB update since I have to manually adjust it everytime I update HB. Thank you.
I am having some trouble with my healer staying too far behind so when the tank pulls a boss and the door shuts, my healer is left outside. Max Heal Target Range: 50 Stay near tank: True Stay near Tank Range: 5 Dungeonbuddy follow is set to: 1 With these settings, shouldn't the healer pretty much grouphug the tank at all times?
andy012345, Thanks for the post, but the time mentioned doesn't indicate an FPS drop -- only how long it took to walk and complete the Combat Behavior tree in that case. Those aren't the same thing as it could occur across multiple frames with no impact. For example, a tree could contain a Wait() composite that waits as long as it wants for a condition to occur without dropping any frames. -Bobby53
