To install addons in WoW Forever, choose a file that explicitly supports Forever, place its real addon folders in the live client's Interface/AddOns directory, fully restart the game and enable the addon. CurseForge can handle the copying and dependencies for you; manual installation gives you direct control over the archive and destination.
The exact live-client folder name is not confirmed here. Find the installation that Battle.net currently launches rather than assuming an old beta, Classic or Retail path is correct.
Before you install
You need the live World of Warcraft: Forever client, the addon's supported release and any required dependencies. If you already have a working interface, back up the relevant files or export the affected addon's profile before replacing it.
Check the download itself. A project page can contain multiple game flavors, and the newest upload is not necessarily the Forever file. Some archives support several flavors at once; that is acceptable when the selected release explicitly includes Forever.
Published files include game-version targets such as 1.60.1. Read the author's current target and notes instead of treating a number from an older tutorial as a permanent compatibility rule.
Method 1: Install with CurseForge
- Install or update the live Forever client through Battle.net.
- Open CurseForge and select World of Warcraft.
- Select the Forever installation in the game or version selector. If it is absent, inspect the available scan or manual-add option and identify the installation through Battle.net.
- Find the exact addon project. Check the author, Forever support and required dependencies.
- Install the supported release into that selected installation.
- Fully close and restart the game after new addon folders have been added.
- Open the AddOns list at character select or through the available in-game menu, then confirm the addon is enabled.
Check the selected game before pressing Install. Having several WoW versions on the same computer makes the destination as important as the package.
A manager can simplify dependency handling, but still read the project's installation notes. Large projects may include optional modules or separate content packs that are not interchangeable with required libraries.
General manager example with WotLK Classic selected. Choose your own Forever installation before installing a file.
Method 2: Install the archive manually
Find the client that you actually launch
In Battle.net, select World of Warcraft: Forever and use the installation-location option beside its launch controls. Open the actual game installation and locate Interface, then AddOns inside that client.
Do not paste a predicted full path into the file manager and assume it belongs to the live game. Beta-era instructions and addon descriptions can retain an older destination. A valid folder for another WoW client will not load files into Forever.
Extract the real addon folders
Download the Forever-supported release and extract it. Inspect the result before copying. The real addon folder contains its .toc file and the accompanying files required by the release.
Copy that folder directly into Interface/AddOns. If the release contains several required addon folders, keep them together as instructed. Install any required companion projects too.
The important relationship is that the actual addon folder sits directly under AddOns. An extra download wrapper around that folder can prevent discovery. For example, a ZIP may extract to an outer folder named after the archive, with the usable addon folder one level inside. Copy the usable folder rather than preserving an unnecessary wrapper.
Do not rename internal folders merely to make their names resemble a tutorial. Dependencies and file references can rely on the package's original structure.
Restart and enable
Fully restart the client after adding new addon folders. A UI reload is useful for some configuration or enabled-selection changes, but a complete restart is the reliable first check after a new manual installation.
Open the AddOns list and check the addon is enabled. If it shows a missing dependency, return to the project's requirements and install the matching companion release. If it is not listed at all, check the game destination and nesting before trying unrelated configuration changes.
Confirm the feature you installed
An enabled checkbox confirms only part of the process. Open the addon's documented settings or window, then perform the task you installed it for.
For a reference addon, inspect a known entry. For an inventory addon, use the relevant bag or bank view. For a UI replacement, check the affected frames during the actions you normally perform. A calm screenshot cannot establish how a combat-related module behaves during a fight.
Add one major change at a time. Once the first addon performs its intended task, introduce the next one. If something stops working, you then have a much smaller set of changes to inspect.
Separate installation errors from compatibility errors
| Symptom | First check | What it tells you |
|---|---|---|
| Addon absent from the list | Correct client and actual addon folder directly under AddOns | The game may not be discovering the files |
| Missing dependency warning | Required companion projects and their supported versions | The main project may be installed without everything it needs |
| Out-of-date warning | Current Forever release and interface target | A label mismatch needs investigation; it does not prove every feature fails |
| Loads, but a function fails | Author's current notes and the exact failing action | Installation may be correct while that feature still needs adaptation |
| Duplicate windows or repeated automatic actions | Overlapping addon modules | More than one project may be handling the same job |
“Load out of date AddOns” can permit a package with an older interface target to load. It cannot rewrite incompatible code or restore information the game does not expose. Use a supported file first instead of treating the checkbox as a porting tool.
If a feature fails, keep the affected addon and its required dependencies enabled while checking the same action. Reintroduce other addons in small groups if the isolated setup works. Save the exact error text for the project's issue report.
Finish with a small acceptance check
Before installing the rest of your collection, write down the outcome you expected from the first addon. Keep it specific: a window opens with the documented command, a chosen option changes the intended behavior, or a known item appears in the relevant inventory search.
Repeat that same action after applying the setting. If the window opens but the expected entry is absent, distinguish missing data from missing installation. A reference database can load correctly while an entry still needs an update. If a second window appears, inspect overlapping modules rather than immediately replacing the archive.
Then close the editor and check the interface in ordinary play. A setting that looks correct while its configuration window is open may be harder to read once other panels, a target or a group are visible. Keep the setup that makes the intended action clearer.
Only move on when you can identify the addon's folder, its enabled state and the feature you just checked. These are separate observations, so one successful check should not stand in for all three.
Preserve your existing settings
Addon files and addon settings are different parts of your setup. Replacing a downloaded folder is not a dependable way to reset or transfer every profile. Use the individual addon's export or backup instructions where available, and preserve a copy of existing settings before changing them.
Beta-to-live migration is a separate task. Do not copy an entire old setup over a working live installation simply to install one addon. Install the current Forever release first, then bring across only the profiles you intend to keep using the project's current instructions.