Evade misses are normal and encountering one does not mean the mob is evade bugged. In my testing I found 8 to be the best default as it does not keep you attacking an evade bugged mob too long, while still allowing some tolerance for mobs which evade briefly then stop. This control value was made a user setting so please feel free to change to whatever value suits your needs best. Be sure to post one or more logs with examples if you are advocating a different default value, -Bobby53
Wench, Thanks for taking the time to post. You will want to following the steps in Reporting Bugs in Singular (click here). If its unclear why that info is needed, I explain a bit further in Bobby53's Standard Request for More Info (click here).
Hordebegone, Thanks for the post. Typically this is would be too vague a description for me to research, but since you are using a Warlock I am assuming you are encountering the same issue others reported. A fix will be posted shortly for that issue, -Bobby53
There was a time span of 17 hours 34 minutes between these posts, so not sure if you a referring to a different post that I did not see because it was removed for lacking the required detail. I check the forums daily on average, so for the timeliest response be sure to provide clearly written issue posts as described in the posts I referred you to earlier. The vague description "Just as the heading states..." typically is a sign that there won't be enough detail provided. Have been ill this week and have not checked since Monday. Apologies to all members waiting on a fix for Warlock -Bobby53
The default value was just my curiosity, its fine, all thought i think 8 is bit high. (Personal preference, I would advocate 4.) My current issue (and i'll be happy to supply log if it doesn't match your side) Is whatever value I set manually is reset back to 8 upon exit of HB. Tried latest singular and fresh install, still always back to 8 after exit. I know you said you fixed this the first time i reported it but that doesn't seem to be the case
I had fixed, but fix didn't get published for some reason. Look for fix in next release (about to publish new one after a little more Warlock testing.) -Bobby53
cevaps, Currently Shaman (Elem/Enha) and Monk (WW) have full Offheal support, meaning they will switch to full healing mode based upon the settings established for Offhealing. There are isolated cases of incidental offhealing (like Feral Druid using Predatory Instinct buffs to heal the lowest health team member.) I will be adding support for offhealing by all classes with a healing spell in an upcoming release. -Bobby53
*new* Singular v4.0.0.4557 available for download! Fix for Warlock not sending Pet to attack prior to casting and a few other fixes. See Change Log for details Available for download from Post #1 of this thread Code: --- Release 4.0.0.4557 --- General fixed - Evade Attacks Allowed: setting now correctly saves and loads from settings file Warlock fixed - All Specs - Pet Attack: was not being initiated before Warlock cast fixed - All Specs - use of Whiplash and Fellash when attackers targeting warlock and in melee range fixed - All Specs - Blood Horror: message displayed identifying attacker which resulted in cast
Something is broken with rogue stealth. Fresh install it goes like this: [Singular] Pull More: disabled, only Questing will Pull targets [Singular] Stealth: 'Auto' cast for Pull of Non-Trivial Targets (MaxHealth > 0) [Singular] warning: Cloak and Dagger will be skipped on Pick Pocketable mobs. Turn off 'Use Pick Pocket' to always use ranged Ambush, Cheap Shot, and Garrote. Turn off "Use pick pocket" i get this: [Singular] Pull More: disabled, only Questing will Pull targets [Singular] Stealth: 'Auto' cast for Pull of Non-Trivial Targets (MaxHealth > 57xx) Bit tired but 57xx is filled based on my current hp. But why have that at all ? It makes no sense ? Even setting trivial to 90% and lowering maxhealth to under 1k it still refuses to use stealth. Only way to get it to stealth is using Stealth -> Always but that breaks questing and various events. View attachment 4428 2015-04-04 19.45.txt Edit. Setting Trivial value to 0 and forcing my own maxhealth is making bot stealth. Which doesn't exactly make sense either.. > 5k or >10k shouldn't matter, none of the mobs are over 3k :S Bit hangover after a long weekend but feels like im missing something really obvious here
Well, there is a bug causing display of Trivial MaxHealth before its been calculated. In otherwords, the default is 50 so you should expect to see 50% of your characters Max Health displayed as the value, but it displays 0 the first time. This is because the message Stealth: 'Auto' cast for Pull of Non-Trivial Targets (MaxHealth > 0) is being output before the value of TrivialMaxHealth is calculated (fixed in next release.) So the displayed message does not match the actual value used for testing if an enemy is trivial or not unless you Save the Class Config settings without changing this value. This could have only made the hangover worse.... my apologies Regarding comment that the only way to get Stealth to work is Stealth -> Always does not match my results. Reasons why it won't stealth when Stealth -> Auto (and should not): 1. Rogue already has agro 2. Targeted mob is trivial EnemyMaxHealth > ((PlayersMaxHealth * TrivialHealthPercent) / 100) 3. Combat Routine PullBuffs behavior not being called 4. Harmful aura exists on Rogue Based on your results, it sounds like the issue was the Trivial Health setting. At the point you turned Pick Pocket off the Trivial Health setting was at 50% so any mob with a maxhealth below 5700 would be considered trivial (and not worth the effort of stealthing.) Here is an example of one you encountered at that point: Code: [17:54:10.278 N] (Singular) YourCurrentTarget: changed to: Umbrafen Oracle.2315 lvl=60 h=100.0%, [COLOR=#ff0000][B]maxh=2937[/B][/COLOR], d=62.3 yds, box=1.7, boss=N, [COLOR=#ff0000][B]trivial=Y[/B][/COLOR], player=N, attackable=Y, neutral=N, hostile=Y, entry=18077, faction=51, loss=N, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, TargetIndex=1, creature=Humanoid, tagme=N, tagother=N, tapall=N Anyway, if you want to have Stealth -> Auto work regardless of the target mobs max health, set Trivial: Mob Max Health % to a very low value (ex. 0) If it does not stealth at that point, we need to focus on a specific occurrence. Add a LOGMARK at the point your Rogue does not Stealth and you felt it should have and upload the log. Thanks for the post and log, -Bobby53
Thanks for the quick response! Stealthing fine with Trivial = 0% Also wanna give a nod to your wonderful log output, really helps pinpoint issues It was the trivial health setting but it was never touched. Only setting changed was disabling pick pocket. This is even more confusing now. The bug actually produced the results i was looking for. This is a vanilla account, no heirlooms, using kicks profiles. I was lvl 62 in a lvl 60-64 zone which is level appropriate. I was ~11k hp at the time and standard quest mobs around 3-5k. Meaning majority of them is considered trivial but not stealthing is causing a few performance based issues. Such as: Taking more damage. (Causes high food consumption / deaths) Taking considerable longer to kill mobs. Taking longer to reach mobs. Can't use "Pull more" functionality. Maybe revise the default value or perhaps use a leveling value 1-99 and one for max level ? Thanks
Understood. Am going to revise the trivial mob detection to factor in both % maxhealth and level differential.
Hi Bobby. Would it be possible for you to implement a feature for Feral druids that will shapeshift in and out of roots etc. Thanks - Ferhal
Hello Bobby. I'm gonna do something you hate and I'm sorry in advance! I'm making something where I'm forced to interact with low flying mobs but out of range for melee abilities and singular struggles to handle it. With default settings it loops: Code: [04:03:26.505 N] (Singular) (Singular) HeroicLeap: jump target is hitbox of ..F979 [04:03:26.506 N] (Singular) (Singular) HeroicLeap: aborting, target is 45.837 off ground and melee is 6.133 Turn off heroic leap and charge it looks like this: Code: [04:27:09.472 N] (Singular) [WoWRedError] You are too far away! [04:27:09.675 N] (Singular) ... [prot] h=99.8%/r=24.0%, stnc=DefensiveStance, Ultim=False, aoe=1, cc=0, dmg1500=0, dmg5000=0, Unyielding Strikes=0 ms, Avatar=0 ms, Targ=..FE59 100.0% @ 55.9 yds, Melee=False, Facing=True, LoSS=True, DeepWounds=0 [04:27:10.207 N] (Singular) MoveToMelee(Moved): towards ..FE59 @ 51.9 yds The culprit is that heroic throw is only part of the pull behavior and not the actual rotation. I did a work around in protection.cs and added it but singular is moving under them and heroic throw cant be used so close.(even with !Target.IsWithinMeleeRange) It also doesn't use taunt for pull behavior. Glad had the same result.
Druid lvl 100 using Grindbot While try to cast "Healing Touch" he still move on and cant finish the Cast, looks very crazy (stop, cast, move, stop, cast, move and so on). Code: [08:26:54.302 N] [Singular] *Healing Touch on Me @ 62.6% [08:26:54.496 N] (Singular) [WoWRedError] Interrupted [08:26:54.497 N] (Singular) (Singular) [CombatLog] SPELL_CAST_FAILED Healing Touch#5185 failure: 'Interrupted' [08:26:54.637 N] (Singular) YourCurrentTarget: changed to: Leatherhide Clefthoof.8EC9 lvl=98 h=0.0%, maxh=78374, d=5.1 yds, box=5.0, boss=N, trivial=Y, player=N, attackable=N, neutral=N, hostile=Y, entry=78575, faction=16, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, creature=Beast, tagme=Y, tagother=N, tapall=N [08:26:54.640 N] (Singular) Rest Heal @ actual:62.6% predict:63.9% and moving:False in form:Normal [08:26:54.642 N] [Singular] *Healing Touch on Me @ 62.6% [08:26:57.354 D] Loading Draenor_21_26 [08:26:57.405 N] theTramper timber | Moving to Small Timber at <3205.075, 5747.193, 61.32903> [08:26:59.752 N] (Singular) Rest Heal @ actual:74.1% predict:75.3% and moving:False in form:Normal [08:26:59.753 N] [Singular] *Healing Touch on Me @ 74.1% [08:26:59.775 D] Garbage collected 1 nav tiles [08:26:59.967 N] (Singular) [WoWRedError] Interrupted [08:26:59.968 N] (Singular) (Singular) [CombatLog] SPELL_CAST_FAILED Healing Touch#5185 failure: 'Interrupted' [08:26:59.979 N] (Singular) EnsureMovementStopped: stopping! to heal [08:27:00.038 N] (Singular) Rest Heal @ actual:76.6% predict:77.8% and moving:False in form:Normal [08:27:00.377 N] (Singular) Rest Heal @ actual:76.6% predict:77.8% and moving:False in form:Normal [08:27:00.040 N] [Singular] *Healing Touch on Me @ 76.6% [08:27:00.379 N] [Singular] *Healing Touch on Me @ 76.6% [08:27:00.636 N] (Singular) Rest Heal @ actual:76.6% predict:77.8% and moving:False in form:Normal [08:27:00.846 N] (Singular) Rest Heal @ actual:78.0% predict:78.0% and moving:False in form:Normal [08:27:00.638 N] [Singular] *Healing Touch on Me @ 76.6% [08:27:00.848 N] [Singular] *Healing Touch on Me @ 78.0% [08:27:01.190 N] (Singular) EnsureMovementStopped: stopping! to heal [08:27:01.241 N] (Singular) Rest Heal @ actual:78.0% predict:78.0% and moving:False in form:Normal [08:27:01.243 N] [Singular] *Healing Touch on Me @ 78.0% [08:27:01.445 N] (Singular) Rest Heal @ actual:78.0% predict:78.0% and moving:False in form:Normal [08:27:01.785 N] (Singular) Rest Heal @ actual:78.0% predict:78.0% and moving:False in form:Normal [08:27:01.447 N] [Singular] *Healing Touch on Me @ 78.0% [08:27:01.786 N] [Singular] *Healing Touch on Me @ 78.0% [08:27:02.110 N] (Singular) Rest Heal @ actual:78.0% predict:78.0% and moving:False in form:Normal [08:27:02.384 N] (Singular) EnsureMovementStopped: stopping! to heal [08:27:02.111 N] [Singular] *Healing Touch on Me @ 78.0% [08:27:02.438 N] (Singular) Rest Heal @ actual:78.0% predict:78.0% and moving:False in form:Normal [08:27:02.777 N] (Singular) Rest Heal @ actual:78.0% predict:78.0% and moving:False in form:Normal [08:27:02.440 N] [Singular] *Healing Touch on Me @ 78.0% [08:27:02.779 N] [Singular] *Healing Touch on Me @ 78.0% [08:27:03.054 N] (Singular) Rest Heal @ actual:79.0% predict:79.0% and moving:False in form:Normal [08:27:03.376 N] (Singular) Rest Heal @ actual:79.0% predict:79.0% and moving:False in form:Normal [08:27:03.055 N] [Singular] *Healing Touch on Me @ 79.0% [08:27:03.377 N] [Singular] *Healing Touch on Me @ 79.0% [08:27:03.651 N] (Singular) EnsureMovementStopped: stopping! to heal [08:27:03.720 N] (Singular) Rest Heal @ actual:79.0% predict:79.0% and moving:False in form:Normal [08:27:03.721 N] [Singular] *Healing Touch on Me @ 79.0% [08:27:04.115 N] (Singular) Rest Heal @ actual:79.0% predict:79.0% and moving:False in form:Normal [08:27:04.116 N] [Singular] *Healing Touch on Me @ 79.0% [08:27:04.511 N] (Singular) Rest Heal @ actual:79.0% predict:79.0% and moving:False in form:Normal [08:27:04.513 N] [Singular] *Healing Touch on Me @ 79.0% [08:27:06.828 N] Stopping the bot! [08:27:06.828 Q] Bot stopping! Reason: User pressed the stop button
tumbum, See line in bold red above. Singular is attempting to stop and cast Healing Touch, but plugin appears to be ignoring cast in progress. -Bobby53
