Which beta dungeon should you run next?

Choose a dungeon for the question your group wants to answer. Availability, a published level range and readiness are three different pieces of information.

New access around the level-30 phase

The first three labels are from the October 1 notes. Dalaran's availability is from the October 8 notes. We have not substituted an old Classic range where Blizzard did not give one. “30+” is not a promise that a level-30 group can comfortably clear the entire instance.

Previously available dungeons

The October 1 notes also list Ragefire Chasm, Hall of Thanes, Ruins of Lordaeron, Wailing Caverns, The Deadmines, Shadowfang Keep, The Stockade, Blackfathom Deeps, Gnomeregan, Razorfen Kraul and Scarlet Monastery.

Use that list as an availability reference. Choose the destination with your group's level spread, familiarity and purpose in mind. A lower-level dungeon can be useful for testing a changed ability without the confusion of an unfamiliar encounter. A newly opened dungeon is better suited to a discovery session.

Agree on three things before traveling

1. Purpose: discovery, quest completion or comparing a build.
2. Preparation: who has which quest, which supplies are missing, and which role each player intends to test.
3. Stopping point: agree when to reassess a difficult section instead of assuming everyone wants repeated attempts.

A five-minute conversation can save an entire trip. Read the quest objectives aloud, especially when similar names have different faction or chain requirements. Keep turn-in travel separate from the dungeon itself when estimating your session.

Make a quest shortlist, not a promise

Open the quest finder and search the dungeon name. Record the quest ID, minimum level and any earlier chain step. For Ruins of Lordaeron, search “A Frightened Request” and “Crest of Lordaeron” as examples. The catalog's recorded quest level is not a suggested solo level.

Confirm those records against your current quest log. Our October 7 client-cache snapshot predates later tuning. Keep a quest off the shared checklist if the starting condition or current availability is unresolved; a named database record alone is not enough to send the whole group across the world.

Compare a run fairly

Record the group levels, destination, build date and what changed. Separate fighting, recovery, waiting and travel. If one run had a longer invitation delay, that does not prove the build became slower. If your purpose is discovery, write down where you hesitated rather than treating a first clear as a speed benchmark.

Use the session planner to create a shared preparation list. After the run, add the encounter or objective that needs a second look. This turns a dungeon visit into a reusable group note without inventing a boss strategy that we have not tested.