LibFail-2.0

15 - Revert r107

Both attacks are avoidable, if you're getting hit you're doing it wrong. Whether you survive or not. It's only spammy if you're bad. especially shockwave. there is NO EXCUSE for getting hit by shockwave. The visual is obvious.

User When Change
mysticalos Dec 16, 2011 at 21:26 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 5 comments
  • Avatar of oscarucb oscarucb Dec 20, 2011 at 06:14 UTC - 0 likes

    I'm not saying getting hit by shockwave is OK, I'm saying that when you're in a typical LFR with half the raid pulling 15k or less, standing in shockwave is the least of their problems.

    I'm coming around to the conclusion that what we need is for EF to detect LFR raids and by default only tattle on pugs who failed so badly they killed themselves. People can (and will) quibble about the importance of various fight mechanics in LFR-faceroll difficulty, but fails that lead to fatality are the one case where it's easy to justify the spam.

  • Avatar of mysticalos mysticalos Dec 19, 2011 at 17:47 UTC - 0 likes

    I agree with maat. the libisn't responsible for how the user uses it, if someone uses EF or something in LFR, then the user is the problem not the lib. the lib is just a reporting tool and shockwave is a fail no matter how you look at it, even if you dont die,as he said, you get stunned, and it hits pretty hard on heroic even before his vengeance is high enough to one shot you, so it adds healer stress.

  • Avatar of oscarucb oscarucb Dec 17, 2011 at 10:16 UTC - 0 likes

    One possible solution is to change EnsidiaFails so that by default it only reports fatal failures in LFR difficulty (ie it effectively sets all "overkill only" options to true in LFR).

    We all know the social context of LFR is very different from guild heroic runs, and spamming people who don't care for fails that barely matter just makes our end users look bad and our addon unattractive.

    I know this addon wasn't really designed for this type of "casual raiding" but the fact of the matter is all our "serious raiders" are also running LFR at least once a week, so we can't ignore this usage case. In fact I'd argue that our addon is probably used in more LFR raids each week than guild runs, since every main that does a heroic guild run presumably also runs LFR, but many people run alts in LFR that don't get heroic guild runs.

  • Avatar of Maat Maat Dec 17, 2011 at 10:07 UTC - 0 likes

    I partly agree with both of you.

    Blade Rush is way too spammy, and even on heroic difficulty it is not deadly.

    However, Shockwave is a dps loss if you get stunned (which you do even in LFR), so even if it may be spammy, it is still a pretty big fail.

    Now I realize that people don't care about fails in LFR and the "spam" of the addon might annoy people, however to determine that is not the libraries job, it is the frontends and the users.

    So if you want an option that'd somehow reduce the reported events it needs to be in the frontend (EnsidiaFails).

  • Avatar of oscarucb oscarucb Dec 17, 2011 at 09:52 UTC - 0 likes

    Yes, they're avoidable, but the fact of the matter is on LFR difficulty they're also trivial. Shockwave hits for about 30% of your health on a geared dps, and blade rush is so small that as a ranged it's not even worth moving to avoid.

    The change to default overkill-only makes it so that instead of printing 200 pointless messages during an LFR kill, it only prints the one or two cases where someone with low health stood in bad and died as a result. Ultimately, if standing in bad didn't get you killed, it's really not worth spamming the raid about it - you can always consult damage meters and other tools to see who took avoidable ambient damage if you care.

    Finally, if you really want to spam your raid for avoidable non-fatal damage, just uncheck the "overkill only" option and you get that effect. Given the overwhelming popularity of LFR raids (where most forms of fire are non-fatal) this addon really needs to carefully set defaults to avoid spammyness or casual users will simply uninstall it to avoid pissing off LFR groups.

  • 5 comments

Facts

Last updated
Dec 17, 2011
Reported
Dec 16, 2011
Status
New - Issue has not had initial review yet.
Type
Enhancement - A change which is intended to better the project in some way
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees