WoW Forever Addons: Journey, WeakAuras & DBM

WoW Forever supports an addon environment, but Blizzard plans to restrict the kinds of in-combat computational addons that can automate calculations, marking, or player communication. Blizzard's UI team has also clarified that Forever uses Mainline WoW's UI architecture, including the vast majority of APIs available in 12.1.5, rather than simply reusing the current Classic addon environment.

That distinction matters for searches around WeakAuras, DBM, Classic addons, damage meters, UI addons, healing tools, and quest addons: compatibility should be tested by feature, not assumed from the addon name alone.

Native gamepad support and Steam Deck setup belong on Controller & Steam Deck Support. This page stays canonical for addon compatibility, UI APIs, WeakAuras, DBM, and combat restrictions.

Journey addon: free guide, downloads and limits

Journey is a leveling-route addon, not a requirement to play Forever. Its maintainer offers levels 1-30 free and links to CurseForge and Wago downloads. Use those links rather than a similarly named addon or a repackaged installer.

The guide's coverage notice distinguishes the paid 1-60 guide from completed Forever-specific content: levels 30-60 begin with a Classic route, with new Forever content planned after launch. Do not read that as a verified full Forever speed-leveling route.

The support instructions use /journey and say to install the addon in the release client separately. They describe intended coexistence with Questie, not our compatibility test. Journey supplies an ordered route; the Questie guide covers quest tracking. Neither is required for our beta leveling reference.

We have not tested Journey in the release client or verified every route. Maintainer statements are not Blizzard endorsement or a guarantee about account enforcement. Installing it cannot reopen the closed beta. Keep the backup precautions below when switching clients.

What Blizzard has actually said about WoW Forever addons

In a post-BlizzCon interview with Kotaku, lead Classic designer Tim Jones and lead encounter designer Mike Nuthals discussed Forever's addon direction. Nuthals said the team is bringing over the in-combat "addon disarmament" approach used by modern WoW so players do not have access to computational addons that automate marking or communication during encounters.

The confirmed point is therefore restricted in-combat computation, not a blanket removal of the addon system.

Blizzard's UI team later provided a more technical clarification: Forever shares the Mainline WoW UI architecture, uses the vast majority of APIs available in 12.1.5, and will also use the addon-disarmament changes introduced in Midnight.

The September 17 live Q&A reinforced this direction: Blizzard said Forever uses the Modern client API and that unifying the API with modern WoW should make addon support easier to maintain.

What addon API does WoW Forever use?

Blizzard's UI team says Forever and modern WoW are both part of the Mainline code family from a UI-loading perspective. The currently confirmed pieces include:

• the vast majority of Mainline WoW 12.1.5 APIs;
• Midnight's addon disarmament rules;
• secret values / secrets used to protect combat information from automation;
• the AuraContainer / AuraButton changes introduced in 12.1.0;
• similar future UI changes being introduced to both modern WoW and Forever when appropriate.

This means a current Classic addon should not be assumed to work unchanged in Forever. Many Classic addons may need adaptation to the Mainline-style API, while some modern-WoW addons may have an easier technical path to a Forever-compatible version.

Blizzard has not supplied a final compatibility matrix for every addon here. With beta closed, any unverified feature remains pending release-client evidence.

Will WeakAuras work in WoW Forever?

Do not treat "WeakAuras is banned" as a confirmed blanket statement. WeakAuras can do many different things, from simple UI display to encounter logic that depends on protected combat information.

The safer current answer is:

• simple display or out-of-combat functionality may remain possible;
• computational or automated in-combat behavior can be restricted by the API and secret-value system;
• existing Classic auras cannot be assumed to work unchanged;
• individual auras may behave differently depending on which data they need;
• beta testing is required before publishing a reliable compatibility list.

This page will separate addon loads successfully from all of its combat features work, because those are not the same claim.

Will DBM work in WoW Forever?

Blizzard has not announced a simple yes/no rule for DBM by name. Encounter addons can contain both ordinary UI features and combat logic affected by protected APIs.

Until the beta client and addon authors document the actual behavior, the useful questions are more specific:

• Does the addon load without errors?
• Which boss timers can use available events?
• Can it mark targets automatically?
• Can it coordinate or calculate information during combat?
• Which features are disabled or degraded by the same restrictions used in modern WoW?

We will update this page with verified behavior rather than labeling an entire addon compatible or incompatible from an interview headline.

What types of addons need testing first?

The highest-value beta checks are:

Addon category	What to verify
WeakAuras / combat alerts	Which combat data, secret values and automated calculations are protected
Boss mods such as DBM	Timers, automated marking, encounter communication, warnings
Damage meters	Combat-log access, pet attribution, interrupts, live calculations
Healing / raid-frame tools	Click-casting, mouseover behavior, protected unit information
UI / action-bar addons	Layout changes and any restrictions that appear only in combat
Quest / map addons	Map data, quest data, waypoint behavior and any protected APIs
Existing Classic addons	Whether they load under the Mainline-style Forever UI architecture and what must be updated

A feature working in the launcher or character select screen does not prove it works unchanged during combat.

Addon verification checklist after beta

The beta is closed. Keep this protocol for when the release client is accessible; do not infer compatibility from an archived beta result or import a full Classic folder blindly:

1. install one addon at a time;
2. record its version and whether it explicitly supports Forever;
3. test out-of-combat UI first;
4. test the same feature after entering combat;
5. note Lua errors, secret values, or unavailable APIs;
6. separate cosmetic failures from gameplay-data restrictions;
7. re-test after client patches because API rules can change.

The WoW Forever Beta guide preserves the completed test window and historical access routes.

Will beta addons and settings carry over to release?

Do not assume an automatic transfer. Back up before uninstalling Beta, then check each addon's release instructions. Players are asking whether their beta layouts will survive, but those community discussions are not a verified Forever migration specification. We have not tested a beta-to-release restore in a local client.

Addon files and saved settings are different:

What to preserve	What it generally contains	What it does not prove
Interface/AddOns inside the selected game installation	Installed addon files and versions	That the same version supports the release client
WTF in that installation, including relevant SavedVariables	Local configuration and addon data, which may be account-wide or character-specific	That every setting, keybind or profile can be restored unchanged
An addon's own profile export, if it offers one	A profile in the format supported by that addon	Compatibility with another addon version or game branch

Back up before removing the beta

1. Exit WoW normally so settings can be saved, then fully close the game and launcher before copying files.
2. Identify the actual Beta installation folder in Battle.net. Do not assume that Retail, Classic, Stress Test and Forever all use the same folder.
3. Copy, rather than move or delete, Interface/AddOns and WTF into a separate dated backup outside the installation. If an addon supports profile exports, save those too.
4. Keep the source files untouched. Record the addon versions and which account or character used each profile; keep account labels and backup contents private.

Copying only Interface/AddOns is not a backup of the addon's saved configuration. An addon manager reinstalling the addon files is not, by itself, proof that your settings were backed up.

Restore cautiously when the release client is available

1. Follow the client-selection checklist to identify Forever. Launch it when access is available, then close it and back up its fresh settings as well.
2. Install an addon version whose maintainer explicitly supports Forever. For Questie, use the separate Forever installation guide, not an assumed Classic build.
3. Prefer the addon's documented profile import. If its maintainer instead documents a SavedVariables restore, restore only the relevant files to the matching account or character location with WoW closed.
4. Test one addon first, outside combat and in combat. If it fails, return to your clean release backup before trying another change.

Do not overwrite the entire release WTF folder blindly. Account and character paths, saved-data formats and protected APIs can differ. A local backup does not carry over beta characters, levels, names, items or access rights; it also cannot bypass combat restrictions. Keep an untouched backup until the required settings work. Never upload it publicly or run an unknown “migration tool.”

What we are not claiming yet

We are not publishing a "best WoW Forever addons" list yet. A recommendation page would be premature until compatibility can be reproduced in the beta client.

Search demand and a dedicated Forever build now justify one narrower page: Questie for WoW Forever. This URL remains canonical for the broad WoW Forever addons intent, while the Questie page covers download, installation and Questie-specific limitations. WeakAuras, DBM, Details and other addons stay here until they develop a distinct verified search intent.

Beta note: addon restrictions can change during testing. This page distinguishes developer-confirmed policy and UI architecture from addon-specific behavior that still needs direct verification.

Sources

• Questie maintainers — addon installation guide

• Player discussion — beta addon settings and migration uncertainty

• Wowhead — World of Warcraft September 17 Live Q&A liveblog

• Kotaku — 8 New Things We Learned About World of Warcraft: Forever

• GamesRadar — WoW Forever takes page out of retail's book as Blizzard confirms addon restrictions

• Wowhead — WoW Forever Will Have Addon Changes from Midnight

Backup guidance reviewed October 22, 2026. The checklist is a cautious local-file workflow, not a Blizzard guarantee that beta profiles will work in release.