WoW Forever Beta CurseForge Addon Directory Path Configuration Guide

There is something oddly exciting about setting up addons for a brand-new World of Warcraft client. It is one of those small rituals that longtime players know too well: install the game, stare at the folders for a few minutes, wonder why CurseForge cannot find anything, and then spend more time fixing the interface than actually playing. With the upcoming WoW Forever Beta, that familiar process becomes especially important because this is a separate client with its own files, settings, and addon directory.

According to the information in the original guide, the WoW Forever Closed Beta is scheduled to begin on September 17, 2026, ahead of the planned November 4 launch. Players jumping into the test build will likely want their favorite tools ready immediately, whether that means damage meters, raid utilities, unit frames, WeakAuras, or simple quality-of-life addons. The problem is that a new client does not always get recognized by addon managers automatically.

That is where CurseForge directory configuration becomes useful. If the application cannot identify the WoW Forever Beta installation, it may install addons into the wrong version of World of Warcraft—or simply refuse to install them at all. Fortunately, once you understand how the game’s folders are organized, fixing the problem is fairly straightforward.

Warcraft 3 Reforged Forsaken Kingdom Campaign Link & WoW Forever Guide

Why WoW Forever Beta May Need a Separate Addon Path

World of Warcraft has never really been just one installation from the perspective of its files. Blizzard’s launcher traditionally separates different versions of the game into individual directories while keeping them under the same main World of Warcraft folder.

If you have played multiple versions of WoW, you have probably already seen folders such as _retail_ for the current main game client, _classic_era_ for Classic Era files, and _ptr_ for Public Test Realm data. The source material for this guide also describes a separate _forever_beta_ or _classic_forever_beta_ directory for the upcoming test client.

The important thing to remember is that your addons need to follow the active client, not simply the main World of Warcraft installation. Putting an addon into the wrong version’s Interface folder will not make it magically appear in the beta.

Typical Installation Locations

From there, you need to locate the folder belonging specifically to the WoW Forever Beta. One thing I would strongly recommend is not blindly trusting a folder name from an old guide. New Blizzard clients can change their internal directory names during testing, so always look at the folder actually created by your Battle.net installation. The principle is more important than memorizing one exact name.

How to Point CurseForge to WoW Forever Beta

CurseForge normally tries to detect installed games automatically, and for established versions of WoW this usually works pretty well. The trouble starts when a completely new branch appears. A beta client may not yet be recognized correctly, leaving CurseForge without a usable installation path.

If that happens, the easiest solution is to add the game directory manually. The interface can change slightly between CurseForge versions, but the basic process remains the same: find the game’s settings, locate the manual game configuration option, and point it at the correct beta directory.

Step 1: Open CurseForge

Launch the CurseForge desktop application and open its main dashboard. Make sure you are using the desktop client rather than simply downloading addons through the CurseForge website.

Step 2: Open Settings

Look for the gear icon to open CurseForge settings. From there, find the section dedicated to World of Warcraft or game-specific settings.

Step 3: Find the WoW Installation Settings

CurseForge should show the World of Warcraft installations it currently knows about. If the Forever Beta is missing, look for an option such as Scan for Games, Locate Game, or Manually Add Game.

The exact wording can vary between CurseForge versions, so do not worry if your interface does not use precisely the same label. You are looking for the function that lets you manually specify where the game client is installed.

Step 4: Browse to the Beta Folder

Use the file browser to navigate to your World of Warcraft installation. You should then see the individual client directories.

The critical part is selecting the actual WoW Forever Beta directory rather than the general World of Warcraft parent folder. If several WoW versions are installed, take a moment to verify which folder contains the beta client before confirming the location.

Step 5: Select the Folder, Not Wow.exe

This is probably the easiest mistake to make. CurseForge needs the directory containing the game installation, not the executable itself. Do not click Wow.exe and expect CurseForge to figure everything out.

Instead, select the beta’s folder and confirm it. Once CurseForge accepts the location, the beta installation should become available as a separate WoW profile or game version inside the application.

Where the Addons Actually Go

After CurseForge recognizes the correct installation, the addon destination should ultimately be the beta client’s Interface\AddOns directory.

On Windows, that will generally look like C:\Program Files (x86)\World of Warcraft\_forever_beta_\Interface\AddOns\. On macOS, the equivalent structure is /Applications/World of Warcraft/_forever_beta_/Interface/AddOns/.

Again, the exact beta folder name may differ in the final client, so treat these paths as an example of the structure rather than something you should manually create without checking your installation. The important hierarchy is simply WoW Forever Beta → Interface → AddOns.

CurseForge Installation vs Manual Addons

Once everything is configured properly, installing an addon through CurseForge should be relatively painless. The application downloads the archive, extracts it, and places the addon folder inside the correct AddOns directory.

Manual installation is also possible, and honestly, it is still useful to understand how it works. Download the addon archive, extract it, and move the resulting addon folder into the beta’s Interface\AddOns directory.

The most common manual-installation mistake is creating an extra folder level. For example, AddOns\Details\Details\Details.toc is usually wrong, while AddOns\Details\Details.toc is the structure you want. The .toc file should normally be located inside the primary addon directory, so if you open an addon folder and immediately see another folder with the same name before reaching the .toc file, you may have extracted it one level too deep.

What If the Addon Button Does Not Appear?

This is one of the easiest ways to diagnose a bad installation path. At the character-selection screen, World of Warcraft normally provides an AddOns button when it has detected addons for that client. If the button is missing entirely, the first thing I would check is the folder path.

Do not immediately assume the addon itself is broken. You may have installed it into _retail_ while the beta is reading _forever_beta_, or perhaps CurseForge is still pointing toward Classic Era. When you have several WoW versions installed, these mistakes become surprisingly easy to make.

Quick Addon Detection Checklist

• Confirm you are launching the WoW Forever Beta client.
• Check which folder contains that client’s Interface directory.
• Open Interface\AddOns.
• Confirm the addon folder is inside that directory.
• Restart the game after making changes.
• Check the AddOns button at character selection.

This simple checklist can save a ridiculous amount of time. In my experience with WoW addon troubleshooting, checking the path first is almost always smarter than immediately reinstalling everything.

Dealing With Out-of-Date Addons

A new beta creates another headache: addon compatibility. Even if an addon is installed in exactly the right place, it may not be officially updated for the beta yet. A new client can change APIs, interface behavior, class systems, and other mechanics that addons depend on.

The in-game AddOns menu includes an option to Load out of date AddOns. Enabling it can allow older addons to load despite their version metadata.

However, there is an important distinction here: loading an outdated addon does not magically make it compatible. An addon might work perfectly, work partially, or completely break. For a beta, I would expect some experimentation, and if a UI suddenly starts throwing errors after installing an addon, disable it first rather than assuming the entire client is responsible.

Can You Transfer Your Existing WoW UI?

Absolutely—and this is where things get interesting for players who have spent years building a personalized interface. WoW stores a lot of local configuration information inside the WTF folder. Depending on the addon, this can include saved settings, profiles, macros, layouts, and other interface data.

If you already have a carefully tuned Classic or Retail interface, you can make a backup of the relevant WTF data and transfer it to the beta installation. The basic process is Existing WoW Client → WTF → Copy Data → WoW Forever Beta → WTF.

I would strongly recommend making a backup before doing this. Beta clients are exactly the kind of environment where you do not want to accidentally overwrite a UI setup you have spent months building.

Be Careful With SavedVariables

The WTF folder contains more than just a single universal UI configuration. Addons commonly store their settings inside SavedVariables, with data associated with accounts, realms, and characters.

That means copying the entire folder can sometimes result in a setup that is only partially recognized by the beta. Character names, realm names, addon versions, and internal configuration structures can all differ between clients.

For addons that provide their own import/export systems, I actually prefer using those tools. ElvUI profiles, WeakAuras strings, and similar configuration systems can be much cleaner than dragging an entire WTF folder from one version of WoW into another. It takes a few extra minutes, but it also gives you more control over what you are bringing into the new client.

My Recommended WoW Forever Beta Setup

If I were preparing a fresh WoW client for beta testing, I would not install 100 addons on day one. That is just asking for troubleshooting chaos. I would start with a small core setup and expand it once I knew the beta client was stable.

• Damage meter for combat testing.
• Unit frames if the default UI is not enough.
• Boss or encounter tools where compatible.
• WeakAuras if the beta supports the required version.
• A few quality-of-life addons that I genuinely use.
• Nothing experimental until I know the basic interface is stable.

Then I would add addons one at a time. This approach makes it much easier to identify the culprit when something breaks. If you install fifteen addons simultaneously and the interface starts throwing Lua errors, congratulations—you have created your own debugging raid boss.

Final Thoughts

Setting up CurseForge for the WoW Forever Beta should not be complicated, but a brand-new World of Warcraft branch can make familiar addon-management routines surprisingly confusing. The biggest thing to understand is that the beta is treated as its own client, which means its Interface\AddOns and WTF directories need to be associated with that specific installation.

If CurseForge does not automatically detect the beta, manually point it toward the beta game folder, not Wow.exe and not another version of World of Warcraft. Then verify that your addons are actually sitting inside that client’s Interface\AddOns directory.

Personally, I would do all of this before the first serious beta session. There is nothing worse than finally getting into a new WoW build, finding the perfect character setup, and then spending the first hour wondering why your entire UI disappeared. A little folder housekeeping beforehand means you can get straight to the fun part: exploring Azeroth, testing the new systems, and figuring out whether WoW Forever actually feels like the kind of classic-era reinvention we have been waiting for.