Midnight, I love the addon, replaced a bunch of my power aura setups, my addon "TimeToDie" and fortewarlock. It's simple, easy to configure. Love it.

One thing that gives me a bit of annoyance is when LnL procs and the addon doesn't suggest any filler shots in between to allow the dot to tick, so I just had to do my own thing.

EDIT: after playing around with it, I got some suggestions. First the sniper training, I suggest making the icon gradually change colour from green to red instead of just green at 14s (when it refreshes) and then red at 6s. And for aspect, make the default set at max 90 and min 30 for example, because for me when I started using the addon, I thought aspect wasn't working but it was because both max and min threshold were set at 100%.

v0.6.0b working great (except ttl)

Did you try it on actual mobs or just on target dummies? Unlike most damage meters FS measures dps not by parsing the chatlog for outgoing dps but rather via targets healthloss over time. So if the target doesn´t loose any hp it can´t evaluate dps either.

TTL worked fine when I did emalon10 yesterday.

@Midnight

What do you think about a darken red feature when out of range?

Is there any wait time for Kill Shot coded in FS? I know wait time has already been discussed, but I was hoping this particular shot might be easier to calculate. In my experience it does often come down to a tight diff in cool down between KS and ES so .. hm

I like how the Aimed icon switches to Multi-Shot when I fire it as it rotates off in cascade mode.

I also use a modified version of Face Mauler for my Ret paladin, not sure if you are aware of it or not.
Serious Help In Timing - Addons - Curse

It has a neat interface compatibility for options.

@Midnight

Seeing the following errors on my hunter:

Date: 2009-06-01 22:02:20
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\FaceShooter\FaceShooter.lua line 1022:
attempt to perform arithmetic on local 'duration' (a nil value)
Debug:
(tail call): ?
[C]: ?
FaceShooter\FaceShooter.lua:1022: CollectData()
FaceShooter\FaceShooter.lua:1140: Scheduler()
FaceShooter\FaceShooter.lua:658: UnitCheck()
FaceShooter\FaceShooter.lua:1313: ?()
FaceShooter\FaceShooter.lua:14:
FaceShooter\FaceShooter.lua:14
[C]: CameraOrSelectOrMoveStop()
[string "CAMERAORSELECTORMOVE"]:4:
[string "CAMERAORSELECTORMOVE"]:1

1st post but long time reader

Great add-on Mid i replaced my Watcher with it. Working greatly for SV but for MM i noticed something:

1) when starting shooting at a mob it gives as 1st priority chimera instead of serpent (it's not a real problem)
2) while shooting if aimed shot goes off CD it doesn't appear on shot priority square it still gives steady shot.

Again really nice work with it!

Best Regards

Katane

@Midnight

Immediately after I logged in, I went out and tab-target a mob. I immediately got the following error:

Date: 2009-06-06 21:41:36
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\FaceShooter\FaceShooter.lua line 1129:
attempt to perform arithmetic on local 'duration' (a nil value)
Debug:
(tail call): ?
[C]: ?
FaceShooter\FaceShooter.lua:1129: CollectData()
FaceShooter\FaceShooter.lua:1265: Scheduler()
FaceShooter\FaceShooter.lua:706: ChangeFrameVisibility()
FaceShooter\FaceShooter.lua:1495: ?()
FaceShooter\FaceShooter.lua:14:
FaceShooter\FaceShooter.lua:14
[C]: TargetNearestEnemy()
[string "TARGETNEARESTENEMY"]:1:
[string "TARGETNEARESTENEMY"]:1

That´s because at lvl 70 you don´t have Kill Shot yet. The AddOn isn´t really meant for leveling so it doesn´t consider rotations for lower levels where important skills are still missing. I should implement a check though.

Good enough. I was wondering if my level had anything to do with it. Thanks for getting back to me.

Been trying it out, comments problems so far:

- if you have sniper training up and switch specs to MM, the sniper training frame keep showing the sniper training icon, even after the buff finally fades. This is a little annoying - reloading ui without the buff up seems to fix it though.

- the mod doesn't seem to take much processing power (turning on CPU profiling seems to peg it at around 6% of my moderate load, which is higher than a lot of mods, but a lot less than my worst cpu hogging mods) however it seems to take quite a bit of memory: over 4 megs. This doesn't really matter since afaik the amount of memory consumed by a mod has no real impact on performace, but it seems odd that it would take that much

edit: ok looked at it more, its memory used when out of combat is only 100kb which seems much more reasonable, however this climbs very very rapidly while shooting, around 100kb per shot (or perhaps per second). I haven't tried it in a raid, but that sounds like it could get unpleasant on a long fight if it keeps going past 4 megs - is this something to do with the TTL calculation?


- does the hunter's mark recommendation taking into account TTL? that would be the best use of it imo "is this trash mob going to live long enough for it to be worth a gcd for me to mark it (considering the damage from Marked for Death if I have the talent, and just the AP from the mark itself). I notice that with 0.62b it's recommending I mark dummies while I'm already in combat with them, even though it can't have a TTL calculation for them?

edit #2: ah, I looked at the code and apparently I misunderstood what the mod was doing - it looks like it's just works through a static priority list of abilities, it's not trying to decide dynamically which one is best.

Are you planning at some point to make it actually calculate how much your chimera shot does compared to your steady shot, and based on that recommend whether to wait on chimera or just fire a steady shot now? This would tie into my aimed shot calculation above too, since that depends on knowing how much damage a GCD used on HM costs you, and how much damage you'd gain from HM given your current DPS and the target's current TTL.

As it stands the current static priority list is something I think most of us can remember anyway (and it has the priorities wrong for some us too, spreadsheet shows me gaining dps by putting arcane before aimed as MM), so the mod seems a little excessive (but full of promise!)

edit #3!: if you do make the Aspect switch calculations smarter, it would be nice if they incorporated logic like "if I'm in viper but have mana to chimera + arcane and aimed, and all are off cooldown, switch to hawk, fire all 3 shots, then switch back to viper and keep steadying". Right now it seems to be just "hey I'm oom, switch to viper... oh i'm full switch to hawk" which like edit #2 seems a simple enough thing that a mod for it isn't needed.

The code for each priority list is neatly laid out enough though that if you just found a way to provide expected damage for a shot and current dps, a user could add the above logic into their own priority file very easily, making this an amazingly useful mod.