|1.3 release||1.87 KB||Nov 14, 2014||6.0.3||1,301||Download|
|1.2 release||1.88 KB||Feb 6, 2014||5.4.2||339||Download|
|1.1 release||2.09 KB||Oct 31, 2008||3.0.2||2,110||Download|
|1.0 release||2.05 KB||Oct 8, 2008||2.4.3||465||Download|
|FDLogger 1.0 release||1.69 KB||Jul 20, 2008||2.4.3||18||Download|
|FDLogger-r81784 beta||1.93 KB||Sep 16, 2008||2.4.3||268||Download|
|FDLogger-r78175 beta||2.04 KB||Jul 10, 2008||2.4.3||262||Download|
|r31 alpha||1.83 KB||Nov 14, 2014||6.0.3||80||Download|
|r29 alpha||1.84 KB||Feb 6, 2014||5.4.2||79||Download|
|r27 alpha||1.85 KB||Oct 31, 2008||3.0.2||96||Download|
|r25 alpha||1.91 KB||Oct 8, 2008||2.4.3||62||Download|
FDLogger is a simple addon that tries to track when which hunter was FD'd.
As normally FD does not generate combat log entries at all, not even for the hunter in question, this is kind of tricky.
This addon makes use of IsUnitFeignDeath() and the UNIT_HEALTH event which fires when a hunter FD's, even though his health is not changing.
For each UNIT_HEALTH event for a given unit, UnitClass() (language independent) is checked. If it's a hunter, IsUnitFeignDeath() is checked.
If that returns true, an entry is made into the table "FDLog", containing a timestamp and the name of the player that was feigning death at that time.
The timestamp is a unix timestamp style timestamp with .123 decimal places added for millisecond precision (so it can be converted to a date format like the combat log's, for relatively obvious reasons or be imported into something like Excel).
FDLog is marked as a saved variable, so after you're done raiding and yelling at hunters who claim to have FD'd but still pulled aggro, you can get all the data you need from your SavedVariables folder.
Enjoy – I know I got it into a working state ;D (our hunters didn't. heh.)