What is available in the opening beta?
Blizzard’s beta announcement sets the initial level cap at 20, with 30 coming later. Opening content includes Skyborne, Zephras Isle, zone content through level 20 and two highlighted dungeons. These are announced testing ranges, not a claim about minimum entry requirements.
| Content | Announced availability |
|---|---|
| Character level cap | 20 initially; 30 later |
| Hall of Thanes | Levels 13–18 |
| Ruins of Lordaeron | Levels 15–20 |
| Skyborne starting experience | Zephras Isle |
Check access before scheduling the group
Blizzard says invitations continue during testing. Eligible accounts install World of Warcraft: Forever Beta from Battle.net’s In Development game-version list. The announced last full testing day is 21 October. A later Server Slam is planned, with details still to come. Read the access instructions.
Ask members to confirm that they can reach character selection before counting them as available. Someone who has opted in but has not received access should remain on a waiting list. Build a session around people who can actually attend.
An example 90-minute guild session
This is our suggested testing plan, not an official schedule. Choose an activity appropriate to the actual levels in your group; do not rush a new character simply to fit a dungeon appointment.
- First 15 minutes: confirm names, invitations, voice or text communication, and one shared objective.
- Next 45 minutes: explore or run suitable content together. Assign one person to collect questions and noteworthy failures.
- Next 20 minutes: repeat one confusing interaction under clearer conditions, if practical. Record what changed.
- Final 10 minutes: agree what you learned, what remains uncertain and who will follow up.
Measure something your guild can use
Useful outcomes include whether members enjoyed their proposed roles, whether the meeting time worked and whether the group could recover from a disconnect. A successful beta evening does not need to produce a definitive class ranking.
Record level, build, group composition and relevant talent choices alongside observations. Check the known-issues guide before interpreting an unusual result as intended design. Short early sessions provide useful questions, but limited conditions make broad balance conclusions premature.
Use raid readiness planning to understand the preparation workflow, and the beta guild checklist to record your questions. Treat any launch roster decision as provisional until members have tried the role they want.