WoW Forever UI Guide: Classic UI Addon, Import and Setup
How to set up your WoW Forever UI: whether the Classic UI addon works, how to import UI profiles, and fixes for addons that will not save after beta patches.
FAQ
Why do my addons not save settings in the WoW Forever beta?
Does the Classic UI addon work in WoW Forever?
Is there a WeakAuras alternative for WoW Forever?
How do I install addons in WoW Forever?
How do you set up your UI in WoW Forever?
Start with the new base HUD: the launch client ships a customizable interface that can be tuned toward the Classic look without any addons, including hiding elements and moving the experience bar. Addons come second — CurseForge carries a growing “Forever” catalog, and community lists confirm which established addons already run on the beta client. The one landmine is settings persistence: a Blizzard-side bug currently stops many addons from saving anything, which this guide untangles before it eats an evening of your setup time.
Why won’t my addons save settings?
Because of a Blizzard-side SavedVariables bug, not your addons. The beta client currently prevents many established addons — Platynator, EQoL, MSUF and others — from writing their saved settings at all, and profile import/export fails along with it. Addon authors cannot patch around it from their side, which is why the r/WowUI PSA thread tells players to stop reconfiguring and wait. The bug also affects parts of the default UI’s persistence, so a fresh install will not help.
The interim workaround is ForeverSVFix, a small community addon on GitHub that restores settings saving while Blizzard works on the real fix. Two practical notes from the same threads: reinstalling or replacing a misbehaving addon will not fix a Blizzard-side write failure, and anything you configure without the fix may need redoing once the official patch lands.
FIX WoW Forever Settings NOW — community beta walkthrough
Which addons already work in the beta?
The community working list from r/WowUI (300+ comments and growing) divides into addons that run as-is, addons that run with rough edges, and addons still missing. The confirmed-working shortlist:
| Addon | What it does |
|---|---|
| ClassicUiForever | Restores the whole Classic interface |
| BetterBlizzFrames | Advanced unit-frame customization |
| UnitFramesImproved | Classic-style unit frames (partially) |
| Baganator | Category-based bag management — the community’s pick over Bagnon |
| Auctionator | Auction house toolkit |
| AtlasLootForever | Dungeon/raid loot browsing |
| EpicDamageMeter | Damage meter |
| GODMODE NamePlates / Platynator | Nameplate customization |
| ForeverAuras | WeakAuras alternative |
| Parrot 3 | Scrolling combat text |
| MBB, BugSack + BugGrabber, AckisRecipeList, TolltipID | Minimap button management, error capture, recipe lists, spell/item IDs |
On bags specifically, the thread consensus is loud: Baganator over Bagnon — better category customization, more active maintenance, and fewer conflicts with other addons. And for the aura-shaped hole in everyone’s setup, ForeverAuras is the stopgap: beta testers report it covers most everyday WeakAuras uses, with gaps you would notice only in advanced tracked-buff setups.
Which addons are still missing?
Quartz (cast bars), EavesDrop (combat log), PlateBuffs (buffs on nameplates) and a full MikScrollingBattleText replacement have no working Forever builds yet — Parrot 3 plus FontMagic is the community’s interim answer for combat text. CurseForge’s Forever filter tab is the place to watch; new ports land there weekly.
How do you enable addons in WoW Forever?
The install path is the same one Classic players already know: addons download into the client’s Interface/AddOns folder and are enabled from the AddOns button on the character-select screen. Download from CurseForge’s dedicated Forever filter tab (or an author’s GitHub) so you only get builds packaged for the beta client — then apply two Forever-specific caveats before spending an evening tuning. First, the SavedVariables bug above means anything you configure can evaporate: run ForeverSVFix, or confirm Blizzard’s fix has landed, before configuring. Second, never assume Classic parity — enable one addon at a time and confirm it survives a full relog before stacking the next.
| Step | Action |
|---|---|
| 1 | Download from CurseForge’s Forever filter tab or the author’s GitHub |
| 2 | Unzip into Interface/AddOns inside the WoW Forever client folder |
| 3 | Restart the client so the character-select AddOns list picks it up |
| 4 | Enable it, then log all the way out and back in to confirm settings persist |
Questie specifically has its own chapter of caveats — the quest helper guide tracks it in full. The short version: the official v12.0.0 prerelease added Forever client support, the maintainer rates the beta unstable (SavedVariables broken, crashes persist), the CurseForge questie-forever package is unofficial, and TomTom does not list Forever — so treat Questie as experimental until a stable release lands.
Can you make the default UI look Classic without addons?
Yes — that is the intended baseline. Forever ships a new, customizable HUD rather than the raw 2004 interface, and the demo verdict across settings was that it slides between retail-style convenience and the Classic look: hiding the micro menu, shrinking the experience bar onto the minimap, and dropping the bag bar all came up as no-addon tweaks in the community threads. Start there before installing anything, then add the addons above for what the settings cannot do.
UI and Settings Guide | Wow Forever — community walkthrough
What should you verify before importing a profile?
Three checks, in order: confirm the SavedVariables bug has been patched (or run ForeverSVFix), confirm each addon explicitly lists Forever compatibility rather than assuming Classic parity, and export a backup of anything you configure so a beta patch cannot wipe it. Quest-helper users have an extra compatibility layer to check — the quest helper guide tracks which tracking addons survive the beta client — and the retail comparison explains why the HUD design landed where it did.
Sources
- [Help] PSA: lots of addons in Forever beta can not save profiles — r/WowUI
- WoW: Forever Working Addons — r/WowUI
- ForeverSVFix — community workaround addon (GitHub)
- Embedded videos are community beta footage; rights remain with their creators.
Related Articles
World
WoW Forever Of Mice and Milk Quest: The Westfall Cookie Easter Egg
How to start Of Mice and Milk in WoW Forever: the Westfall mouse that gives it, the Nesingwary turn-in, why it's unfinished in beta, and the joke behind it.
OpenClasses
WoW Forever Undead Classes: Every Class Combo Confirmed
Every class the Undead can play in WoW Forever: the Classic five, the newly confirmed Undead Paladin, reworked racials, and why Undead Hunter is not one of them.
OpenOverview
WoW Forever vs Retail WoW: Key Differences Explained
A direct comparison of WoW Forever and retail WoW covering progression, addons, rulesets, content pace, and which version of the game fits different players.
OpenWas this helpful?
Thanks for the feedback!