It's saying it should be cast when it's already up. I can't replicate it on a target dummy, only seen it during a raid. I've also seen TellMeWhen think serpent needs to be reapplied which is why I'm wondering if there's a bug in the UnitAura calls somewhere in Blizz's code.

But there is a another bug (kinda) related to serpent sting and Marks. Serpent should always be applied after Hunter's Mark and before Chimera with Marks. But it's obviously less dmg so the priority scheme isn't picking it up until later.

Serpent Sting will adjust to your current AP (that includes Hunter's Mark) everytime you use Chimera, so the priority scheme you mention shouldn't have any effect on your damage. Naturally, most hunters always cast mark before sting so this shouldn't matter anyway.

Edit: but I guess you are right, it is still a bug (haven't noticed it myself yet).

in Ulduar last night i noticed that FaceShooter v0.7.2b suggests another shot instead of pausing between explosives on explosive proc.
No big problem though since the pause is second nature by now.

That´s the expected behavior if the bug described in my pior posts were still present. It doesn´t happen as long as your Sting is the only one on the target. That´s why I´m asking if there´re other (sting casting) hunters in your raid. I didn´t have those issues with 0.6.5b when I was the only hunter in our whole Ulduar10 raid.

HM is calculated as AP*0.6*numHunters DPS so even alone, unimproved and with only as much as 20-25s ttl it should get priority over about anything but KS, ES or CS+CS-Serpent. Also CS damage takes into account if Serpent is on target or not. AS serpent stings damage should almost always be higher than a non-serpent CS it should also naturally get priority over the latter.
Under which circumstances did you get another priority? During the raid or on a target dummy? Was an old HM still running or was the mob about to die? Did another hunter have a Serpent Sting running on your target?

I also noticed serpent sting bug with 7.2 yesterday - FS suggested to reapply it with 8 seconds remaining. There was one more hunter in the raid with his SrS on the target.

Well it´s supposed to blank whenever ES would be recommended but the last ES is less than 2s ago. So the only exception I can think of is if you got an LnL proc, KS is coming off CD right after you cast ES and KS is doing more damage than ES. But back-to-back ES has always been kind of a complicated matter so I guess it´s very well possible that there´s still a bug somewhere.

Did you get that bug on every LnL proc or did it just happen while under some specific circumstances?

Guess I changed something after my last LnL proc tests. Gonna fix this along with the debuff check bug.

Yes sadly I was just testing in a deserted darnassus on a target dummy.

I'll try to get the CPU profiling test done in a raid too, when presumably the much greater number of buffs and debuffs to process could have more of an impact.

Some Rogues have noticed an issue where their Rupture DoT will sometimes not appear in NeedToKnow, EventHorizon, or the default unit frames but still cause damage. It sounds like the UNIT_AURA event might not always be being fired when there are lots of debuffs on a mob.

While I won't deny the possibility of more bugs beeing involved I'm quite sure there's some rather obvious problem with FS not detecting debuffs from other players at all. It's easy to test when you target a dummy with someone else's HM on it. FS is hard coded to not recommend casting HM unless it's got 10s or less to it run out. The bright side of this is, if I know the source of the problem it should be relatively easy to fix it.
I can start the WoW client from this machine but I've already got a few ideas what to try when I'm back home. I'm confident I'll have this one and the back-to-back ES bug fixed and v0.7.3b out this evening.

In running Uldar25 with two other hunters last night using the latest FS, I actually experienced the second problem: FS NOT recommending SrS when it wasn't up. It got to the point that I simply fired SrS whenever FS showed BA, just so I knew it would be up regularly. To be fair, for reasons I haven't figured out yet, I spent most of the fights with about 2 fps, so it could have displayed briefly and then been overwritten by ES when that came off CD I guess.

This was always in a raid with multiple hunters and multiple stings up. I'll check out the new version and see how it goes. The only reason I think it might be a blizz bug is that TellMeWhen is having the same issues when it thinks a sting isn't up on the target.

I did find an issue in the combat log with SPELL_AURA_REFRESH firing when other players cast spells. Very possible that is related to issues with UnitAura/Buff/Debuff and corrupting the caster value somehow. Would actually be pretty easy to test with 2 hunters. Have your buff checking logic print out who owns which stings. If you get two stings owned by the same player (or a sting not owned by who cast it), then you've found the bug.

Oh, do you factor in TTL in the calculations? That kinda invalidates any testing I was doing on the target dummy cause it's always sitting at 1 health or close to that.

Installed 0.7.3b, couple of problems I encounted while raiding.

1) When LnL procs, FS does not suggest any shots at all.
2) It doesn't suggest to fire serpent sting before aimed shot like it used to a few versions back if the boss is over a certain %HP.
3) And when the mob HP is low, it still suggests serpent sting and black arrow even when you are not going to get the full benefit/damage.

Ok, did some more testing on real mobs and here's what I found:

Hunter's Mark
Chimera Shot
Serpent Sting
Aimed Shot

Serpent Sting should really be before Chimera. Now maybe in terms of damage from Serpent that's not the case, but since it buffs Chimera dmg it should be cast 1st.

1) It´s not a bug, it´s a feature! It´s been theorycrafted here that in case of LnL procs it´s higher damage to wait for 0.5s after each proc (so you don´t waste any ES ticks) than filling in a lower damaging shot and essentially delaying the ES by 1s.
2) If Aimed Shot is calculated as the higher damaging shot at that moment that´s what FS suggests, I don´t see anything wrong with that either.
3) That´s due to those two shots not taking TTL into account yet. I´ll have to readd this in the next version.

Well SpS has always been priorized over CS for me already so I didn´t feel the need to change anything but seeing as CS scales better than SpS - especially considering I used an 29 dps crowssbow for most tests - I guess it´s not so unlikely after all. I can just hard code the behavior into FS.

In .7.3b Faceshooter was frequently skipping Serpent Sting and suggesting Steady Shot even when I didn't have a Serpent Sting on the target (both by eyeballing the debuffs and my PowerAuras). It was quite odd behavior in that sometimes it would properly suggest the Serpent Sting and sometimes it wouldn't. One time when I noticed this behavior I tested the addon by going 3/4 rotations past the elapsed Sting and it still would keep suggesting Steady over Serpent.

And I never hit Viper all raid

0.7.4b:
- Serpent Sting and Black Arrow damage factor in targets TTL. So for example if your targets TTL is calculated as 7s SpS damage is calculated as only two ticks.
- Serpent Sting now always takes precedence over chimera unless the target is going to die in less than 3s (it takes to cast SpS and CS and SpS to tick at least once).

I had the opportunity to test SpS detection with multiple SpS on target and it seemed like it works the way it´s supposed to do. So if you still have trouble with SpS beeing not beeing recommended when it should or the other way round - please report here. If possible include informations about targets ttl and if other hunters had SpS on target.

INstalled FS 0.7.4.b and logged in . Throwing out mass errors (currently SV specced):

[2009/07/05 13:27:17-773-x4]: FaceShooter-0.7.4b\FaceShooter.lua:1847: attempt to compare number with nil
FaceShooter-0.7.4b\FaceShooter.lua:2249: in function `Scheduler'
FaceShooter-0.7.4b\FaceShooter.lua:2526: in function `OnUpdate'
FaceShooter-0.7.4b\FaceShooter.lua:2312: in function <Interface\AddOns\FaceShooter\FaceShooter.lua:2312>

[2009/07/05 13:27:27-773-x1]: FaceShooter-0.7.4b\FaceShooter.lua:1847: attempt to compare number with nil
FaceShooter-0.7.4b\FaceShooter.lua:2267: in function `Scheduler'
FaceShooter-0.7.4b\FaceShooter.lua:2796: in function `?'
FaceShooter-0.7.4b\FaceShooter.lua:15: in function <Interface\AddOns\FaceShooter\FaceShooter.lua:15>
<in C code>: in function `UseAction'
Interface\FrameXML\SecureTemplates.lua:258: in function `handler':
Interface\FrameXML\SecureTemplates.lua:460: in function `SecureActionButton_OnClick':
Interface\FrameXML\ActionButton.lua:40: in function `ActionButtonUp':
<string>:"ACTIONBUTTON6":4: in function <[string "ACTIONBUTTON6"]:1>

[2009/07/05 13:27:27-773-x14]: FaceShooter-0.7.4b\FaceShooter.lua:1847: attempt to compare number with nil
FaceShooter-0.7.4b\FaceShooter.lua:2267: in function `Scheduler'
FaceShooter-0.7.4b\FaceShooter.lua:2526: in function `OnUpdate'
FaceShooter-0.7.4b\FaceShooter.lua:2312: in function <Interface\AddOns\FaceShooter\FaceShooter.lua:2312>

Bah sorry about that. Forgot to set some brackets properly which caused those bugs if you´re not MM specced. Should be fixed with 0.7.5b

Probably a leftover: FS keeps spamming
[16:41] DEBUG: Chimera Shot?!? while raiding/shooting.

Indeed. You can either fix it by removing the line or downloading 0.7.6b *sigh*

I've gotten this twice now, once with 0.7.3b yesterday, and again today as soon as I started shooting with 0.7.6b:

I don't think I was doing anything particularly odd when it popped yesterday, and definitely just firing shots as normal today (I *think* it triggered when I fired a chimera, but not sure).

Once it happens, the rotation seems to get stuck on suggesting Chimera Shot. See if I can get reproduction steps for you now.

edit: Reproduction

- Only happens as MM, not survival

1. Target one of the level 60 target dummies
2. Hunter's Mark
3. Serpent Sting
4. Chimera Shot
5. Steady Shot - as soon as you steadyshot, you get the error

After this the rotation display seems to be stuck on Chimera till you reload/respec.


Also, since the TTL calculation seems to stop serpent and black arrow ever being suggested while you're on a target dummy, is there any work around practice mode to make it display again for dummies :P I imagine some others would like being able to do rotations with it that do involve keeping the DoTs up but on a target dummy.