LibFail-2.0

10 - Add a fail type for interrupts

A large number of fights in the game have a mechanic of:

Boss casts "Huge Spell of Death that Must be Interrupted"
Some/Any group member must interrupt it or someone (possibly multiple ppl) dies.

It would be really nice if LibFail had the ability to report the failure to interrupt, which is often just as important a fight mechanic as moving out of fire. The obvious problem is the person who died is often not the one who messed up, and we don't have enough information within the addon to correctly assign "blame" for the missed interrupt (because the interrupt assignment is done in vent or party chat and does not show up in the combat log). However despite this limitation I think it would still be useful for LibFail to report that a death was directly due to someone failing at fight mechanics (and not eg lack of heals). I'm imagining a fail like:

Someone failed at interrupting [Huge Spell of Death that Must be Interrupted], which hit JohhnyInnocent.

Where "Someone" is a generic "we don't know who to blame" string, and the player name at the end is optional and just indicates who died as a result. It probably makes sense to omit these fails from the fail stats, or possibly we could create a dummy "Someone" player to hold them.

Some motivating examples:

Feludius Hydrolance
Nefarion phase 2 Blast Nova
Maloriak Arcane Storm
Rajh Inferno Leap
High Priestess Azil Force Grip

many many others..

I volunteer to implement this idea if it's popular

User When Change
oscarucb Aug 25, 2011 at 06:24 UTC Create

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

  • 3 comments
  • Avatar of Lumanas Lumanas Nov 23, 2011 at 06:46 UTC - 0 likes

    Do it

  • Avatar of oscarucb oscarucb Sep 05, 2011 at 18:14 UTC - 0 likes

    I agree it's more useful in situations where traditionally exactly one person is assigned ahead of time to interrupt the given ability (eg Maloriak Arcane Storm) - so that when LibFail says "someone" failed at interrupting, everyone in that group knows it actually means "JoeBob". This is especially true in 5-mans where basically no fight requires more than a single interrupter, and in 10-mans where its very rare to need more than 2 interrupters for any given fight.

    However even in cases where there are multiple interrupters assigned (Nerfarion P2, Alysrazor) I think it's still useful if you set it for overkill only - it essentially acts as an online fatality diagnosis. Ie, this death was caused by someone else failing at fight mechanics (interrupting), as opposed to just lack of heals. And of course, any given detection can be turned off by the user (or even by default) if it's found to be too spammy.

    Last edited Sep 05, 2011 by oscarucb
  • Avatar of mysticalos mysticalos Sep 04, 2011 at 04:19 UTC - 0 likes

    constructively i cannot agree with this one. Interrupts are entirely subjective. look at heroic alyzrazor. you need 3 interrupters per side, 2 on current add and 1 rover to go get the first interruptor on next add while the first 2 finish previous off (earlier tier anyways, now that 3rd is less important as dps checks become faceroll). But just saying "somoene in raid failed at interrupting" isn't really telling us useful information. unless a fail can assign blame to an actual party, it's just spam. that's no different then saying "someone in your raid stood in a fire".

    well i don't care if i that doesn't identify the problem(ie the person)

    I think the entire purpose of libfail is to report individual fails of raid members for quickly addressing the issue. An evaluation of personal performance not to screw up or people are yelling at you.

  • 3 comments

Facts

Last updated
Sep 04, 2011
Reported
Aug 25, 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