If I enable "Disable Non Combat Behavior" will this speed up downtime? like my character is never oom and doesn't really need to "Rest"
Heyho! Maybe I am blind, but there used to be an option to set the % when Ice Barrier is castet and if Ice Barrier should be casted before the pull. My Mage runs around and I never see him using it. Where can I set that option?? And another thing. My mage sheeps enemies. Thats ok, but after killing all the others and only the sheep is left, it stands around, waiting untill the mob comes out of sheep. That just looks stupid bottish. Any way to improve that?
Also Singular does not attack critters, even if they are attacking you. Also, when a mob is in combat with your toon, but the mob is not dealing direct damage to you (ej: Rain of Fire), the bot will not autodefend itself.
i know i never upload logfiles bobby but there is one more issue when questing singular avoids killing the target near him he runs to the target that is further away on a distance its looking verry bottish a real player would kil that target that is attacking him and not running to the target that he targeted on a distance and ignoring the closest one
*new* Singular v4.0.0.4419 available for download! New release containing fixes for issues that logfiles were provided for. Additionally some other work in progress that testing has been completed on. See change history for full details Code: --- Release 4.0.0.4419 --- General *new* - Capability Flags for Facing and Movement - Singular behaviors which Face the target and Move towards the target can be disabled by the BotBase, Profile, or other components via Capability Flags. Have added logging to indicate when the character is not facing or not in line of spell sight of the target but the CapabilityFlag for that is set to Dissallow. change- Facing and Line of Sight - revised implementation so attacks and abilities are not cast if not facing and in line of sight of target. Previously it would face and move to line of sight, but also allow attempts at casting abilities on the assumption that at most one would fail. Since this can be selectively disabled by other components but abilities continue to cast, have added additional checks to deal with this in all spell priorities for all Class Specializations, Class Lowbie implementations, etc. fixed - Casting Buffs: will now correctly handle overrides and check for the correct aura name Death Knight fixed - All Specs - fixed issues with applying diseases fixed - All Specs - fixed issues with not recognizing Necrotic Strike as override for Frost Fever and Blood Plague fixed - Blood - AOE spell priority used in Normal, Battleground, and Instance contexts fixed - Blood - recognition of Crimson Scourge procs fixed - Frost/Unholy - Remorseless Winter: Normal context - cast if targeting enemy player within 8 yds fixed - Frost/Unholy - Remorseless Winter: Battleground contexts - cast if within 8 yds of enemy player (casters only) fixed - All Specs - Dark Succor Death Strike: was being cast immediately due to bug in time to death logic regardless of player health or time remaining on buff. Now correctly checks target will die within 6 seconds fixed - All Specs - Soul Reaper: revised kill sniping logic to generate haste buff more frequently Hunter fixed - All Specs - Explosive Shot was still being cast when AOE was disabled fixed - All Specs - Explosive Trap was still being cast when AOE was disabled Monk change- Windwalker - Instances: change to spell priority Shaman fixed - Elemental - Totems: were not being set during Pull fixed - All Specs - Normal Context - Totems: Healing Stream Totem will be set correctly while soloing using the SelfHeal setting in Class Config change- Elemental/Enhancement - Totems: setting totems while in Combat made higher priority change- Elemental/Enhancement - Totems: removed Healing Tide Totem from off-heal settings change- Enhancement - Ghost Wolf in PVP: will use Ghost Wolf more frequently to close distance to ranged target without breaking form with a spell cast. Applies to Battlegrounds and World PVP Warlock *new* - Destruction - Instance priority based on SimulationCraft profile for Level 100 only. Supports Level 100 talents Warrior fixed - Lowbie - checks if AOE spells are allowed prior to casting Thunder Clap. Typically Lowbie's are Level 9 or lower, so this is a very rare occurence. Would happen only when has disabled Select Talents in HonorBuddy Settings and no specialization has been selected.
Singular is a Combat Routine. Targeting is handled by the BotBase, not the Combat Routine. For the Questing BotBase, target selection is controlled via a Questing Profile (.xml). Problems with a profile? Post in the authors thread. Problems with multiple profiles? Post in the HonorBuddy Support forum.
Is the new version included with the new test build? and also https://www.thebuddyforum.com/honor...205559-ability-neck-singular.html#post1873194
Currently using Warlock Singular and after it completes a couple quests it runs all over various zones to sell stuff. I dont know if its a Singular issue, a quest bot issue, or what. Heres a log for you, im sure youll know what to do better than i would.
as i explained, there is no need to attach the log due to the problem is not stated in the logfile, it has been checked very thorough to find the problem. it simply just clicks in center of the NPC and tries to morph into it. no more explanation needed than that, no need to check the log either due to it only says moving towards enemy like any other Routine does. As for the Spirit ress i will update this reply today when i test it again just for the log purpose.
Will take a look, but the only thing Singular does in the Death behavior is handle character choosing self-rez if it has Soulstone or Ankh, otherwise nothing. It doesn't get involved in non-combat movement (dead or alive) except for some very limited circumstances (Healthstone, Mage Table). Thanks - I would expect just the GankDetect message, not the one above. Will look at this for next release. That's sounds like a bug. Thanks for the log I would expect that as well. Not sure I understand what you mean by queue other abilities. I'll look at this, but Singular does not account for user initiated actions. In other words, it neither prevents nor does anything to support user interaction outside of the HotKeys supported. Thanks for the post w/log and detailed observations! -Bobby53
Other CC's i've used puts on like a semi lock(hard framelock?), where its almost impossible to use wow's in game latency queue to fit your own keystrokes in. With singular, if i start spamming heroic strike it halts the on gcd rotation and sometimes even completely stops it. I just didn't think it would affect the on gcd rotation at all. I understand if its not intended that i "help" singular when its automated, was just an observation on the heroic strike issue I was under the assumption (as usual, sorry) that the unstuck handler was singular ? The log entry was for getting stuck and getting into a load loop. Was doing it for 5 hours on the same spot just trying to run forward. The spirit healer issue is consistent and can be reproduced whenever you want. (At least in ashran, i dont bot other bg's. Cant see why it would behave different tho.) The issue (if you didn't know) is that the bot is ignoring the spirit realm bubble and trying to run and corpse ress. If someone takes your insignia after death it completely bugs out and either goes offline/gets kicked/bg is over.
What Class+Spec are you?: DK blood What 'context' is the bot in? (Instance, BG, Normal): ashran...BG What level are you?: 100 Have you made any modifications to Singular?: nope What time (HH:MM:SS) or LogMark did your issue occur? 00:24:50.201 What happened (be specific)? there are those bonfires in ashran where you as player can't walk on but the mobs can. The bots try to also stand into the bonfire, but it can't so it will try to jump until it's dies. The weird this is that it doesn't need to walk into the bonfire because it can just attack the mobs even without standin into the bonfire if you want need to coords here are they Did you attach a complete debug log? (choose one: YES or YES) YES
Noticed that no matter what your settings, you'll lose control of your character as singular tries to move you so you're not LOS of your target (was using honorbuddy's combat bot). It used to not do it. It's not good for players to lose control of their character in any way; we need to be able to disable this so that it's our choice to move/not move. Just need to search for multiple entries of "MoveToLoss[Moved]" in the log.
it happens with kicks questing pack any questing pack it targets the normal one but the guy that is targeting me another mob he wont kill that unlees he killed the first one that he targeted its weird
As a restoration druid when it uses Incarnation: Tree of Life it tries to spam Lifebloom on everyone it can. However, tree of life no longer lets you have multiple lifeblooms at once so it just ends up switching it between different targets wasting mana and gcds.
View attachment 38628 2015-02-27 13.22.txt Hunter stands there for about 3-4 sec's after being attacked. then starts attacking. and no i'm not using 769. i did the HB automatic update to 770. doesn't happen all the time . but just noticed it since bot being updated with 6.1
Very minor thing i found. Class config -> Enemy control -> "Evade attacks allowed" is always reset back to 8 after exiting honorbuddy. You can save and open, start bot etc but soon as you exit and start again its back to 8.
