I believe there's an issue within the CastOnGround logics. I've seen this happening on other classes as well - but more rarely. It seems to be the worst for Elemental Shamans for whatever reason.
I was noticing this on my testers as well. After peeking at the Singular logic - it should be casting it under stressful situations. eg: Three mobs attacking us - or there's an elite - etc. The code it self looked fine, so I'll need to field test this a bit more. Once I can debug it a bit I'll make fixes. Thanks for the report!
The multi-shot issue should be fixed. For bestial wrath, the bot should be using it if: "Your current focus is greater than 90 and Kill Command is off cooldown or less than 3seconds from cooldown." It's setup this way to maximize the potential of the Bestial Wrath buff. If in common questing context the Bestial Wrath isn't being cast because the requirements are too strict, I can add new settings in that will make it more lenient.
EchoTiger's version? Hmh. I'll work in better AoE functions for Feral Druids for the next coming update.
I can add in a user-setting that'll let you pick a minimum for buffs. It'll be live in the next update.
For some reason, the melee composites for getting in range with mobs overrides the facing with a 180degree tolerance. I'm not sure why this override would be set as the default facing is 70degrees - and that's perfectly fine. I'll need to discuss this with Raphus to see if there's any reason why the 180degree override is set as it makes no sense to me at all.
Hmm, very interesting. There was a similar issue with the Heirloom items "Use:" composites where it would spam using the Heirloom, but the Heirloom would never get "used." This primarily happened with the necklace heirloom that heals you when you use it. I'll look into this one. It's probably an issue with the use item logic.
you complicate things, you just need to make a row of spells and the conditions of their use, in different game modes
Isn't that what Singular is? and any routine for that matter... Can you give a working example of what you mean? That can handle rotation, movement and detect context (solo/instance/etc)
Thanks for your efforts EchoTiger. Just wanted to pop in to report that as a Disc Priests it appears to try and buff Power Word: Fortitude when this no longer exists as a spell (it's likely that it probably also does it as Holy, I noticed it in Common.cs for pre-buffing) and also that Disc Priest does not cast Power Word: Solace if it is talented (the code was commented in Discipline.cs and is perhaps old).
cant play wow without singular！ I stopped play the Hunter and created a DH because singular optimized the routine well haha
any way to get the WW monk routine to not use the same ability twice in a row? It's really killing DPS because of mastery and the talent hit combo. It affects tiger palm and blackout kick the most, so maybe its just those two that need work. The biggest problem is the bot casts blackout kick 2+ times in a row, when it should fill the gap in between with tiger palm or something else. I don't know what language singular is in (probably C++?) otherwise I'd implement it myself if it was a language I know / an easy one to hack around in. PS: if you add touch of karma support and fix the above bug I will bake a cake with your username on it.
How to reset the singular setting? I changed the allow User movement in botting to true to control moving by my self in combat bot. but when I changed it back to false, it still not auto move while fight in combat bot mode ,and I can still control the movement. I deleted the hb folder and reinstall it , the singular setting looks like back to default ,but when hb start ,it still says the singular installation had modified in pink color ,and I still cannot auto move when fight in combat bot. Need help
Im having massive problems as a Resto Druid. It wont cast any spells, even though players are under the threshold set in the routine. Is there any configuration need to be set so the routine can see im playing a resto druid/healer?
Mob tagging isn't bugged. Blizzard made it so up to 5 players can attack a single mob at once. As long as the other human players are doing damage to the mob, loot is shared to everyone who assisted killing the mob. This change was made when the Legion prePatch was released.
