For a missing list entry, check the active client and folder/manifest structure. For an enabled addon with no visible UI, check its documented controls, load errors, and saved position before reinstalling.
Try a ready-made addon
Get a useful starting point before creating your own. These releases passed checks in the ForeverMods preview Lua runtime; test them in your installed game client too.
Forever Checklist
A personal list with four fixed preparation tasks. Tick items, reset the list, and keep your progress after a reload. Progress stays with you; it is not shared with your guild.
Visible on login. Type /foreverchecklist to hide or reopen it.
v1.0.0 · Preview checked 2026-10-19
Installation and folder locations · Help if the addon does not appear
Check the selected game installation
Multiple WoW editions can have separate AddOns directories. Use Battle.net’s installation-folder option for the game you selected, then locate that client’s Interface/AddOns directory. A correctly packaged addon in the wrong client folder will not appear in the client you launch.
Close the game before a fresh installation, copy the addon, and restart it. Use the character selection AddOns menu to confirm the package is present and enabled.
Remove the extra ZIP wrapper folder
The common packaging mistake is an extra folder level. The path should resemble Interface/AddOns/MyNotes/MyNotes.toc, with MyNotes.lua alongside the manifest. Interface/AddOns/MyNotes/MyNotes/MyNotes.toc is one level too deep.
Extract the ZIP into a temporary directory and inspect it before copying. Do not place the ZIP itself inside AddOns and expect the game to unpack it.
Interface/
AddOns/
MyNotes/
MyNotes.toc
MyNotes.luaInspect the TOC manifest and dependencies
Confirm that the TOC is a text file with the expected .toc extension, not .toc.txt. Its file entries must match the packaged Lua filenames. Check the author’s stated client version and any required addon dependencies.
Changing the Interface metadata alone does not update incompatible API calls. An out-of-date label and a runtime compatibility problem are different issues; use the compatibility guide before forcing an old package to load.
If it is enabled but invisible, check its controls
Some addons are intentionally hidden until a slash command or button opens them. Others display a small indicator or background utility rather than a full window. Read the addon’s public description and the generated summary for its intended behavior.
A saved position may be outside your current screen after a resolution change. Use the addon’s documented reset-position control if it has one. Do not delete all saved variables as the first troubleshooting step.
Isolate the first error and retest
Enable the relevant addon with its required dependencies and temporarily disable unrelated addons. Capture the first Lua error through the client’s error-display setting or your established error-reporting tool. Repeat the exact action that caused it.
When asking the creator or the AI for a repair, include the addon version, client build, action, and error text. A browser preview is useful for checking a layout fix, but finish by repeating the failure in game.
- State whether the addon is absent from the list or enabled but invisible.
- Check directory depth and exact filenames.
- Read dependencies and supported-client notes.
- Try the documented command and reset control.
- Retest with only required addons enabled.
- Keep the working version available for rollback.