Reporting a Problem

🐞 Build a report to paste into an issue.

Type /ens report (or Settings > Data > Copy a bug report). It opens the same copyable window with a bug report that starts with three lines to fill in (what happened, what you expected, how to make it happen again), followed by:

• addon version, client build and language, date;
• where you were: open tab, window and text size, the dungeon being checked (and why), your keystone, this week's affixes, whether you're in a group, an instance or hosting a listing, and your spec;
• the planner slots and the last group checked, as specs only (never player names);
• settings changed from the defaults (window position left out);
• how many other addons are loaded, naming any that share the same screens (Raider.IO, Premade Groups Filter, ElvUI, Details, WeakAuras and similar);
• the addon's own recent Lua errors with their first stack lines, how many times each happened, and the version that raised them. The addon keeps its last 10 errors; errors recorded by BugGrabber, if installed, are included too (with BugGrabber installed it handles errors itself, and the report says so when it caught none from this addon);
• the /ens verify summary with up to 12 FAIL and WARN lines.

Nothing is sent anywhere: you copy it and paste it into your report. /ens verify says whether error capture is active in your client.

Note

Nothing is sent anywhere. You copy the report and paste it yourself.

---

← 🩺 Checking Against Your Client · ⚖️ License →