Their Dancing Mad history
Every pull in every log they appear in — this ignores the pull limit above on purpose.
When it went wrong
Two rough nights and a standing habit produce the same total. The shape over time tells them apart.
Which mechanics they break
Every mechanic this tool can judge, side by side. Caused is provable from the log. Suspected is a deviation from what their own group normally does. Unclear means the mechanic broke and the log does not say who. Click any count to open the exact pulls behind it.
Judged runs lower than the number of pulls you asked for, and differs per mechanic: a pull that wiped in P1 never reached Limit Cut, so there is nothing to judge it on. Only pulls where the mechanic actually happened count.
What the ledger says
Caused only counts breakdowns the log can actually pin on them. When a resolution goes wrong and nothing identifies a cause, it is filed unattributed rather than charged to whoever happened to eat the beam — that number is a limit of the evidence, not an accusation.
How likely are they to break it
An estimate from the pulls listed above only. It is not a full account of anyone’s performance — it does not include their whole history, and a small sample can move these numbers a long way. Treat it as a lead to check, not a verdict.
The register
Caused is what started a breakdown. Caught by is damage that followed from one already underway — once a soak is missed everyone eats a beam, and counting that would rank the victims above whoever caused it.
Pull by pull
Hover an entry for what broke it.