CurseForge offers addons for WoW Forever, but you need to select the Forever game installation and a release that explicitly includes Forever support. Checking the app's game selector and checking an addon's file are two separate steps. A successful download into another WoW installation will not make that addon appear in Forever.
If you prefer manual downloads, the project website can provide an archive without the desktop manager. The exact live-client directory name is not established here, so identify your installation through Battle.net instead of copying a beta-era path.
Understand the two parts of CurseForge
The CurseForge website contains project descriptions, file lists, images and dependency information. The CurseForge desktop app installs and updates selected addons for an installation on your computer. You can use a project page to assess the file even when the app is doing the downloading.
The game flavor is essential because Forever is separate from modern WoW and Classic. A project can support several flavors through one archive or offer separate files. Both arrangements are possible. What matters is whether the actual file you select includes Forever, rather than whether the project's name sounds familiar.
Select the Forever installation first
- Install or update World of Warcraft: Forever through Battle.net.
- In CurseForge, open World of Warcraft and inspect the selected installation or version.
- Select the Forever installation before searching for addons.
- If the installation is missing, use the available game-scan or manual-add option and identify the location through Battle.net.
- Check the selected destination again before installing your first addon.
App labels can vary with the installed version. If the app does not identify the client clearly, do not choose Retail or Classic as a substitute. Establish the installation location first, then return to the scan or manual selection.
Instructions written during beta sometimes name a beta folder or predict a future live folder. Neither is a reliable reason to redirect the manager away from the installation Battle.net currently launches.
Check the actual file before installation
On the project's file list, look for the Forever flavor and review the compatible game versions, release date and author notes. Published Forever files include targets such as 1.60.1. Use that as context for the published releases, not a rule that every future file must retain that number.
| Check | What you need to establish |
|---|---|
| Exact project and author | You are choosing the intended addon rather than a similarly named fork |
| File flavor | Forever is included in the release you will install |
| Game-version target | The release targets the client version the author documents |
| Dependencies | Required companion projects will be installed too |
| Release notes | The specific feature you need is available and its limitations are understood |
The most recent upload across an entire project is not automatically the correct download. A newer Retail file can sit beside a separate Forever release. Conversely, a multi-flavor release can legitimately list both Forever and another game branch.
Compare concrete release examples
The checked DungeonJournal project lists a Forever release named ForeverDungeonJournal1.6.6.zip, dated November 3, 2026. The separate project called Forever Dungeon Journal has a different identity and a description with planned functions. Matching the first archive's words to the second project's name would therefore lead to the wrong choice.
AtlasLoot Forever provides another useful example. Its listed archive AtlasLoot Forever 1.0.7-181026-11601-11509.zip appears under both Forever and Classic, with game versions including 1.60.1 and 1.15.9. The shared archive is not automatically a mistake: the file listing explicitly includes Forever.
These examples also show why a filename alone is insufficient. Version-like numbers inside a name can describe the author's packaging choices. Read the platform's flavor and game-version fields together with the release notes instead of trying to derive compatibility from one fragment of the filename.
For a later update, repeat the same comparison on the current file list rather than seeking one of these older filenames specifically.
Use project descriptions to choose scope
The Forever catalog includes small visual changes, convenience bundles and full interface replacements. Check the scope before installing a package just because it appears near the top of a search.
Forever Quest Tint focuses on distinguishing quests absent from a stored Vanilla quest list. Its author describes teal quest backgrounds, optional markers and settings opened with /fqt. It does not provide a complete new quest database by itself.
ForeverPlus provides configurable warnings, chat and tooltip options and everyday conveniences. Its author documents /fplus for settings and individual module switches. This is a different choice from replacing all of your unit frames and action bars.
WoW Forever Suite offers optional interface and inventory tools in a settings panel opened with /wfs. Most features start disabled. Its saved inventory and bank information depends on previous visits and recorded data.
ForeverUI is a broad interface suite, with /fui as its main command and modules that can be switched off. Its page lists multiple frame, bar, bag and quest functions. Treat those as author-described capabilities, then check the current release and the modules you intend to use.
Forever Guide by LFYZ concentrates reference information in a window opened with /fguide. Its author describes dungeon quests, items, gear and profession tools. It is not the same project as a similarly named dungeon journal or route guide.
These descriptions help you select a project; they do not certify that every function has been tested on the live client. Choose the smallest scope that addresses your current need.
Install, update and verify
After confirming the installation and file, install the addon and its required dependencies. Then fully restart the game after adding new addon folders. Open the AddOns list at character select or through the available in-game menu and make sure the project is enabled.
Verify a specific function rather than stopping at an enabled checkbox. For example, open the settings command documented by the author, inspect the intended quest display, or open the bag view the addon supplies. If a project loads but a combat-only function fails, the download destination may be correct while the feature still needs an update.
Do not use the “Load out of date AddOns” option as a replacement for file selection. It can allow an older interface target to load, but it cannot adapt code to unavailable game functions.
Check the settings for the feature you installed.
When CurseForge does not show what you expect
The game installation is absent: confirm that Battle.net has installed the live client, then inspect the app's game scan or manual destination. Do not assume an older beta installation is the live game.
An installed addon is not recognized: check the selected game instance before downloading another copy. Copied addons may need a scan of the correct installation's AddOns folder.
An addon appears in the app but not in the game: compare the app's installation with the client you launched. Also inspect archive nesting and dependencies. The game needs the real addon folders rather than an outer download wrapper.
An addon loads but behaves differently: read its Forever-specific notes and update the relevant release. A file label establishes the author's target; it does not guarantee identical behavior to Classic or Retail.
Keep existing settings backed up before replacing a larger setup. Once the manager points at the correct live installation, use it consistently for that installation and review the selected flavor whenever an unfamiliar project or update appears.