Defailure
This addon determines who failed at Defile.
EnsidiaFails is not really usable for determining who the hell messed up, because it displays everyone who got damage from defile anytime.
So Defailure determines who "failed" like that:
When a player gets defile, it records the first one that gets damage from Defile (i.e. causes it to grow).
If the first one is the player who got the Debuff, the second one is considered responsible (the player that got the defile has one "free pass").
It displays the fail during combat and a statistic at the end of the fight.
Comments
-
profalbert Owner
-
View User Profile
-
Send Message
Posted Sep 12, 2010As far as I can see, EnsidiaFails uses only the LibFail-callback to determine who failed at defile. This callback fires when someone made the defile grow, nothing more and nothing less. I actually use that same callback in this addon.
It is accurate about who made it grow, but not everyone who made it grow actually failed (imho). When it grows really large, there are tons of fails and it's difficult to determine who was first.
Well I don't know about heroic mode, but in normal mode the defile-target should only make it grow once. If it actually is twice on HM, I can always change it.
But wrt to the idea of the 2 people only triggering defile because, someone else messed up previously, that's exactly what this addon is about.
As I understand you are a co-author of LibFail and EF. You may feel free to use my code in LibFail if you like.
However, I don't think it's really clean enough to be in a lib. It uses OnUpdate to poll the defile-target and a hardcoded "cooldown" for defile-fails.
-
View User Profile
-
Send Message
Posted Aug 26, 2010why not just try to contribute better code to libfail?
although EF method seems pretty accurate to me, i believe it actaully checks for taking damaga twice within 3 seconds. (ie you defintely made it grow if your name popped up)...you may not consider it a fail if someone made it grow twice and in tern 2 more people were in it only cause it grew, but those 2 poeple who were at edge probably grew it even more even though it awsn't their fault, makes a fail like this really hard to perfect in who screwed up vs who just got caught in it's path when it grew. but from my experience libfail does pretty accurate show a fail when it grows. its become guild prractive to just assume it's gonna grow at least twice and don't stand near the defile and be a contributer to it's growth by getting caught in it.