How to report a broken addon in WoW Forever

Patch 1.60Updated Nov 5, 20262 min read

In the first weeks after launch addons update daily and break just as often. A good report gets a fix in a day; “addon broken pls fix” gets nothing. Here is how to find the culprit and what to send.

1. Check that you have the Forever version

Open the addon’s .toc file and look for 16001 in the ## Interface: line or a file with _Camelot or _Forever in its name. If neither is there, the addon has no Forever version and the error is expected; look for a replacement in the catalog or on the page Broken addons. Details are in How to install addons.

2. Update

Update the addon and its libraries. Many first-week errors are already fixed in the next version.

3. Find which addon it is

In the AddOns window (character screen or game menu), click Disable All, then enable only the addon you suspect.
Restart the game and repeat what caused the error.
If the error is gone, enable your other addons in halves until it comes back. The last group you turned on contains the conflict.

4. Capture the error

Install BugSack: it collects errors without popping windows during play, and lets you copy the full text. Without it, turn on the default error window by typing:

/console scriptErrors 1

You need the first error, not the hundred that follow it. It starts with a file name and line number, for example Questie/Modules/QuestieMap.lua:512: attempt to index a nil value, followed by a stack trace.

5. Write the report

Report where the author asks for it, usually the issue tracker or the comments on the addon’s project page. Include:

the addon name and exact version (from the AddOns window or the ## Version: line in the .toc);
that you play WoW Forever, client 1.60.1 and your client language;
the full error text from BugSack;
what you did when it happened, and whether it happens with all other addons disabled.

Check open issues first: someone may have already reported it, and adding your details to the same issue helps more than a new one.

Resetting an addon’s settings

Sometimes the error comes from old saved settings. Close the game and find the addon’s file in:

_forever_\WTF\Account\<ACCOUNT>\SavedVariables\<AddonName>.lua

Move it somewhere as a backup rather than deleting it, then start the game. The addon starts with default settings. Per-character settings are in WTF\Account\<ACCOUNT>\<Realm>\<Character>\SavedVariables.

Do not report it to Blizzard

Blizzard does not support third-party addons. Their bug reports are for errors in the default interface: if the error names a Blizzard_ file and happens with all addons disabled, that one is for Blizzard.

Keep going

Addon catalogWhich popular addons work in Forever, with what to use instead when one does not.ForeverBase addonsOur own addons for Forever: waypoints with an arrow, where an item drops and who sells it, right in its tooltip, and world buff timers shared with your guild.Starter addon packA short list of addons that make leveling easier, all working in Forever.What the game already doesFeatures of the Forever interface that replace common addons.