ash23, Thanks for taking the time to post. To act on your suggestions, I will need the details described in Reporting Bugs (click here). Set Log Level to Diagnostic and use the LOGMARK button in Class Config to add a mark to the Log at the point where you see Singular did not cast but should have. As for multi-dot approach, will need more specifics on the specific combat scenario as Singular has context specific spell priorities and not just one. -Bobby53
But isnt he target an different Mob? [11:29:30.979 N] (Singular) YourCurrentTarget: changed to: Tundra Crawler.42EB h=100.0%, maxh=8982, d=48.9 yds, box=12.0, boss=N, trivial=N, player=N, attackable=Y, neutral=N, hostile=Y, entry=25454, faction=14, loss=Y, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N and after Pickup a new Quest he start [11:29:31.207 N] (Singular) YourCurrentTarget: changed to: Sage Highmesa.004B h=100.0%, maxh=18582, d=4.9 yds, box=4.1, boss=N, trivial=N, player=N, attackable=Y, neutral=Y, hostile=N, entry=25604, faction=1921, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Kill and try to Kill Sage Highmesa. The Hostile says N. And it was triggered from Singular. I cant see any Plugin that triggers this kind of Attack.
I have noticed I'm getting LUA errors running dungeon buddy - raids only - with singular. Don't notice it when using demonic. Anyone else having that issue?
I will attach a log if it happens again bit as for my next quesrion regarding having it pull with a bomb or ice lance in frost spec?
ez101, The errors you are referring to don't appear to be reflected in the log file provided. Please see Reporting Errors [CLICK HERE] and follow the steps for enabling diagnostic output and marking the logfile at the point the error occurs. Thanks for the post and good luck with your Paladin, Bobby53
ash23, Will add a quick pull ability to next release similar to what is in place for Elemental Shaman where it will automatically pull with instants if questing in an area where other players are present and potentially competing for mobs. Will additionally have it pull with Level 75 talent once learned. -Bobby53
Tumbum, I originally read your response on my phone, but in re-reading see I did make a mistake in my earlier reply and additional info is needed. You were correct in that I had copied the wrong current target change notification when showing the Hostile=Y in my earlier reply. My apologies for the misinformation. However, the rest about what I mentioned is correct -- the decision to kill Sage Highmesa was made by the Questing BotBase and is ultimately controlled by the Questing profile used. Singular was just the tool it used to kill it. First, it is important to realize that Singular does not target mobs, the BotBase and other components do. Targeting is the act of identifying what enemies should be considered targets. If there is an obvious problem with attacking the current target, Singular will set the Current Target frame to a different one -- but that new target always comes from the Target List controlled by the BotBase. The statement that Singular triggered the target change to Sage Highmesa is incorrect -- Singular only told you that something changed it, Said differently, in the example the message you copied is a message output by Singular to let you know about an important event. It does not indicate that Singular changed the current target, only that some component did. When Singular actively changes the current target there is a specific message beginning with "[Singular] Switching to" followed by the new current target and why it changed it. It does not change the Current Target without outputting that type of message. You should not see this very frequently during questing as good questing profiles typically do an excellent job of selecting the mobs that are most important to kill and are valid. Here is a scrap from the logfile around the area you mentioned with comments explaining what is happening and who is doing it: Code: [B][I]Questing BotBase detects quest is complete, so sets BotPOI to QuestTurnIn[/I][/B] [11:29:28.619 D] Goal: Turning in Quest - A Proper Death : QuestID - 11675 : To - Sage Highmesa : ID - 25604 [11:29:28.619 D] Changed POI to: Type: QuestTurnIn [B][I]Singular detects that the current target was changed, so announces it[/I][/B] [11:29:28.766 N] (Singular) YourCurrentTarget: changed to: Sage Highmesa.004B h=100.0%, maxh=18582, d=4.9 yds, box=4.1, boss=N, trivial=N, player=N, attackable=Y, neutral=Y, hostile=N, entry=25604, faction=1921, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N [B][I]The following InteractDebug indicate the actual turnin attempt at this point[/I][/B] [11:29:28.833 D] InteractDebug:995294044 [11:29:28.833 D] Interact Done:995294044 [11:29:30.493 N] Tried to complete quest 5 times with no success [11:29:30.493 N] Closing Questframe [11:29:30.901 D] [QDBG] Done with forced behavior [ForcedQuestTurnIn QuestId: 11675, QuestName: A Proper Death]. [B][I]Quest was turned in, so Questing BotBase clears the BotPOI[/I][/B] [11:29:30.901 D] Clearing POI - Reason Quest turn in completed. [B][I]Questing BotBase now selects Sage Highmesa to Kill it. Decision not made by Singular[/I][/B] [COLOR=#ff0000][11:29:30.907 D] Changed POI to: Type: [B]Kill[/B], Name: [B]Sage Highmesa [/B][/COLOR] .... lines removed for brevity .... [B][I]Singular detects Questing BotBase has changed the Current Target so notify the user[/I][/B] [11:29:31.207 N] (Singular) YourCurrentTarget: changed to: Sage Highmesa.004B h=100.0%, maxh=18582, d=4.9 yds, box=4.1, boss=N, trivial=N, player=N, attackable=Y, neutral=Y, hostile=N, entry=25604, faction=1921, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Kill [B][I]Questing BotBase calls Pull Behavior instructing Singular to Kill targeted mob[/I][/B] [11:29:31.274 N] [COLOR=#ff0000](Singular) <<< PULL >>>[/COLOR] CurrentTarget now: Sage Highmesa.004B h=100.0%, maxh=18582, d=4.9 yds, box=4.1, player=N, hostile=N, faction=1921, loss=Y, face=Y, agro=N, IsBotPoi=Kill The most important line above is at 11:29:30.907 indicating that Questing BotBase set Sage Highmesa as the Kill BotPOI. I can't tell you why it was selected since that decision was made by something other than Singular. Hope that helps. I'm afraid I won't be able to help further in diagnosing why the Questing BotBase with the Questing Profile in use decided to attack a neutral mob that was not hostile, but please feel free to ask additional questions. You may also want to reach out to chinajade for details on this. I have reattached your .zip with the log since it was deleted when the message was archived. -Bobby53
Bobby, question. Is it Singular or Kick's profiles that the bot does not defend himself on PvP realms? I keep dieing while questing on PvP realms, because the bot does not defend against players. It's very obvious that way that I am a bot. I've levelled numerous toons now (Horde PvP mostly) with Kick's and Cava's and while using Singular (on all of them) I keep getting killed by players, while just taking the beating...
Soeski, In the cases I have witnessed it was due to being attacked at a point where Singular is not being called. This was due to the Questing Profile having either disabled the Combat Routine or invoking a Quest Behavior that was not calling the Combat Routine. I am sure you kow, but to explain for others reading this -- Singular is a Combat Routine. In the HonorBuddy framework, a Combat Routine can only function when it is called by the BotBase, Plugin, or Quest Behavior. In some cases, the tasks those components are trying to carryout need to avoid entering into Combat, so they will disable the Combat Routine and prevent it from attacking even when being attacked. The details of what you mentioned are a little vague though. There have been a couple recent changes to targeting in Singular dealing with the BotPoi that may have a side effect I haven't seen which you encountered. If the situation you were referring to is that it stayed focused on the BotPoi rather than turning to attack the player, that is possible although I haven't seen it. To check what is happening in a scenario you observe, I would need a diagnostic log file with a LOGMARK in it near the point the issue occurred. See the Reporting Bugs [click here] for steps. A diagnostic log would include the details regarding what is going on for me to say specifically and if an issue with Singular exists and identify it. My recommendation is to always quest with Log Level => Diagnostic. Unlike when Raiding, there isn't the performance penalty associated with diagnostic logging. There is one issue I know of due to Singular where the character is not fighting back (fixed in next release.) This happens when your Singular toon is standing on top of the target (and I mean literally at a distance of 0.00) The problem is that at that distance the IsFacing API always returns false, but the .Face API can't fix because it isn't actually a facing problem. All occurrences of this I have seen were with melee characters attacking NPCs, so not specific to PVE or PVP realms, but with the movement that usually occurs in melee encounters with an NPC. I haven't seen this happen when fighting a player. As mentioned, this issue is fixed in the next release. I have added a slight randomly chosen strafe to move slightly off the target and allow the facing logic to complete. If you can post the info needed I'll be happy to look into that further. Thanks for the post and good luck with your Toon, Bobby53
Quest Botbase Feral Druid - lvl85 Zone: Twilight Highlands Quest: How to Maim your Dragon Toon drop down the Item to call the Dragon. Toon fight with the Dragon till its Green and Friendly. Normaly now my Toon has to Jump up the Dragon. Singular still try to kill the Friendly Target and Dragon despawn. [HR][/HR] [10:35:42.414 D] Changed POI to: Type: Kill, Name: Baited Black Drake botbase says kill this singular recon and switched to kill [10:35:42.830 N] [Singular] Switching to BotPoi: Baited Black Drake.8782! later mob is friend [10:35:53.739 N] (Singular) [CombatLog] SPELL_CAST_FAILED Mangle#33876 failure: 'Invalid target' but singular still want combat it [HR][/HR] Attached just this Quest as Profile so you can take a look into the Script.
Tumbum, Thank you for the post and details. As I described previously, Singular attempts to kill what the BotBase tells it to. It continues to try to kill them as long as the BotBase allows it to. In this case, the Questing BotBase (as directed by the Questing profile in use) set the Baited Black Drake as the BotPoi to Kill: Code: [10:35:42.414 D] Changed POI to: Type: Kill, Name: Baited Black Drake Ultimately, it is the BotBase which decides how long to fight. There are existing Quest Behaviors that handle the case of allowing the Combat Routine to fight to a certain health level then discontinues combat to perform some other action. The quest profile you are using should be revised to employ that type of quest behavior for the completion of this quest. However, in past versions, Singular would have stopped fighting when the NPC turned friendly. A recent change in the BotPoi validation was made to address this issue you had submitted: http://www.thebuddyforum.com/archives/124589-hb-archives-singular-do-not-delete-60.html#post1445055 Am revising that change so that it now performs all target validations on the BotPoi except the Critter check when the mob is a PoiType.Kill. That should allow targeting the Frogs and discontinuing combat with the dragon when it turns friendly. This will be in the next release. Thanks for the post and good luck with your questing, Bobby53
Hello bobby, its been a while Destruction warlock has some issues with capping embers and staying capped, even on single target. Think it needs some overrides 1. Stop casting conflagrate if capped on embers (bot correctly wont cast CB with 3> stacks backdraft but that currently only prolongs the problem) 2. Once capped, nothing should have higher priority than casting chaos bolt. * I've seen it dump embers occasionally, what are the current triggers for it ? * Would it also be possible to have singular react to procs ? Even if its something crude as "trinketproc" or w/e you can check for and then forcing chaosbolt to be the next action until 2+ seconds left on buff. ? If not, is it possible to manually add checks for spellid's ? Would like it to react to following procs: 148906 146046 Those things combined will lead to HUGE dps increases. Thanks
tomten, Thank for the post, but there isn't enough detail provided for me to look into the Ember issues (capped/dumping.) Singular Destruction Warlock implements multiple spell priorities with a config setting to select. Happy to look at those further, just shoot me a diagnostic log and set a LOGMARK at the point the issue occurs as described in Reporting Bugs (click here). As for trinket procs, I'll add so that spell priority changes when proc detected, just provide specifics on any changes beyond casting a Chaos Bolt if available. -Bobby53
Jaladhjin, Thanks for the post. Would be glad to push those options out in next release. They would be on the Group Healing tab. New release of Singular will be sometime next week. Thanks again and good luck with your Druid, Bobby53
I really like the singular fire mage routine... but when you enable the kite feature it will frost nova the target, turn around and run away. is there a way to get it to just blink instead of run?
Hi I didn't provide logs cause i thought it wasn't necessary in this specific case If the code allows it to cast conflagrate when capped on embers, it needs changing. If the code allows it to cast anything else besides chaos bolt/shadowburn when capped, it needs changing. For the procs: * You want to refresh immolate.(I do it with less then 2,3 sec left on proc as i cant fit chaos bolt casttime) * If enough embers to cast chaosbolt or shadowburn, you want todo that and not cast conflagrate and force incinerate casts. * Chaos bolt / Shadowburn should have highest priority and dump as much ember as possible, if less then 2,3 seconds left on procs you want to cast immolate as you wont finish a chaosbolt. (unless under hero/meta gem proc, then CB will be shorter, all this assuming >20% hp.) I'll try todo some logmarks during a run tomorrow but now i need sleep Thanks!
