cameronmc88
Member
- Joined
- Jun 25, 2012
- Messages
- 241
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"
Log file neededno matter what class i use with Singular it seems as it tries to spoon the mob, this affects the pick pocket for rogues as they cannot pick pocket them due to they are being too close. Does not matter what level. the log will not help in this case. it's a range problem when moving towards enemy.
Here's a cool picture to show the problem:
http://i.imgur.com/e39c2Xm.png
i can post more pictures if needed, this is just an example.
Also, Singular has a bug with Ressing at Spirit Healer at BG/Ashran/Wintergrasp/Tol Barad and any other places with spirit healer that resses you automaticly within 1 minute.
How To attach log file (<-- Click) -----
--- 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.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
Log file needed
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).... Woke up to my poor lil bot being stuck on the same spot for 5+ hours, middle of a instance. Not a single whisper tho lol, not sure if i should be amazed or afraid
Check the log somewhere about [08:18:27.844 D] I think it gets stuck after a death around there but no idea. Was sleeping as usual.
View attachment 169069
Thanks - I would expect just the GankDetect message, not the one above. Will look at this for next release.... In the same log, im also getting spammed with:
Code:[08:18:24.983 N] (Singular) (Singular) Programmer Error - Combat Log Event On Character: filter out COMBAT_LOG_EVENT_UNFILTERED - 0818F400000000000000000006C865A4 Enemy.Paladin.65A4 - Censure 31803 on 0818F400000000000000000003749056 Me [08:18:25.063 N] (Singular) (Singular) GankDetect: received COMBAT_LOG_EVENT_UNFILTERED src=0818F4000000000000000000084A53F9 dst=0818F400000000000000000003749056
That's sounds like a bug. Thanks for the logEdit. I checked log and it seems to treat heroic strike as an off gcd ability after all.
What made me think otherwise is two fold:
1. It doesn't use heroic strike nearly enough and consistently rage caps. (see log entry [04:55:49.381 N] or [04:57:11.404 N] )
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.2. If you use heroic strike manually, it will queue all other abilities and cast nothing (where i would expect it to continue normal rotation while I spam heroic strike)
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.
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).
Did you attach a complete debug log? (choose one: YES or YES) YES<Blackspot X="4904.893" Y="-4497.42" Z="63.5293" Radius="4.203259" />
<Blackspot X="4918.146" Y="-4406.056" Z="49.61431" Radius="4.203259" />
<Blackspot X="5071.677" Y="-4558.547" Z="48.0059" Radius="4.203259" />
<Blackspot X="4994.327" Y="-4474.405" Z="63.52841" Radius="4.203259" />
<Blackspot X="4896.106" Y="-4578.702" Z="77.22555" Radius="4.203259" />
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.
Just curious if this is a typo, or explosive shots is beeing disabled with the aoe ?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:Hunter fixed - All Specs - Explosive Shot was still being cast when AOE was disabled