23051602, Thanks for the post. When posting regarding an issue or question, you will want to follow the steps in Reporting Bugs in Singular (click here). Sacrificing the demon is due to choosing the Grimoire of Sacrifice talent and affects all Warlock specs. If you do not want the Pet sacrificed, just select a different Level 75 Talent. Thanks for the post and good luck with your Warlock, Bobby53
ArmyDr, Thanks for the post. No, there isn't a way to simply turn Mind Sear off. Singular is designed to use the best possible spell based upon evaluating the configuration, settings, specialization, talents, gear, operational context and combat scenario. It should be casting Mind Sear in AOE scenarios. You can disable AOE Spells which would turn off the use of Mind Sear as well as all other AOE Spells. If you believe there is an issue with the use of Mind Sear in this case, please follow the steps in Reporting Bugs in Singular (click here) and I will research the issue for you and respond. Good luck with your Priest, Bobby53
*new* Singular v4.0.0.4631 available for download! Available for download from Post #1 of this thread. Contains several fixes for issues submitted by members. Code: --- Release 4.0.0.4631 --- General change- Frost Immune: Aquantion #16292 now explicitly added to Frost Immune list fixed - Pet Attack: was being unnecessarily repeated on Pets current target in some cases. *new* - Death Behavior: settings available to control length of time to wait and amount of safe distance (clear of mobs) prior to using Ankh or Soulstone ressurection *new* - Totem Targeting: will now target and destroy totems set by Current Target if NPC. Setting added to Class Config to allow disabling this ability. Will attempt to target totem a maximum of once per 15 seconds. Death Knight fixed - Frost / Unholy - Pull: was casting Outbreak followed by Howling Blast or Icy Touch due to buffs not being visible quickly enough in client. Will now throttle disease application in Pull fixed - All Specs - Dark Succor: the Death Strike performed was inadvertently using too restricted a range for testing if facing Mob. Mage fixed - Frost - Frost Immune Handling: a check for Frost Immunity was missing from a cast of Fire Blast (low priority and only used prior to learning Ice Lance or on Frost Immune mobs) fixed - Frost - Frost Immune Handling: a check for Frost Immunity was missing from a cast of Frostbolt and failing to suppress Warrior change - All Specs - Enemies Flying/Above Ground: added Taunt as highest priority ability used when these targets are at range
Loving the fast updates! Code: [Singular] /use Excess Potion of Accelerated Learning Could that be placed under scroll use, which is disabled by default ? Since they're resource tied and requires farming of rares to use frequently it would be nice if I could choose when to use them. Toggling flask will remove other uses I do want automated. Cheers
tomten2, Yes, I'll move use of those to another setting as the Use Flasks/Crystals/etc setting is intended for items not consumed on use. Will separate the Excess Potion of Accelerated Learning from Scrolls since they aren't random drops. -Bobby53
I have noticed for a while that Singular has problems facing mobs expecially after you disable and reenable the combat behavior. Today I noticed this message for the first time: [Singular] warning: facing disabled and not facing Nerub'ar Webweaver.6399 @ 1.9 yds This happened after a CustomBehavior "UseTransport" which disables and enables the combat behavior. For me this is a pretty big issue, because basically I have to restart the profile after I disable combat behaviors which I do regularly in my raid profiles. Edit: Restarting the profile won't cut it. I have to restart Honorbuddy. Edit 2: There also seems to be an issue when you disable and re-enable combat routine movement. Afterwards facing enemies also seems to be a bit off.
Studio60, Thanks for taking the time to post, unfortunately there is not enough detail present for me to assist you. When posting regarding a suspected issue or question regarding your use of Singular, please follow the steps in Reporting Bugs in Singular (click here). The warning message you mentioned is one I added to Singular to notify the user that the questing profile has disabled Facing by the Combat Routine (in this case Singular.) Without the message, the appearance is simply that facing in Singular is broken rather than that it was programmatically disabled by the botbase/profile/etc. Based on the description it sounds like a bug in the profile or the quest behavior in use. If you would like this looked into further please attach a logfile from a session where the issue occurred with a LOGMARK at the point you feel that facing should have occurred and did not. I will be able to research at that point and assist with identifying which component is responsible and facilitate getting that corrected if possible. Thanks again for the post and good luck with your Singular toon, Bobby53
Speaking of target facing. Would it be possible for singular to still face targets when Targeting = None ? (Optionally with movement = none). Been helping an irl friend lvl his first char and lazy as I am, I have been using singular with enyo and without those off, it will target and dismount any mob in aggro range. (Using chopper to travel us both, it becomes tedious) With targeting off, I have to babysit bit too much. Would there be any harm in still facing targets or perhaps an additional setting to still allow facing ? Optionally if singular paused while on mount ? (I like this the most tbh but can see why its problematic.) Or I'm I being a lazy cunt here for not setting a pause hotkey ? :x
Try using Combat Bot instead. Singular intentionally does not recognize Combat Bot as a manual assist botbase so that Singular will still perform movement when the Allow Movement = Auto setting is in effect. The intention was to allow you to leave the Singular setting alone, and simply switch between LazyRaider (for no movement) and CombatBot (no movement while out of combat, but Singular movement in combat enabled.) For questing and other things which don't have a lot of dangerous ground effects or positioning requirements, it represents a good trade-off between manual assist moving while not fighting while leaving fights fully automated. -Bobby53 Edit: you can also change the Singular setting Allow Movement to All, which will not detect the botbase and leave Singular movement enabled with LazyRaider, RaidBot, and other manual assist botbases as well. I prefer to switch botbases than changing a Singular setting that I will have to go and reset for use in other contexts, but to each his own.
Hi, HyperMonkey, Since not everyone's garrison is laid out the same, can you go to your map table, and take a screenshot of how your Garrison is laid out, please? Also, in this log, can you point us to a timestamp that the stall happened? cheers, chinajade
Just a quick one to ask for support of the spell 'Flap' (s:164862) for balance druids via 'Glyph of the Flapping Owl' with perhaps copypasta of logic as you have for mages slowfall which works very well And thanks for all the effort you put into making this such a good CC
Already present. If not working as expected, please follow steps in Reporting Bugs in Singular (click here). Thanks for the post, Bobby53 Edit: typo present in the glyph name, so was not recognizing it when equipped. Also noticed that Levitate was missing for Priests when falling. Fixed in next release
Not sure if this is an issue with Honorbuddy itself, or an issue with singular; but noticed on combat bot - it's no longer using either blessing of might/kings (for my prot pally) no matter if you specifically set one to use, or tell the bot to use auto decision to cast. In both instances, I have made the changes, and then completely closed out of the bot and restarted it to see if there's any change. Also completely deleted the settings folder to make sure it wasn't a corrupt file. Using the latest honor buddy (version 783) and singular 4631. I will post this under the honor buddy release thread as well just in case!
leehun03, Thanks for the post! You will need to follow the steps in Reporting Bugs in Singular (click here) if you are encountering a problem or question regarding Singular. Thanks for the post, -Bobby53
GK2014, Thanks for taking the time to post with a logfile. This appears to be a bug introduced with an optimization made in Singular 4.0.0.4524 for finding group members when buffing and arbitrating between mutually exclusive buffs offered. The impact is that no Blessing is cast when Solo and will affect all Paladins. Fixed in next release. Thanks again for post and good luck with your Paladin, -Bobby53
Tks much for the fast response Bobby - happy to help out! It appears that some of the classes will not buff themselves if solo; but if they're in a group - they'll buff the group just fine (monk, mage and paladin do not buff solo; monk buffs fine if in a group). Unfortunately short of testing each and every class, all I can recommend is to check and see which classes are actually affected by the bug.
