Actualy I found mistake. My Settings file was set to different folder not to rute folder and I was triggering who knows what version of Singular
Druid - Feral - lvl80 Questbot Toon stays directly behind a Elemental but dont attack. Spams endless the Routine but tell all the Time "out of range" but its just 5 yard away. Log starts at: [18:06:04.298 D] (Singular) [WoWRedError] Out of range. till end of Log where i stopped it.
tumbum, Glad you were running a Feral as it has most of the status values needed for this already present in its diagnostic output. The problem appears to be due to an issue with the return from HonorBuddy's .IsWithinMeleeRange API. It is saying that the target is within melee range, while the Pounce spell which requires melee range is failing due to being too far away. The log entries: Code: [FONT=courier new][18:06:05.075 N] (Singular) <<Pull>> h=100.0%/e=100.0%/m=100.0%, shape=Cat, prowl=Y, savage=0, tfury=0, brsrk=0, predswf=0, omen=0, pts=0, th=100.0%, dist=5.8, [B][COLOR=#ff0000]inmelee=Y[/COLOR][/B], face=Y, loss=Y, dead=-1 secs, rake=0, rip=0, thrash=0[/FONT][FONT=courier new][18:06:05.077 N] [Singular] Casting Pounce on Frozen Earth.1A4E @ 100.0% at 5.8 yds[/FONT] [FONT=courier new][18:06:05.336 N] (Singular) reset target timer to 00:00:20[/FONT] [FONT=courier new][18:06:05.339 N] [Singular] Casting Pounce on Frozen Earth.1A4E @ 100.0% at 5.8 yds [/FONT] [FONT=courier new][18:06:05.343 N] (Singular) [CombatLog] SPELL_CAST_FAILED Pounce#9005 failure: 'Out of range'[/FONT] shows the target reported as being within Melee range, but the Pounce cast still failing due to being out of range. I'll revise the Singular logic which decides when to stop moving when moving to melee range which will decrease the likelihood of this occurring -- in next release. For a complete fix, it will require the .IsWithinMeleeRange to return an accurate value. I'll report to HB Team, but otherwise out of my control. -Bobby53
Log : View attachment 3832 2013-11-10 20.11.txt Anyone else experiencing issues on a shammy? seems the pull distance is set to far away, as my shammy stops to attack a mob outside casting range, and just spams "casting lightning bolt" (however its not casting as wow is stating that you are to far away) Just wanted to see if that's specific to myself or others have seen it? Code: (Singular) YourCurrentTarget: changed to: (null) Moving to Type: Hotspot, Loc: <-9194.271, -1127.831, 70.45897> Activity: Setting Rogue Wizard at 82 yards as your target (Singular) YourCurrentTarget: changed to: Rogue Wizard.4C0C h=100.0%, maxh=317, d=78.9 yds, box=1.5, trivial=True, player=N, attackable=Y, neutral=N, hostile=Y, entry=474, faction=17, loss=Y, facing=Y, blacklist=N, combat=N, TargetIndex=1 Changed POI to: Type: Kill, Name: Rogue Wizard Activity: Moving towards Rogue Wizard (Singular) reset target timer to 00:00:20 (Singular) <<< PULL >>> CurrentTarget now: Rogue Wizard.4C0C h=100.0%, maxh=317, d=45.0 yds, box=1.5, player=N, hostil=Y, faction=17, loss=Y, face=Y, agro=N, IsBotPoi=Kill, TargetIndex=1 (Singular) MoveToUnit[Moved]: moving within 40.0 yds of Rogue Wizard.4C0C @ 42.0 yds (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 45.0 yds, th=100.0%, tmelee=False, tloss=True (Singular) MoveToUnit[Moved]: moving within 40.0 yds of Rogue Wizard.4C0C @ 41.5 yds (Singular) MoveToUnit[Moved]: moving within 40.0 yds of Rogue Wizard.4C0C @ 41.1 yds (Singular) MoveToUnit[Moved]: moving within 40.0 yds of Rogue Wizard.4C0C @ 40.6 yds (Singular) MoveToUnit[Moved]: moving within 40.0 yds of Rogue Wizard.4C0C @ 40.1 yds (Singular) StopMoving: RangeOfUnit, within 36.0 yds of Rogue Wizard.4C0C @ 38.6 yds, method: Styx.TreeSharp.Action.RunAction (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 38.5 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 36.2 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 37.0 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 36.2 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 35.9 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 35.4 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 35.6 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 35.8 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 37.0 yds, th=100.0%, tmelee=False, tloss=True (Singular) .... h=100.0%/m=100.0%, maelstrom=0, target=Rogue Wizard.4C0C @ 36.4 yds, th=100.0%, tmelee=False, tloss=True [Singular] Pull Target Rogue Wizard.4C0C out of range/line of sight for 20.0 seconds, blacklisting for 00:05:00 and clearing BotPoi Blacklisting F13001DA00334C0C for 00:05:00 [Type: Pull] - Reason : No reason specified. Caller: at Singular.SingularRoutine.<>c__DisplayClass37.<CreateLogTargetChanges>b__36(Object r) in f:\G2PLAY.704\Routines\Singular\SingularRoutine.Behaviors.cs:line 507 Cleared POI - Reason Clearing Blacklisted BotPoi Cleared POI
Well done on your work Bobby. I was watching a rogue level the other day via questing and the way it gouged, blinded and sapped when confronted with multiple mobs was a delight to watch.
Shtwht?, Thanks for the log file with debug information. Unfortunately the example you pasted into your post didnt match any occurrance within the log file. If you encounter further issues, please follow the steps in the Reporting Bugs [click here] post that I link frequently in this thread. It provides steps on adding a LOGMARK to the log file to conclusively identify the point the issue occurred without pasting a wall-of-text. Pull Distance controls when the BotBase calls Singular to perform a Pull. Said differently, Singular doesn't care what the pull distance is. In this case, a review of the code showed some conditional move/stop logic for Enhancement Shaman prior to Level 20 was in error and causing the problem. Look for a fix in the next release. This issue is specific to Enhancement Shaman prior to Level 20. Thanks again for the post and good luck with your Shaman, Bobby53
Blinkpoolz2, Thank you for taking the time for feedback! Greatly appreciate it and good luck with your Rogue, Bobby53
*new* Singular v3.0.0.3187 available for download!!! Change History for this release appears below. Complete Change History as always is included in the .ZIP See the Reporting Bugs [CLICK HERE] post for details on how to request assistance, post about a problem, or ask questions about the behavior of your botting session with Singular. Still receiving too many bug/question posts regarding behavior users watched that don't contain a complete log file and point of reference to when a single event happened. So, no multi-color bright lights this time. Just a simple request to provide the detail. Don't forget to use the LOGMARK! button. It is located on the Class Config window and will place a mark in the log file making it easy for you to indicate when something happened that you have a question about or problem with. This button provides the same behavior as the LOGMARK plugin. Having a problem while running Singular that you want to report? Click the LOGMARK button immediately when you notice. A line will be added to the log file at that time and now you have a very accurate way to let me know when the problem occurred. Ok, now that's out of the way: - Download the latest version of Singular.ZIP from Post #1 in this thread - .ZIP in Singular thread will always be the current version - HonorBuddy will contain an older version until a new release of HB posts Any post must include a debug log file (a file created with Debug Logging set to true.) To do this, click Class Config and set the Debug Logging option to 'true' then run until you create the issue again. The resulting log file will contain more info than a standard log file which will be essential in understanding the decisions being made by Singular which you weren't expecting. As always, the prior version is still available for download. If you encounter a problem due to the new release of Singular you can always downgrade as needed. Worth mentioning one more time due to the large number of posts without log files that are received, but you must attach a complete debug log with any post. Please see the link at the top of this post for details.
Singular has issues with The Direglob, basically not attacking it. The Direglob - NPC - World of Warcraft Seen issues with this mob on several characters, should be looked at... I set the log to diagnostics half way through so it does log during the attack. Thank you.
Rogue - lvl8 Toon is near a Mob. Got this Mob to attack in Target, but spams this endless. Log starts at: [12:30:46.465 D]
From 1 to 10 the Hunter will attempt to use and spam Last Stand, problem is that you need to be over level 10 to be able to set talents which gives you the option of pet talents and that gives you Last Stand... I'm guessing that there just needs to be a level check requirement when using Last Stand and I'll assume that there's no StyxWoW.Me.Level check.
(Singular) warning: 40 seconds since Questing BotBase last called Singular Which Bot? (Grind, Quest, Archaeology Buddy, BGBuddy, etc) Quest Character Information (Class, Level, Race, Spec) Warlock, 39 ,Worgen , Destruction What profile were you using? (if applicable. Please provide a link, or an attachment for the profile) File Below Date the bug occured (please be as specific as possible, eg; Weds, 12th of October, at 5:36 AM EST) Last 2248 2013-11-13 12.17 Please explain, in as much detail as possible, what the bug is. After the update I started the bot and he just stood there. He will use the basic spells or self-casts but then stands there then, if hes at the flight master he will check the map then close it. I have used other cc's and they work and I do not get this error. But. They suck lol this cc works really well. I had though this was an HB problem but once I switch out CC's the problem goes away. Please explain any steps to reproduce this bug. If the bug is not reproducible, we may not be able to fix it. I have, reinstalled HB once by exe and once by download and placement. I have deleted all add-ons in game as well as reinstalled wow its self. I have updated singular and re-downloaded all profiles used. In short I have reinstalled everything at least once. Same issue each time. I have also turned my anti virus off before installing the program as well as when I ran it. Please list all plugins currently enabled (as well as links to any plugins not packaged with HB by default) Never used any add on other than what is turned on by default. ItemForAura QuestHelper, and anti drown. Which Custom Class are you using? Please include the version, and link if applicable. Singular http://www.thebuddyforum.com/attachm...-3187.zip.html. Please attach a log for this bug report. File Below I have posted this under HB problems but no one has replied. http://www.thebuddyforum.com/honorbuddy-forum/70565-bug-reports-honorbuddy-bug-reports-7.html
So after 2 hours of playing my log is 6MB weight a lot of error for Rouge Subtely while lvling. With a lot of :
retcyn, Thanks for the post. The thread you mentioned as already having posted in appears to be a place users can post regarding bugs. It doesn't seem there is any follow up in it unless additional info to understand the issue is needed. Not quite sure of the purpose of that thread, but your best bet is typically to post in the HonorBuddy Support subforum. As for the issue cited in your title, this message doesn't indicate a Singular bug -- (Singular) warning: [##] seconds since [aaaaaaaa] botbase called Singular, that is a message issued by Singular letting you know it isn't being called. If Singular didn't do this, then there would be nothing happening without any clues as to why. It is the botbases job to repeatedly call the Combat Routine. If calls aren't occurring then Singular cannot evaluate whether the character needs to Rest, needs Healing, or needs to Buff. It is also the BotBase that decides when to enter Combat, which it does by calling Singular when it either wants to pick a fight or finish one already in progress. The Combat Routine doesn't really have a say in those decisions, it's basically a servant that does what it is told and as you found out, does nothing when it isn't told anything. Ultimately the issue is due to the specific quest you were on and the quest profile/quest behavior not being updated to support it. The update I am referring to are some design changes that were made in the Questing botbase regarding how a profile controls what behaviors the Questing botbase is allowed to use. Look for a response in your original thread, as this isn't a Singular issue. Thanks for the post and good luck with your toon, Bobby53
Singular vs Questbot in Hyjal So the questbot want to go in other direction and the singular want to go in other direction its looks like schizophrenia.
Hello! For Feral Druid it's possible to set when more than 3 mobs in melee range to do (Thrash,Swipe) AOE skill for the first skills instead of single attack rotation (weakened armor,rake)? Also if there is a way to disable completely the weakened armor skill it will be greatfull.
kasia, Please see my Standard Response to Posts with Insufficient Information [CLICK HERE]. The log file provided shows contention between the BotBase and the Combat Routine while moving. Note: the Combat Routine is a tool used by the BotBase to kill things. If it wants them killed, it calls it. If it wants to move somewhere without interference, it doesn't call it. The problem here is that the BotBase is trying to move to a point -AND- calls the Combat Routine (Singular in this case) to move to a target and kill something. Here is a sampel from your log: Code: [07:58:42.214 D] [QDBG] Starting behavior [ForcedQuestObjective Objective: [GrindObjective MobID: 40229, Count: 8]].[07:58:42.224 D] Goal: Goal: Kill Scalding Rock Elemental x 8 [07:58:42.292 D] Activity: Loading Tiles [07:58:42.292 D] Loading Kalimdor_38_22 [07:58:42.756 D] Changed POI to: Type: Hotspot, Loc: <5557.667, -3752, 1583.852> [07:58:42.922 N] [Singular] attention: Pull Distance set to 100 yds by Questing, Plug-in, Profile, or User [07:58:43.052 N] [Singular] Current target invalid. Switching to TargetList mob Scalding Rock Elemental.ACF0! [07:58:43.053 D] (Singular) EnsureTarget: set target to chosen target Scalding Rock Elemental.ACF0 [07:58:43.646 D] Changed POI to: Type: Loot, Name: Scalding Rock Elemental [07:58:43.950 N] Moving to Type: Loot, Name: Scalding Rock Elemental [07:58:44.222 D] (Singular) MoveToMelee(PathGenerated): towards Scalding Rock Elemental.ACF0 @ 8.3 yds [07:58:44.291 D] (Singular) MoveToMelee(Moved): towards Scalding Rock Elemental.ACF0 @ 8.3 yds [07:58:44.346 N] Moving to Type: Loot, Name: Scalding Rock Elemental [07:58:44.624 D] (Singular) MoveToMelee(PathGenerated): towards Scalding Rock Elemental.ACF0 @ 5.8 yds [07:58:44.669 D] (Singular) MoveToMelee(Moved): towards Scalding Rock Elemental.ACF0 @ 5.8 yds This is not a Combat Routine issue. It is a Quest Profile or Quest Behavior issue. Please post in the HonorBuddy Support thread referencing this post. -Bobby53
FadeToGrey: Thanks for the post. Feral Druids do have AOE support. If you find that it isn't being used, please be sure to follow the steps in Reporting Bugs [CLICK HERE] when you have a question to ask or bug to report. There is not a way to disable use of Weakened Armor debuff. If there is a reason you would like to do that, I'll need a detailed explanation and specific example demonstrating why that would be necessary. Thanks for the post, Bobby53
I checked again deeper and found the CR good enough. Those that would like to change now. 1.Thrash skill should to be activate as the first skill in AOE rotation when more than 3 mobs in melee range. (atm is setted to 5+) so change the set start AOE count to 3 (with weakened armor disabled) 2.Weakened armor skill is not always needed. (the best is to have a setting in the UI for true/false or just disable it in AOE rotation) What Class+Spec are you?: Druid Feral What 'context' is the bot in? (Instance, BG, Normal): Solo Instance Grim Batol gold farm What level are you?: 90 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? What happened (be specific)? Did you attach a complete debug log? (choose one: YES or YES)
