Getting started with addons
How to install addons for WoW: Forever, what “out of date” means and how to see error messages. No extra software needed.
Installing addons is easier than it looks. All you need is the right folder and a few minutes. Note that WoW: Forever runs in its own folder, separate from retail and Classic.
Installing addons
1. Find the game folder
Open the Battle.net launcher and select WoW: Forever. Use the cog next to the Play button to open the game folder in Finder or Explorer.
Inside that folder there is a subfolder Interface and inside it AddOns. If they do not exist yet,
simply create them. Mind the spelling with a capital A and O.
2. Download and unzip the addon
Download the addon from CurseForge or Wago. You get a ZIP file. Unzip it and drag the folder inside into
Interface/AddOns.
Important: a
.tocfile has to sit directly inside the addon folder. If it is one level deeper, the game will not find the addon.
3. Enable it in game
Start the game. On the character selection screen you will find the AddOns button in the bottom left. Tick
the new addon there. For new addons a full restart is needed, a /reload is not enough.
What “out of date” means
Every addon tells the game in its .toc file which version it was built for. This number is called the interface
number. If it does not match the current game version, the game marks the addon as out of date and does not load it.
In the AddOn list on the character selection screen there is a checkbox Load out of date AddOns. With it, the game also starts addons with an older interface number. That often works fine. If the game changed something the addon relies on, you will see errors and only an update helps.
We update our addons after every patch. The changelog of each addon shows which version it was last tested with.
Showing error messages
When an addon does not do what it should, there is usually a Lua error behind it. The game hides these errors by default. Type this into the chat:
/console scriptErrors 1 From now on a window appears whenever an addon throws an error. /console scriptErrors 0 turns it off again.
If you want to report a bug, these three things help us most:
- the text from the error window, ideally copied rather than typed
- the version of the addon
- what you were doing when the error appeared
Sometimes the exact interface number helps too. This command shows it:
/dump select(4, GetBuildInfo()) Still stuck?
Have a look at the frequently asked questions or ask in our Discord. English is welcome there.