WoW Forever WikiWoW Forever Wiki

Choose a starting point for your addon setup

Start with the part of World of Warcraft: Forever you want to improve. If you need to install a specific project, begin with its Forever-supported file and the installation guide. If your interface already works but feels crowded, review the native UI controls before replacing it. If a feature has stopped working, identify whether the problem is file discovery, a dependency, an overlapping module or the feature itself.

This site organizes addon help around those different tasks. The addon directory helps identify projects; recommendation pages help you choose scope; installation and manager guides handle files and enabled selections. Individual project pages explain the particular addon rather than assuming that every familiar Classic or Retail function transfers unchanged to Forever.

Forever is its own game alongside modern WoW and Classic. Its original-world foundation does not establish addon compatibility. Use a project whose author explicitly includes Forever, then verify the feature you actually need.

Use the interface you already have

A new setup does not have to begin with a full addon pack. Forever includes native interface tools that cover several jobs players previously filled with separate downloads. Trying those controls first gives you a clearer reason for adding anything else.

Open the game menu and inspect Edit Mode. It lets you position supported HUD elements and adjust their available controls. Arrange your own health and resources, target information and action buttons before adding secondary panels. A readable layout is easier to maintain than one built around every possible display.

For inventory, try Combine Bags if one window is your main requirement. A dedicated bag addon becomes a more distinct choice when you want categories, richer searches or recorded items across characters. Reorganizing the display does not increase the number of items your bags can carry.

The native damage meter can show damage, healing and several other encounter metrics. It can be moved with Edit Mode, and additional windows can show different information. Check which view and segment you are reading before comparing numbers: an overall record and one current fight answer different questions.

Also inspect the available cooldown, nameplate, mouseover and click-casting controls. Options search can help you find a feature when categories differ from an older tutorial. Choose an addon after identifying the specific presentation or function you still want.

Choose a tool by its actual job

Several projects can mention the same activity without solving the same problem. Quest locations, guided routes, quest narration and identifying new quests are separate choices. Installing one does not establish that it provides the others.

Questie adds available-quest information and other quest data to the map. Forever already provides guidance for accepted quests, so compare the additional information with the amount of exploration you want. Database gaps can remain for new or changed quests. A missing marker does not necessarily mean the quest itself is unavailable.

Forever Quest Tint is a narrower visual tool. Its author describes a teal treatment and markers for quests absent from a stored Vanilla quest-ID list. That can help distinguish content while you read, but the list can have omissions. Treat the color as an indicator rather than conclusive proof of a quest's history.

For dungeon preparation, distinguish reference information from live encounter warnings. DungeonJournal describes quests, rewards, boss drops and quest locations in an in-game window. That is different from a boss-warning system, and its database still needs updates when rewards change.

Similarly, a broad reference project such as Forever Guide by LFYZ combines several information tools. Decide whether that wider scope is useful to you before adding multiple databases that repeat the same entries.

Check the project identity before downloading

Names are not unique enough to choose an archive by themselves. Match the author, project description and exact release. This is especially important for forks and projects whose names differ by only one word.

DungeonJournal and Forever Dungeon Journal are separate projects. The former documents the command /dj and a Forever quest-and-loot reference. The latter describes a spoiler-light discovery journal and labels many functions as planned. A promising description of future features is not a confirmation that those functions are already finished.

ForeverAuras also needs context. Neroxrw's standalone project is a WeakAuras fork with its own Forever release and commands. ForeverUI uses the same name for an aura module within its suite. Do not assume their profiles, imports or instructions are interchangeable because the labels match.

Once you have the right project, inspect the release's Forever flavor, compatible game versions, date and dependencies. A single archive can legitimately support several WoW flavors. A separate Forever archive is also possible. The meaningful check is whether the actual file includes Forever support, rather than whether its filename follows one expected pattern.

Published files in the current material include targets such as 1.60.1. Treat those as the authors' release targets, not a permanent rule for every later game update. A file label also does not establish that all modules have been independently tested in the live client.

Install into the client that Battle.net launches

Use the installation guide when you have selected a project and need it to appear in game. The destination matters as much as the archive. An addon installed into another WoW client will not become available in Forever just because both clients share part of the same parent folder.

A desktop manager can handle downloading, placement and required dependencies. Select the live Forever installation before searching or installing. If the app does not list it clearly, identify the installation through Battle.net and inspect the manager's scan or manual-add controls.

For a manual installation, extract the supported archive and identify the real addon folders. Each usable folder contains its manifest and accompanying files. Those folders belong directly under the current client's Interface/AddOns directory; an extra outer download wrapper can prevent discovery.

This guide does not establish a fixed live-client directory name. Instructions written during beta can retain old paths or predictions about launch. Find the current installation through Battle.net rather than copying an unverified full path.

Fully restart the game after adding new addon folders, then inspect the AddOns list and any dependency warnings. Loading the project is the first check. Opening its intended window and using the feature you installed it for is the next one.

Separate file updates from addon profiles

A desktop addon manager and an in-game selection manager work on different parts of the setup. Understanding the difference avoids expecting one tool to fix a problem outside its scope.

CurseForge provides a desktop route for supported downloads and updates. The selected game installation and selected release flavor both matter. WowUp is another desktop manager with multiple providers and installation scanning, but its general features do not by themselves establish how a particular installed version recognizes the live Forever client. Check the current recognition and provider before relying on historical beta instructions.

ForeverAddonManager is an in-game project for combinations of enabled and disabled addons. Its author describes account-wide selection profiles, character assignments and optional application at login. It does not download files or copy another addon's layouts, keybindings or internal configuration.

For example, two characters can use the same enabled selection while keeping different layouts inside a UI suite. If the list of loaded addons is correct but the frames differ, inspect the suite's own profile settings. Reapplying an enabled-addon selection does not transfer that visual profile.

Keep required dependencies with the projects that need them. A saved selection cannot load files that are absent, and a successful download cannot decide which configuration you want on every character.

Give each interface function one owner

Convenience bundles and full UI suites can overlap with both native features and other addons. Before enabling a second tool, check who already handles that element or action.

ForeverPlus describes optional conveniences, warnings, chat and tooltip adjustments. WoW Forever Suite combines optional interface, inventory, training and everyday tools, with most features initially disabled. ForeverUI is broader, covering frames, bars, nameplates, bags and other modules. These are different scopes rather than automatic steps in one required progression.

If you choose a suite, decide which modules to retain. Avoid enabling multiple replacements for the same bars or frames unless you have confirmed the intended combination. For automatic repairs, junk selling or quest interactions, choose the behavior you want and give that action one owner.

Recorded information also needs context. An offline inventory or bank view reflects previous observations, not a live connection to a character you are not playing. Profile exports may exclude character records or history. Read what an export contains before treating it as a complete backup.

Follow the symptom when something fails

If an addon is absent from the AddOns list, inspect the active client, destination and archive nesting first. If the list reports a missing dependency, check the required companion project and its supported release. Neither symptom calls for deleting every saved setting.

If an addon loads but one function fails, update the Forever release and read its current limitations. Then repeat the same action with only the affected project and its required dependencies enabled. If that works, reintroduce other addons in small groups to locate an overlap.

An out-of-date loading option can bypass an interface-target warning. It cannot rewrite incompatible code or restore combat information the game does not expose. An old Classic import may therefore need adaptation even when part of its display appears correctly.

Keep the exact error text and the steps that produced it. Back up an existing configuration before replacing files or changing saved settings. Once the intended function works, save that setup and add the next significant change separately. This makes the next update or fault easier to understand without rebuilding your whole interface.