1. Settle access before arranging a login time
Open the Beta access checklist. Identify your route to access and the WoW account you plan to use. Confirm the current official service notice before inviting everyone to log in at a particular hour. Keep invitation, client installation and successful login as separate checks.
If something fails, note the exact message and which step failed. Avoid changing several account or client settings at once: a clear description is more useful when following official support instructions. Do not share passwords, redemption codes or private account screenshots in a public group chat.
Before installing: PC and Mac requirements
This compact comparison comes from the Windows and Mac tabs of Blizzard’s Forever-specific requirements, checked September 17. Use the original for complete CPU/GPU combinations and later revisions.
| Check | Windows minimum → recommended | Mac minimum → recommended |
|---|---|---|
| Operating system | Windows 10 64-bit, May 2019 update or newer → Windows 11 | macOS 12 → macOS 15 |
| Memory | 8 GB → 16 GB RAM | 8 GB → 16 GB RAM |
| Storage | 128 GB available SSD space | 128 GB available SSD space |
| Minimum display | 1280 × 720 | 1280 × 720 |
Check CPU and GPU separately; enough RAM alone does not establish compatibility. The storage number is not a Beta download measurement, and recommended specifications are not an FPS benchmark. Keep keyboard and mouse available while trying controller support. Record resolution and visual settings alongside any performance observations.
2. Make one shared character plan
Blizzard’s Deep Dive recap says grouping requires the same ruleset and faction. Confirm those first, then use the race/class table and class overview.
| Decision | Write down with your friends |
|---|---|
| Account context | The region/version everyone intends to enter; verify availability in the actual client. |
| Ruleset and faction | One agreed choice for each; do not leave either until invitations fail. |
| Character | Each player’s class and race, including any unlock to check. |
| First activity | A short questing session, exploring one region, or learning a role. |
| Meeting point | A place the group can actually reach, plus an alternative if someone cannot. |
You do not need a damage ranking to make this plan. Start from what each person wants to try, then inspect the relevant abilities in the client. Keep community previews separate from a tooltip you have personally checked.
3. Plan one manageable journey
Open the destination directory and boat connection schematic. A named region, a port and a dungeon entrance are different meeting instructions. Choose the most specific location your group has verified.
For Riverglades, consult the port and location notes. For a Skyborne start, use the Zephras Isle notes. Do not send another race toward a starting area until its access is confirmed. Preview level ranges help frame a question; they do not prove a character can enter.
Save time for checking your return route and controls. A short, repeatable outing is easier to learn from than changing your class, talents and destination all at once.
4. Give your first session one question
| What you want to learn | A useful small check |
|---|---|
| A changed class ability | Read the tooltip, use it in a controlled situation and record the result. |
| A route or entrance | Record the departure, destination, access requirement and how you returned. |
| Camping | Review the system notes, then observe what your profession can contribute. |
| Playing with a controller | Try targeting, interaction, bags and menus before difficult combat. |
This is our testing method, not a claim that any specific route or build has been verified. Avoid reporting a preview value as final balance.
5. Keep a reusable field note
Copy this template into your own notes:
Date and client build:
Region / ruleset / faction:
Character class and level:
Question I tested:
Steps I followed:
What I observed:
What is still uncertain:
Official source or screenshot reference:
Record observations separately from explanations. If an ability or route behaves differently later, the build and steps help you identify what changed. Keep account details out of shared notes. Return to the source register and dated official announcements when a rule matters to your next decision.