Thumped, Thanks for passing along. This is a Bot error occurring within its targeting. Immediately after that, there is a memory read error which is something they are aware of. Forwarding along to the HB Devs. Thanks for taking the time to post and good luck with your Druid, Bobby53
Haggy, Thanks for the post. A couple responses regarding this:
Haggy, I encountered an issue with some other work I was doing and in researching it encountered a bug that was likely impacting you (guessing without a log file.) An issue exists with the spell information in HonorBuddy which is causing it always return false to SpellManager.CanCast("Savage Roar") and SpellManager.CanCast("Thrash"). That was not present when testing on the Feral Druid routine was originally done which explains different results. Note however, running on a test dummy without the proper setup for force the use of Instance behaviors will cause you use the Solo (Normal context) behaviors which won't cast Thrash unless you are in combat with multiple training dummies within Thrash range. I'll have a Singular fix release posted in the next couple days which will include a workaround for this issue. Thanks for the post and good luck with your Druid, Bobby53
Not enough info to look into further. Standard Response to Incomplete Forum Posts [CLICK HERE]
It is in the spell priority. Not enough info to look into further. Standard Response to Incomplete Forum Posts [CLICK HERE]
Thanks for the follow up. I posted to you on this above regarding a bug in HonorBuddy (in case you missed it [#779 - CLICK HERE] ). The absence of any successful Savage Roar cast indicates you were being impacted by the bug, as it prevents any automatic cast of that ability at present when checking SpellManager.CanCast() first. -Bobby53Ok I tested it again today. A couple of warsong matches. No Savage Roar. Not a single one.
I have seen other CC having similar issues. If you look into the Druid secution. There is one FeralDruidCC. Not sure what the problem exactly was, but maybe you have a minute to take a quick look.
In the log there are a lot of:
[22:14:23.834 D] [Singular-DEBUG] cast Savage Roar to use 4 points on corpse of Mage since buff has 0 seconds left
Not sure what Mage he is talking about the whole time
Here's the full log:
View attachment 85399
Cheers
Haggy
WileE91, Thanks for the post but you're using an old version apparently. See the Change History for Singular 3.0.0.1967 [CLICK HERE] . It will be easy to find as that was the only 5.2 related change for Hunters in that release. Please also see the Standard Response to Incomplete Forum Posts [CLICK HERE] . Good luck with your Hunter, Bobby53
95] Spell.Cast("Rejuvenation", mov => false, on => Me, ret => _ImaMoonBeast && Me.HasAuraExpired("Rejuvenation", 1)),
//Added Settings & Removed Moonbeast
95] Spell.Cast("Rejuvenation", mov => false, on => Me, ret => /* _ImaMoonBeast && */ Me.HealthPercent < DruidSettings.Rejuvenation && Me.HasAuraExpired("Rejuvenation", 1)),It keeps running and turning , not casting or only casting 1 spell and then turns around to run again.
Sometimes it even aggro's a mob. Spell.Cast( "Typhoon", ret => Clusters.GetClusterCount( Me, Unit.NearbyUnfriendlyUnits, ClusterType.Cone, 8f) >= 1),
- This checks for the Clustercount being above 1, which results true almost always.
- Problem here is the absence of a safe check ( Will i aggro more mobs or not )[COLOR=#333333][FONT=verdana][COLOR=#696969][FONT=courier new][B]What Class+Spec are you?: Balance Druid
What 'context' is the bot in? (Instance, BG, Normal): Normal
What level are you?: 90
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? : Overall.
What happened (be specific)?: Dummy Settings & Unefficient behavior.
[/B][/FONT][/COLOR][/FONT][/COLOR][B][COLOR=#333333][FONT=verdana][B][COLOR=#696969][FONT=courier new]Did you attach a complete debug log? (choose one: YES or YES)Yes I guess.[/FONT][/COLOR][/B][/FONT][/COLOR][/B]Can you release fix for rogue? Cant grind normal everytime bot stuck in combat
Nazaruk, My apologies as I somehow missed this earlier post to you regarding Combat spec. You can easily attach large log files by compressing to .ZIP before attaching as text compresses very well, especially repretitve text.
I have not been able to duplicate the behavior you encountered. I have re-reviewed your previous log posted and the only thing I can see is:
That value determines at what distance you will begin approaching an enemy. While a value of 1 is a problem, I don't believe it is the reason for the problem you have encountered. The only other thing I can see is that you are not using an English WOW client. This shouldn't present a problem either as there is nothing that should be impacted, but none the less represents another difference that exists.
WileE91, Thanks for the post. Any time Singular is updated the version bundled with HonorBuddy becomes obsolete. You won't see it updated until the next HonorBuddy release which is why the .ZIP package of Singular is available to you. Singular being community driven is covered in Post #1 of this thread (same place you download the .ZIP from.) Thanks for the post and good luck with your Hunter, Bobby53
Could you clarify how this is a problem? The cast of Rejuvenation at that point is intentional so the Moonkin is buffed with a HoT in Combat to offset incoming damage rather than waiting until health has dropped to a point you are forced to recover from the damage rather than fight on. The test for Glyph of the Moonbeast is needed as that isn't a cast you want occurring if it will take you out of form. I'll look at this further along with providing settings to control once I understand better understand the negative aspects of how this was impacting your usage.
Kiting is disabled in the attached log file. Please post a log file and a identify a specific occurrence (by time or logmark) that correlates to the behavior you were seeing and I'll look into this further for you.
The current GetClusterCount check referenced is for preventing wasteful casts of Typhoon when there are no mobs within range in the frontal cone. Will add test to suppress cast if non-aggroed neutral mobs or crowd controlled mobs are present in the cone.
Thanks for the considered post and good luck with your Druid, Bobby53
tomten, Thanks for the suggestion! That doesn't seem like it would have helped in this situation. The member wasn't accessing Post #1 for the .ZIP, so it doesn't seem likely they would have encounter Post #4. The complete change history is always present in the .ZIP file downloaded. When I post a notification about a release to forum members, I include a copy of the change notes relevant for that release as a convenience to users already reading the notification. For users that don't read the new release notifications and don't download the .ZIP, it isn't obvious to me how an additional Change History maintained on Post #4 will be of much use. For now I'll add a note to Post #4 on where to find them in case someone were looking for them. Thanks for the post, Bobby53