What has Blizzard said about addons?
In MMORPG.com’s 15 September interview, Josh Greenfield describes taking cues from modern WoW’s addon approach, with adjustments informed by feedback. He mentions a built-in damage meter and a planned cooldown manager, whose availability in the initial beta is uncertain.
That is a statement of direction, not a compatibility list. This article does not certify any addon as working in Forever.
Will your Classic addons work in Forever?
Treat each addon as an individual testing task. A familiar name or a working installation in another version of WoW is not evidence that it behaves correctly in the Forever client. Look for the author's explicit support statement, then test the relevant release in the available build.
Record what you actually need it to do. A raid frame displaying a group correctly does not establish that its dispel indicators, range checks and combat behaviour all work. Test those functions separately where the client allows it.
- Record the client build, addon version and test date.
- Check installation and login before testing group behaviour.
- Test the specific feature you depend on, including during combat where relevant.
- Keep a short description of any error and a way to reproduce it.
- Recheck after a client or addon update before declaring a problem fixed.
Choose a small guild UI baseline
Our recommendation is to start from the tasks players must perform: recognise assignments, read their own status and communicate when something goes wrong. Ask testers to establish what the default interface already handles before adding a guild-wide installation requirement.
For example, a healer might test party visibility while another volunteer checks whether an assignment is readable at their usual screen size. These observations are more actionable than a long list copied from a different game version.
Keep optional preferences separate from agreed requirements. If a required feature fails, write down the fallback your group will use and who will explain it before the next session.
What would change this guide?
A published compatibility policy, an available client build or a developer update could answer different questions. Check whether new information describes an intention, a feature players can test, or a result someone has reproduced. Preserve that distinction in your guild notes.
Use the beta checklist below to give each volunteer a small, repeatable task. Avoid buying or requiring a UI package on the assumption that its Forever support is already established.