When an addon fails, check in this order
Check the folder, then the Forever file, then any companion addon.
Still broken? Disable all addons and enable them one at a time.
Check in this order
- FolderInterface\
AddOns inside _forever_ - Forever fileThe file lists Forever as its game version
- Companion addonQuestie also needs QuestieDB
- One at a timeFind the addon causing the error
- UI resetLast resort, back up first
Here you get errors, fixes and Blizzard's rules.
For what to download, see our addon picks.
Everything here was checked on November 10, 2026.
We read official notices and developer files; we did not test in-game.
The folder is Interface\AddOns inside _forever_
Put addons in World of Warcraft\
Where the World of Warcraft folder sits depends on your install.
The folder name comes from CurseForge's guide (October 25, 2026) and WowUp's code.
We found no Blizzard page that names it (checked November 10, 2026).
Addon missing from the list? Look for a doubled folder like Interface\
One folder too many and the game cannot find the addon.
After moving it, fully restart the game and check the AddOns menu.
GitHub source zips can add a branch or version to the folder name.
Rename that folder to the plain addon name, such as Questie.
Files copied from the beta folder _classic_beta_ are not updated by copying.
If you copied them over, update to the Forever files.
Moving beta settings also means renaming the folder in WTF\
Back up live files and settings before you overwrite them.
Why Classic files fail, and what the base UI covers
Classic files can misbehave on Forever, so get the Forever file.
Forever pairs Classic-era content with modern WoW UI APIs.
It also reports Retail's project ID (Questie pull request #7848).
Addons that used that ID to detect the client picked the wrong behavior.
Some called old APIs that were missing or broken.
Questie added Forever detection and API conversion, merged September 23, 2026.
The addon API follows modern WoW (developer Q&A, September 17, 2026).
Try built-in features before you add an addon for the same job.
Forever ships with a damage meter and the Cooldown Manager.
| Feature | What we confirmed |
|---|---|
| Damage meter | September 17, 2026 Q&A: built into Forever |
| Cooldown Manager | November 6, 2026 hotfix: crowd control durations fixed |
| Gamepad UI | November 2, 2026 notes: better addon compatibility |
| Forever-only handling | Questie pull request #7848: detection and API conversion |
From Blizzard's developer Q&A, hotfixes and development notes, and the Questie repository.
A November 6, 2026 hotfix fixed crowd control durations in the Cooldown Manager.
Gamepad UI conflicts with user-made addons were reduced (November 2, 2026 notes).
Setup for those features has its own guides, linked below.
Fix errors by symptom: disable all, enable one at a time
When errors start, disable every addon first.
Log in, then enable addons one at a time from the AddOns menu.
If the error returns, suspect the addon you enabled last.
If one addon keeps failing, leave it off until a new Forever file arrives.
Finding the addon that breaks
- Disable allEverything in the AddOns menu
- Enable oneAfter login, one at a time
- Test itWatch for the error
- Turn off the culpritUntil a new Forever file arrives
When you report a bug, include the full error text and the addon version.
Blizzard's launch notice (November 4, 2026) also says to keep addons updated.
Disabling addons is not the same as a UI reset (Blizzard support, October 21, 2026).
Before a reset, copy the Interface and WTF folders inside _forever_.
Those folders hold your addons and their settings (CurseForge).
For the reset, follow Blizzard's support article Resetting your User Interface.
If the bug also happens with the default UI, post it in Blizzard's Bug Report forum.
| Symptom | Check first | What to do |
|---|---|---|
| Addon missing from the list | Folder location, doubled folder | Move it to AddOns inside _forever_ and restart |
| QuestieDB not installed | QuestieDB is missing | GitHub bundle or QuestieDB Forever file |
| Questie does not load at all | Wrong QuestieDB version | Use the QuestieDB-Forever file |
| CurseForge app shows the wrong list | Game version in the app | Select Forever in the top-right menu |
| Game marks the addon out of date | Is there a new file yet? | Wait for a new Forever file |
| Lua errors after login | The addon you enabled last | Enable addons one at a time |
| Gamepad UI looks wrong | Addon conflict | Disable addons and compare |
| Settings keep resetting | Possible SavedVariables issue | See the settings section below |
Questie errors: check QuestieDB first
Questie needs a separate addon, QuestieDB, to run.
QuestieDB not installed means Questie cannot find that companion addon.
The latest GitHub bundle includes both folders.
A Questie maintainer pointed to that bundle on November 5, 2026.
Copy both the Questie and QuestieDB folders into AddOns.
The CurseForge app should install QuestieDB for you.
If not, check that Forever is selected and install QuestieDB separately.
If Questie does not load at all, the QuestieDB version may be wrong.
Get the QuestieDB-Forever file (a maintainer, November 7, 2026).
Avoid other listings that just add Forever to the name.
A maintainer said on September 20, 2026 they did not know one such uploader.
That is a note about the source, not a claim that the file is malicious.
The latest bundle on November 10, 2026 is v12.6.4+v1.0.12 (November 7 UTC).
Questie updates often, so check for a newer file every time you download.
Questie's work list still has unverified in-game items (edited October 29).
Report errors on Questie's GitHub with the full error text.
Map addons with a Forever file
Every map addon in the table has a Forever file (checked November 10, 2026).
HandyNotes added a Forever-tagged file, v1.6.32, on November 3, 2026.
Check Forever support separately for each HandyNotes plugin.
Mapster's latest file is 1.14.0 from October 3, 2026.
No new Mapster file has appeared since launch, so disable it first on errors.
Leatrix Maps is at 1.60.28-forever (November 6).
Leatrix Plus is at 1.60.29-forever (November 6).
TomTom is at v4.4.1-release (November 7).
The Questie bundle is v12.6.4+v1.0.12 (November 7).
Dates are the UTC upload dates on CurseForge and GitHub.
| Addon | Use | Latest Forever file |
|---|---|---|
| HandyNotes | Map notes | v1.6.32 (November 3) |
| Mapster | Map styling | 1.14.0 (October 3) |
| Leatrix Maps | Map reveal, coordinates | 1.60.28-forever (November 6) |
| Leatrix Plus | Convenience features | 1.60.29-forever (November 6) |
| TomTom | Coordinate waypoints | v4.4.1-release (November 7) |
| Questie | Quests on the map | v12.6.4+v1.0.12 (November 7) |
Checked on CurseForge and GitHub on November 10, 2026. Dates are UTC.
A file listing game version 1.60.1 is tagged for Forever.
We checked the files, not how they run in-game.
“Disable everything before login” was beta advice
We found no live-server instruction to disable addons before every login.
A Questie maintainer wrote that on September 20, 2026 about the beta client.
Back then, logging in with addons on could make them unusable, they warned.
Maintainer replies after launch (November 5 and 7, 2026) do not mention it.
Neither do Blizzard's launch notice or known issues list (November 5).
Log in with your addons on as usual (our take, based on those checks).
If only one character hangs at login, disable all addons and compare.
Then use the one-at-a-time steps above to find the cause.
When settings vanish: not on Blizzard's list
Settings resetting after login is not on Blizzard's known issues list (November 5).
That list is not comprehensive, so absence does not mean it is fixed.
The November 6, 2026 hotfixes have no SavedVariables entry either.
During the beta, a Questie maintainer reported settings not saving (September 20, 2026).
Questie's investigation reproduced the restore failure on beta build 69913.
The beta build 69977 notice (September 22, 2026) listed no settings fix.
Questie's work list parks this as a known beta-client limitation.
That list was last edited October 29, 2026, so it has no live results.
The last post in the related Blizzard thread (September 25, 2026) is a player report.
It says settings were restored on beta build 70009; no staff member replied.
We found no Blizzard confirmation of that report and no live-server result.
After each client update, test whether your settings stay.
To protect important settings, copy the WTF folder inside _forever_.
Are paid addons allowed? Blizzard's addon policy
All addons must be distributed free of charge (UI Add-On Development Policy, rule 1).
The policy dates from March 2009 and is still posted on Blizzard's forums.
The U.S. and EU policy texts matched when we checked on November 10, 2026.
We found no separate addon policy just for Forever.
Rule 1 also bans premium versions with paid features.
Rule 1 also bars charging for downloads or addon-related services.
Rule 2: code must not be hidden or obfuscated and must be publicly viewable.
Rule 3: no function that harms realms or other players.
Rule 4: addons may not advertise goods or services.
Rule 5: no donation requests in-game, only on the website or distribution site.
Rule 6: no material the game's age ratings would not allow.
Rule 7: addons must follow the Terms of Use and EULA.
Rule 8: Blizzard may disable addon functionality at its discretion.
| Policy rule | What it says |
|---|---|
| Free of charge (rule 1) | No premium versions, paid downloads or paid related services |
| Visible code (rule 2) | No hiding or obfuscation |
| No harm (rule 3) | Nothing that harms realms or other players |
| Advertising (rule 4) | No ads for goods or services |
| Donations (rule 5) | Not in-game, website or distribution site only |
| Content (rule 6) | Nothing the game's age ratings would not allow |
| Terms (rule 7) | Follow the Terms of Use and EULA |
| Disabling (rule 8) | Blizzard may disable functions at its discretion |
Our summary of Blizzard's UI Add-On Development Policy (U.S. forums), checked November 10, 2026.
We found no official answer on whether free addons with paid guide files fit rule 1.
That comes from searching Blizzard staff posts on November 10, 2026.
A Customer Support rep said on October 20, 2026 this was outside support's scope.
They pointed to the email address in the policy thread for addon concerns.
An October 24, 2026 reply repeated that and said Blizzard knows its own rules.
Neither reply ruled on whether a specific addon breaks the policy.
We do not judge whether any specific addon or service breaks the rules.
If Blizzard takes a position, we will update this section.
The policy's contact address is WoWUI@blizzard.com.
What to recheck after a patch
Patches can break addons, so run through this list after each one.
| When | What to check |
|---|---|
| Right after a patch |
|
| If something breaks |
|
| Keep an eye on |
|
Files and policy here are as of November 10, 2026.
For what to download, see our addon picks.

