Skip to Content
8-15-2009 @ 8:31PM
Only problem I see with this article is the bit about failbot - I've seen it incorrectly report information too often to trust it anymore (according to my GM's failbot I've been hit by Mimiron's rockets 7 times in one fight... maybe I'm just op?). Even if you trust it, though, I find that looking through each person's record of death via Recount or something similar is more informative.
8-15-2009 @ 8:48PM
Acheron is another good mod for charting deaths/mistakes. The raid leader can use it to see everything that happened leading up to each raid member's death and can broadcast that report to a specified channel.
8-15-2009 @ 8:49PM
It's not saying you've been hit by seven rockets -- it's the seventh failure for you of the raid.
8-15-2009 @ 9:19PM
I know how to read failbot, thank you. I'm saying the message popped up 7 times in 1 fight (in which I wasn't hit I might add).
8-15-2009 @ 9:38PM
lol, touche.Seriously, though, there were complaints from guild members about failbot's inaccuracy, so our raid leaders scrapped it a while ago.
8-16-2009 @ 4:39AM
Just FYI: Failbot was discontinued/abandoned by it's developers. There are alternatives however, Ensidiafails for example. Also FYI: When Failbot reports your name for a fail the number appended to the end is the number of times you have been failed at that type since the mod was reset - when your raid leader decides to reset the mod is completely at their discretion. E.g: Neirin fails at void zone (4) Means that you have been hit by a void zone and that the mod has recorded you being hit on three separate occasions, those occasions may have been 5 months ago however unless your raid leader has reset the mod for the raid / encounter. In the mod suggested by the authors as a replacement there is an option to automatically reset the fail counters upon encounter start. And yes, I'm one of those annoying raid leaders who will run these mods during any raid, Ulduar 25 or a Sarth1D pug run with alts. Name and Shame is unfortunately the only way that most people (from new players, to experienced raiders) will learn from their mistakes.
8-16-2009 @ 12:30PM
From The Developers of Failbot:"I have recently quit raiding and will soon be quitting WoW altogether, so I will no longer be able to maintain and update this project. I suggest checking out EnsidiaFails for a proper replacement:http://wow.curse.com/downloads/wow-addons/details/ensidiafails.aspx"EnsidiaFails does appear to generate inaccurate numbers regarding the total number of failures. True you can set options to count the total number of fails per fight but I reset mine per wipe and still see off totals. I am not really sure but I am guessing for example when you standing void zone it counts ticks of dmg so one void zone might equal 4 times due to the dmg ticks? Unsure but the fact remains during the fight it does correctly identify when a fail occurs. On OS25 for example one guy generated an event every time so we started calling out his name and telling him to moving right or left specficly. The event generation is more accurate than the count totals so pay more attention to that.I have had the raid complain about the spam generated and I find using a seperate channel that people can choose to join helps.Bottom line is on things like the clouds on yogg-saron...ensidiafails or any other failbot alternative is not going to help. You have to watch your raiders and have others report behavoir. The shame game sucks but addressing an issue with a person having trouble with an issue is going to make them a better player. We had a player spawning adds in the clouds. Taking him aside and explaining cloud movement and add generation, had the raid going from wiping in the first phase to going through it like butter so it helps!
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.