Make a Forever Addon Work

Yes: start by identifying what fails. An addon missing from the list, a dependency error, a broken quest marker and a feature that stops during combat require different checks. Downloading an arbitrary Classic file or changing an interface number cannot establish Forever compatibility.

Use the author's release that explicitly includes Forever, preserve your settings, and test the problem with the smallest relevant addon set. A published Forever file establishes the author's target; it does not guarantee that every module, imported profile or database entry works after a client update.

Describe one reproducible symptom

Before changing files, write down the action that fails and what you expected to happen. “My addon does not work” could mean that it never loaded, that its options did not open, or that a particular calculation was blocked during a fight.

Use a concrete description such as:

• The addon is absent from the character's AddOns list after a full restart.
• It is listed but reports a missing dependency.
• Its main window opens, but one quest has no objective marker.
• Its layout works alone but overlaps another UI replacement.
• A button works outside combat and shows an error during combat.
• Settings change in the current session but appear different after the next login.

These observations establish a starting point. They do not, by themselves, identify whether the addon, another addon or the client caused the failure.

If the addon is absent, check files before settings

An addon that the client never finds is a file-location problem to investigate before a profile problem.

1. Confirm that Battle.net is set to the Forever installation you actually launch.
2. Locate that selected client and open its Interface/AddOns directory.
3. Check that the extracted addon folder sits directly inside AddOns.
4. Open the addon folder and check for its .toc file or the documented version-specific .toc files.
5. Remove an accidental extra ZIP-name wrapper by placing the actual addon folder at the documented level.
6. Restart the client after adding the files and inspect the AddOns list again.

Author source-file example showing TOC files. This is not the live client root directory or an installed AddOns folder.

Do not assume the current live root directory has the name printed in a beta tutorial. The stable part of the check is the selected client and its Interface/AddOns structure. It is possible to install a perfectly extracted addon into the wrong WoW installation.

Some downloads contain several folders because the project ships modules or libraries separately. Keep the components the author provides and check declared dependencies before discarding folders that look unfamiliar.

If it is listed, verify the release and dependencies

Check the exact file's game flavors and release notes. A project name appearing in a search result does not tell you which file you downloaded. A multi-flavor file may explicitly include Forever, so a separate Forever-only ZIP is not required in every case.

The November 2026 author/distribution examples include Forever targets labeled 1.60.1 and interface 16001. Those examples help distinguish branches; they are not a permanent number to force into every addon file. Use the project’s current declaration and your actual client context.

An “out of date” label reports an interface-version mismatch. Allowing outdated addons may help you inspect a known project, but it does not rewrite unsupported APIs, update quest data or restore missing combat access. Changing the .toc number solely to remove the label has the same limitation.

If the list reports a dependency, install the dependency identified by that project's documentation and check its own version support. Then restart. Do not substitute another similarly named library because a general guide happens to mention it.

If the window opens, test the specific feature

Once the main window opens, stop treating every failure as a failed installation. Test the operation that matters to you.

For a quest helper, inspect one accepted quest, its location-source label and current objective. Legacy quest coordinates or an incomplete new-quest database can explain a missing marker even while the tracker itself is functioning.

For a UI replacement, check whether the affected frame is provided by the addon or by another suite. A package can load correctly while a competing addon moves, hides or replaces the same frame.

For a meter, distinguish a blank window from a documented combat restriction. ForeverMeter's author describes some comparisons becoming available only after combat and some enemy threat information remaining hidden. Repeatedly reinstalling the same build will not make intentionally unavailable information appear.

This test should answer a narrow question: does the addon perform its documented job in this situation? It should not require a wholesale interface rebuild.

Isolate a conflict without deleting your setup

A conflict becomes easier to identify when you change one variable at a time.

1. Back up the selected client's addon settings before resetting or replacing them.
2. Disable other addons that replace the same tracker, frame, bag window or meter.
3. Keep the problem addon and its documented dependencies enabled.
4. Restart or reload as appropriate, then repeat the same action.
5. If it works, enable the overlapping addons individually and repeat the action after each change.
6. Keep a note of the smallest combination that reproduces the problem.

For ForeverUI, the author provides a module switch for each component under /fui and a text backup through /fui backup. If you are diagnosing one of its modules, switching off overlapping modules can be more informative than installing a second full UI package.

A symptom disappearing with every addon disabled confirms that the default interface behaves differently. It does not yet prove which addon caused the original problem. Re-enable the relevant components until the relationship is reproducible.

Capture the error instead of guessing from its last line

If you receive a Lua error, keep the complete message and the action that produced it. An author can use the full trace to locate the failing code; a shortened description can omit the important call.

The documented WoW command /console scriptErrors 1 enables visible Lua errors, and /console scriptErrors 0 disables those popups again. Error-capture tools such as BugGrabber and BugSack are another option when their current files explicitly support your client.

A message mentioning arithmetic on a secret value points toward an addon trying to calculate with restricted information. An ADDON_ACTION_FORBIDDEN message indicates a blocked action to investigate with the author. Neither message is a reason to download a package promising to remove the client restriction.

When reporting, include the addon version, client context, full error text, reproduction steps and the smallest addon combination that still fails. If a suite offers a diagnostic command, include that output too. ForeverUI documents /fui errors; ForeverQuest documents /fq debug for its own problems.

Treat old beta workarounds as historical

Do not assume that a beta-era settings problem is present in the live client. Published pages can retain old warnings after a fix, and a report from September does not establish your current November failure.

If settings appear to reset, verify the character, account and selected addon profile first. Make an identifiable setting change, leave the game normally, then inspect the same profile on the next login. A crash or forced quit is different from a normal exit when determining whether a session's changes were written.

Preserve the old settings before removing a workaround or trying a clean profile. Do not copy an entire beta configuration over a live setup merely because a forum reply describes it as a fix. That can overwrite the very state you need to compare.

Know when a port needs the author

A port is more than editing an interface label. UI function names, protected actions, combat information and data coverage can all differ. If the project has no declared Forever support, ask whether the author maintains a Forever branch or recommends an alternative.

The useful handoff is small and reproducible: “this version, this character action, this error, these dependencies.” If the required feature relies on data that the client does not provide, the resolution may be a redesigned feature or a different workflow rather than a setting you can toggle.