You can't really decide anymore, Windwalker has fist weapons and Brewmaster uses 2h staff. If you mean without artifact, i don't know but don't think it's that important while leveling. I'd personally suggest dual wield as Windwalker.
It may be due to the talents you have selected. The log isn't showing your talents properly for whatever reason - can you show me which talents you have selected so I can replicate this on a tester?
I can look into this, but ideally it would be something that could be handled on a profile. With a profile, traditional mounting can easily be disabled and Ghost Wolf can be replaced in place of it.
I've fixed the misspelling of the two abilities in the latest update. Thanks for bringing this to my attention!
I believe the standard pull distance is 40. Used to, you could modify this in your Settings & Tools menu - but this was removed. Now, it's mostly up to the botbase or the profile you're using to adjust the pull distance so there's not a setting in Singular (I don't believe.)
When/if I get time. If there's an issue that you have with them, report it and I can fix it quicker than it would take for me to manually get a tester out to it and test for issues.
Shadowflame is a talent. Green - Supported. Tested. Optimal rotation. May not use some talents. I'll add adding this ability to the feature request page.
Some notes for you: 1) In the Wake of Ashes ret, you're checking unit count first. For better performance, it's better to check user settings first - that way if any of them are set to false, the bot won't bother calling the object manager to scan for units. It's a waste of performance to run unit checks on every pulse if there's no reason to. 2) Unit.UnfriendlyUnits(range) is checking any unit around us. Wake of Ashes if a frontal attack, so it would be better to use: Clusters.GetConeClusterCount(90f, Unit.UnfriendlyUnits(12), 100f) >= 1 Hope those tips help, Thanks for contributing to the community!
It shouldn't be pulling everything with this logic set as this checks specifically for units that are aggro'd with your player or units that are tagged by your player. This issue was originally occurring due to this specific logic not being used - and it was assumed fixed in (HB-3046) I'll mark this down to be tested and re-checked. If it's not working with this new logic, then there's some underlying issue going on that needs to be weeded out.
Thanks for the tips! of course they help. Gonna get to that soon. Question if you don't mind... some spells are restricted to WoWContext.Normal (eg. Hammer of Justice and buff Blessings) wich is preventing the bot from casting them in BGs. I changed that to WoWContext.All and seems it fixed the problem for BGs... but can this cause problems in "other" Contexts? Edit: Sorry if this is noob question but I just can't sleep untill I know this... what do the 90f and 100f mean in the example you gave me. Where do you get them from!? Thanks!
Hello, I have question. While Using Enyo's RaidBot in 110 Heroic Dungeon as BM Hunter, i saw 2 problems : 1. Its keep buffing and unbuffing " Volley " spell, from what i've saw it seems like everytimes a monster die/join ( Well, everytimes the total count of active enemies change ) its activate and unactivate the spell. 2. On Multi Target it does not use multishot in place of single dps rotation cobra shot. Do you need logs? If yes, What exactly? I stop the bot and start it again in a new and fresh heroic? Thanks from advance. (N.B : It work fine anyway in single target, i'm more than pleased. )
