Reaching the cap changes the question from “where do I level?” to “what do I want to learn next?” Pick a question that matters to your character, then choose an activity that can answer it.
Start with the question you actually have
| Question | Start here | Leave with |
|---|---|---|
| What can my group run? | Beta dungeon directory | One destination and a shared quest checklist |
| What should I change in my build? | Level-30 talent planning | Two comparable saved plans |
| How do I test Legacy perks? | Legacy testing worksheet | A before-and-after comparison |
| Is this item worth a detour? | Gear decision guide | A usable upgrade shortlist |
| How do I get from 20 to 30? | Questing versus dungeons | A route decision based on your own session |
Turn a search into a session
Our Beta Session Planner combines your level, class, available time and goal into a short plan. It also opens a class-specific talent calculator at the level you selected. You can tick the preparation steps and copy the plan for your group.
We built the planner around decisions rather than a completion score. A player with half an hour and no group needs a different suggestion from five friends who have an evening together. The planner does not predict loot, dungeon completion time or damage. Its suggested time blocks are a way to organize your available time.
Two updates that change your plan
The October 8 update opened City of Dalaran for testing and granted beta participants 16 Legacy Points. Follow the official update for the complete changes.
For a group, that creates a useful split: a discovery run and a controlled comparison. A discovery run asks what is unfamiliar and where the group hesitates. A comparison asks whether one change helps with a specific problem. Trying both at once makes your notes harder to interpret.
A sensible order at the cap
- Check your current spell ranks, quest log and gear requirements.
- Choose one relevant guide above and write one question.
- Save your current talent plan before changing it.
- Run a familiar activity once before testing something unfamiliar.
- Record the build date, your level and the result you observed.
For example, a player investigating downtime should track recovery stops and the actions that caused them. A player investigating a dungeon role should agree on comparable pulls with the group. Neither needs to turn the session into an unsupported “best class” ranking.
What a level-30 cap does not promise
An accessible dungeon can contain enemies or rewards above your level. A database can contain content that is not yet enabled. Treat the in-game acceptance requirement, equip requirement and your group's readiness as separate checks. Our quest catalog is a partial community-data reference; it is not a guarantee that every record is available in this phase.
Keep a short deferred list for anything you cannot use yet. This prevents a future reward from taking priority over a question you can answer tonight. At the end of the session, keep one discovery, one unresolved question and one next action.
Send the page link, the detail, and an official source to dleowls01@gmail.com. Please do not include account passwords or private game-account details.
