Death cutoffs and called wipes in Warcraft Logs

A point in each pull after which nothing is counted: the first death, the third, or the moment the wipe began. Everything a player did before it is judged; everything after is left out.

Because once a pull is lost, the raid stops playing it: tanks stop swapping, players stop dodging, some walk away from the keyboard. Counting those minutes charges people for a pull that was already over, and buries the mistakes that lost it.

From two signals in the log. Whichever comes first is the wipe, since the pull was lost from that moment:

• A mass death: at least 40% of the raid (3 players or more) dying with no more than 12 seconds between one death and the next, running into the end of the pull. A real wipe looks like this: a burst of deaths, not a slow fade.
• The raid stopping: the players still alive stop casting and never start again.

The raid giving up while still alive. LogSnitch measures, second by second, the share of living players who cast something. When it falls under 65% of the pull's usual level (its 75th percentile) and stays there to the end for 15 seconds or more, the wipe was called at the start of that stretch.

Why 15 seconds: a puzzle mechanic makes the raid stop casting too, while players pair up or move, but the raid recovers within 10 to 15 seconds once it is solved. On one Mythic Entombed Sentinels pull, two players failed Helical Toxins; a second later the share of players casting, near 100% all pull, fell under the line and stayed there for the last 30 seconds, twenty seconds before the mass death.

No hotkey is needed: the call is read from what the raid did, so it works on any uploaded log.

• Until the wipe (the default): what happened before the wipe began, mass death or call.
• Until 1, 2, 3 or 5 deaths: to see only what led to the first deaths.
• The whole pull: everything, to the last second.

A kill, or a pull reset with no wipe to find, is read to its end. The cutoff applies to every mechanic at once, deaths included.