Question for everyone--which mage build does Singular work the best on? Frost seems a bit questionable, and before I try out any of the others I wanted to make sure I was picking the one which works best with Singular. Don't get me wrong; it works, but I'd like something that works as well with Singular on the Mage side as, say, Paladins do. Thanks!
Currently using it with Dungeonbuddy on 5 bots, DK,Priest,hunter,rogue,druid. Having zero issues, thanks Bobby.
Hello. Thx for your work. I'm using Grind Bot with Singular routine (disc priest) and i have a question. How can i use Divine Star spell to hit mobs?
Seem to be a problem with rogue (Combat) and the Quest "Cycle of Life" in Dragonblight. Seems to have problems wit the Emerald Skytalons. View attachment 6452 2013-12-04 09.14.txt
Pick Lock doesn't seem to work for low level rogues on junk boxes. I end up wit full bags of junk boxes while leveling my rogue. Is there any way to fix it?
The Bot have problems with targeting if there are many enemys. View attachment 3292 2013-12-06 18.52.txt
i am using the default singular with bgbuddy as a night elf r druid. is there a way you can stop if from casting wrath and healing instead. i can't tell you how many times i have died cus the bot casts wrath instead of healing myself. Thank you. also can you add in an option for resto druid to use cc or something. also can we please get the routine to use lifeblooms or add hte option. can you make an option to use the soul of the forest proc to refresh lifeblooms or clone an enemy using cds or something? symbiosis is set to true for enabline. yet it never casts symbio on anyone to use it? I set the hotkey for movment to true but every key i have set when pressed does not suspend the bot like it says it should. also there is an option for wild mushroom but it never cast shroom ever.
seriously. casting wrath as a healer instead of healing when the bot for whatever reason (which is 6 times out of 10) thinks i should 1v1 is so dumb.
Yes, I agree there are issues with healing sometimes not being given the priority it deserves... Sadly, this problem exists not only in the druid class but other classes as well such as the shaman (I've seen it once before dying on 100% mana).
emmark, My apologies for the delay in responding. Yes, with Targeting Style set to None all targeting by Singular is disabled. I can look at this further, but this is not a Debug Log file: Follow the steps in the Reporting Bugs [CLICK HERE] post and set a LOGMARK at the point where it has switched targets and you believe it should not have. Thanks for the post and good luck with your DK, -Bobby53
Obliv, Thanks for the post and my apologies for the delay in responding. You will want to submit a debug log when encountering an issue (log provided doesn't have the detail to look into this for you.) I did review the code however and saw there was a bug in the cast on self when solo. Thanks for making me aware and look for fix in next release, Bobby53
The botbase has set the BotPOI to: but another component is interfering and changing the current target: Since the component responsible is not writing to the log, the only message appears is Singular's log notifying you that the current target frame in WOW has changed (and not by Singular.) This could be a plug-in or the quest behavior in use, but whatever component is responsible for changing the target to something other than the BotPOI. The behavior in use is CollectThings so not sure if this is an inappropriate use resulting in your issue or the parameters to it require revision. Ultimately, the component which is switching the current target needs to do one of the following: - clear the BotPOI before setting the target - set the BotPOI to the desired target - stop changing targets and use targeting filters Hope that helps, -Bobby53
Singular is a Combat Routine, and Combat Routines are tools used by other components to kill things. If Singular is trying to kill something, it is because the BotBase, Plugin, or QuestBehavior is calling its Pull or Combat behavior. In this case, it shouldn't be since it appears your character is dead. I did notice the following: I don't believe the Feign Death wait interfered, but it is possible. I have added additional logging and a check for death to prevent this in the next release. Please let me know after you run it for while (when its available) if you have the issue again. -Bobby53
Slite62, There is a typo in a log message output call that is causing an exception. This interferes with the normal operation and is causing your issue. This problem can occur for Rogues fighting flying mobs. Issue fixed in next release. Thanks for letting me know, Bobby53
