WRITTEN ARTICLE · INTERFACE AND ADDONS
WoW Forever addon support, UI tools and controllers explained
What developers have said about addon restrictions, the built-in damage meter, controller support and how to check a guide addon during testing.
October 8: reapply your gamepad bar settings
Gamepad action bars now support Edit Mode, with layouts saved separately for each UI type. Open Edit Mode, select the gamepad action bar and reapply preferences such as compact layout. The old Options settings are not transferred automatically.
The map initially focuses the Quest Log so movement can continue until you actively use the map cursor. Blizzard also fixed an input problem after looting and updated hold-button indicators and raid-frame navigation.
Cooldown Manager now covers every class, racials and trinkets. Further consumable support is still pending.
In this article
Looking for a quest helper in the beta?
Our quest-helper guide compares readable tracking, navigation and authored routes, with the latest tracker release notes and original Wisp beta screenshots.
Beta launch: check inherited addons and keybinds
Warcraft Tavern’s updated report describes settings carried over from a previous beta installation. Check your enabled addons before assuming a clean setup. This does not establish compatibility for any particular addon.
Record your enabled addons before isolating an error. Change one thing at a time, preserve settings and repeat the failing action. The installation guide records the local macOS client folder we inspected and separates file inspection from a successful in-game test.
Which addon API does Forever use?
Icy Veins relays a Blizzard representative’s UI Discord statement that Forever shares mainline WoW’s UI architecture and most APIs available in version 12.1.5. Its coverage also reports Midnight-style restrictions and built-in damage-meter and cooldown-manager tools from the earlier Game Informer interview.
For Wisp, that is a reason to test each supported action against the actual Forever build. It does not establish that a Classic addon can be installed unchanged, or that every non-combat API is unrestricted. Our recorded beta walkthrough shows Wisp running in the client. Full route and class testing is still in progress.
Will WoW Forever allow addons?
In MMORPG.com’s 15 September interview, Josh Greenfield describes an addon approach broadly following modern WoW, with restrictions open to adjustment after feedback. This does not establish compatibility for any particular addon.
Treat support as a question about the exact addon version and the exact game build. A project can work in another edition of WoW and still need changes for Forever. An announcement about the overall UI policy is not a successful installation test.
Earlier interview: interface tools before beta
The September interview discussed a built-in damage meter and a planned cooldown manager. That availability question is now superseded by the October 8 support announcement above. The interviewer also reports seeing Edit Mode in the demo.
Is controller support official?
Blizzard’s What’s Next recap announces official gamepad support alongside modern and Classic visual presets and HD/SD character-model choices. It does not provide a tested compatibility list for every controller or guide addon.
Controller fixes in the 22 September client build
Blizzard’s 22 September Beta Client Update (WoW Forever 1.60.1 build 69977) lists two gamepad fixes: controller navigation now works in the character selection screen when the game is launched with a gamepad active, and quest-giving items can be interacted with on a gamepad. Exit the beta and update through the Battle.net app to receive the build. If you test with a controller, note its model and platform in any report; Blizzard has still not published a compatibility list.
Our recommended first-session setup check
Start with the game’s own interface so you have a clear baseline. Then add the smallest set of tools you need, one at a time. If something breaks, you will have a better chance of identifying the change responsible.
| Check | What to record |
|---|---|
| Client and addon versions | The game build and the actual release you installed |
| Basic display | Readable text, usable panel size and accessible controls |
| Progress | Whether a completed step and selected guide survive a reload |
| Input | Whether your keyboard, mouse or controller can operate the controls you need |
| Failure case | The action that failed and whether it still fails with other addons disabled |
What does this mean for ForeverWisp?
The public Wisp beta now contains eight starting-area routes towards level 20. The previous alpha contained Classic reference routes and should be replaced. The addon page explains the new download and its known limitations.
For a guide viewer, our acceptance checks need to cover readable instructions, reliable saved progress, correct character context and recovery after a UI reload. We will only describe a particular client or input setup as tested when we have recorded evidence for it.
Make a useful beta report
Keep feedback narrow: name the build, the tool, the action and the result. A reproducible example such as a panel becoming unreachable after changing UI scale is more useful than a general statement that the interface feels wrong. Remove account details and unrelated chat from any screenshots you share.
Related reading and guides
Sources and review notes
- Blizzard: October 8 beta development notes
- MMORPG.com: Jeff Parrott and Josh Greenfield interview, 15 September
- Blizzard: Forever What’s Next panel recap
- Icy Veins: addon API statement and earlier Game Informer interview
- Warcraft Tavern: previous beta addons and keybinds, corrected report
- Blizzard / Kaivax: Beta Client Update, 22 September (build 69977)
Updated October 9 with the October 8 gamepad Edit Mode changes and Cooldown Manager support. Older API interviews and controller reports remain dated background. No new controller or Wisp compatibility test is claimed.
