Debug what happened, not just where it crashed.
Alluneve-Debug is a lightweight debugging framework for World of Warcraft Retail addon developers. It provides a shared API for structured, severity-based logging, letting you track your addon's behavior without building your own logging infrastructure or flooding your chat window.
Flight Recording
When !BugGrabber captures a Lua error attributable to your addon, Alluneve-Debug automatically submits a report containing 60 seconds of diagnostic history before the error and 10 seconds afterward, by default.
Instead of just a stack trace, you get a timeline of what your addon was doing leading up to the problem.
No Lua error? No problem. You can manually trigger a flight-recorder report through the API or an in-game slash command, making it useful for investigating unexpected behavior, race conditions, and other issues that don't produce errors.
Structured Debug Logging
Log messages with DEBUG, INFO, WARN, and ERROR severity levels. Every registered addon maintains its own independent diagnostic history, with optional chat output.
Session logs are limited to approximately 1 MiB of estimated memory per addon, automatically discarding older messages when necessary.
The underlying paged FIFO storage, single global cleanup ticker, and frame-budgeted cleanup are designed to keep performance overhead low, even during heavy logging.
Requirements
!BugGrabber is required for report submission. BugSack is optional but recommended for viewing reports.
Alluneve-Debug only records diagnostic information supplied by addons that integrate with its API. Automatic error attribution is best-effort.
For Addon Developers
Integration requires only an optional dependency and a simple API registration.
See INSTALLATION.md in the GitHub repository for integration instructions, API documentation, and available slash commands.
Alluneve-Debug Team
