Is the level-30 beta update available now?
Blizzard’s released build raises the beta cap to 30. Checked 2 October: this replaces yesterday’s maintenance preview. Consult current service notices if you cannot connect.
The illustration below preserves the European maintenance announcement as history. Its estimated restart window is not a current outage notice. Use the released patch notes and your actual client access when arranging a group.
Where are the full patch notes?
Read the dated 1 October development notes. Check dated entries before treating community reports as shipped features.
For officers, keep three short lists: confirmed changes in the notes, observations reproduced by your members, and open questions. Attach the client build to the second list. That makes it easier to revisit a report when someone tests a different version later in the week.
Recheck talent plans as characters gain levels
A higher ceiling gives members more room to develop their characters, but it does not mean everyone arrives at the same level. Ask for current level and intended next role before scheduling content. A member who wants to try healing may need a different practice group from someone continuing an established damage build.
Use our nine class talent guides to frame the discussion, then compare their dated observations with the current talent interface. Save your allocation before making changes and check the price offered for a reset. The beta respec guide explains the earlier temporary pricing announcement; the new client and patch notes should settle whether anything has changed.
Choose an activity the whole group can actually reach
Start from the lowest-level attendee and the party’s available roles. Our dungeon level-range reference helps shortlist a destination; confirm access, travel and quests before promising the run. Returning members can help a newer party with Hall of Thanes while others continue levelling.
For PvP, the Darkspear Islands map preview separates announced objectives from extracted client information. Check the actual queue and group restrictions before putting a battleground evening on the calendar. A cap increase alone does not verify that every planned activity is enabled.
Make your first session after maintenance easy to join
Confirm that attendees can log in before fixing the session. Include the region, time zone, meeting point, desired roles and finish time. Ask one organiser to post the final plan so members have a single, clear invitation.
In your guild roster template, keep current availability separate from launch commitments. Record who wants a levelling partner, who is ready for a dungeon and who is only available for a short setup check. You can form useful smaller groups without waiting for every member to catch up.
