BlameThrower

Tired of seeing errors in libraries and not knowing which addon actually caused them? BlameThrower walks the stack, skips library frames, and tells you the real culprit.

What it does

When an addon throws a Lua error, BlameThrower captures it — via BugGrabber if you have it installed, otherwise through its own handler — analyzes the message and stack trace, and identifies the application addon responsible, not the library it passed through.

Features

Smart attribution — skips Ace3, LibStub, CallbackHandler, and other known libs to find the real culprit
Grouped view — errors rolled up per addon with counts, severity, and "new" badges
Severity coloring — red / yellow / gray based on count and recency; minimap icon reflects the worst unseen severity
Three-tier mute system — Ignore (drop on capture), Snooze for session, or Snooze forever
One-click disable — right-click any error to disable the offending addon and reload
Session filter — defaults to the current session; flip to All to see persisted history
Minimap button — LibDBIcon, color-coded, pulses on new errors
ElvUI-aware — buttons and scrollbars pick up your ElvUI skin automatically

Slash commands

Command	What it does
`/blame` or `/bt`	Toggle the main frame
`/blame clear`	Wipe errors (keeps BugGrabber's DB)
`/blame clear all`	Wipe everything, including BugGrabber
`/blame clear old`	Keep only current-session errors
`/blame session` / `/blame all`	Filter toggle
`/blame debug`	Print diagnostic state

Optional dependency

BugGrabber — preferred error source, shared with BugSack / Swatter. BlameThrower works standalone without it (falls back to its own error handler).