By Open source contributorsUpdated 4 min read
A forest settlement in Blizzard's WoW Forever preview
On this page

Excavation Site is a different commitment from an early capital-adjacent dungeon. A party may be arriving from several questing routes, and its members can have different objectives even when their levels look similar. Use this preparation sheet to make those differences visible before the meeting.

Source check: October 22, 2026. Gameplay review pending. Blizzard's new-dungeon overview lists Excavation Site for levels 24–29 in the Wetlands, above Whelgar's Excavation, and describes its location near Thelgen Rock and Dun Algaz. This is location and planning context, not an independently measured travel route or a guaranteed entry requirement.

Choose the handoff from outdoor questing

Ask where each player will be when the session starts and which quests they intend to complete. Agree whether the posted start means beginning travel, meeting nearby or entering the dungeon. Give the group a named time zone, a realistic finish and a way to announce delays.

Use the Forever leveling planner to inspect your own route before changing it for the party. Keep a record of the chapter you intend to return to. Do not skip an outdoor chain solely because a dungeon estimate appears to cover the same amount of experience.

Confirm region, character ruleset and faction independently from activity preferences. A group discussing the same dungeon in Discord may still have incompatible characters. Check levels and learned abilities rather than treating the published range as proof that every player is ready for the same plan.

Prepare quests without inventing certainty

Search the quest directory for the quests players actually plan to bring. Read individual requirements, objectives and evidence labels. An incomplete or conflicting reference should not be treated as a complete quest walkthrough.

Have everyone compare the intended bundle with their own quest log before travelling. Note which prerequisite is missing and who needs help. Do not advertise a precise experience total until you have checked the actual quests, player levels and which rewards were already claimed.

If a quest is absent from the directory, that is not proof it does not exist in game. The public index intentionally excludes incomplete or unusable reference records. Report the exact name, build and observed state through the review process instead of adding a guessed objective to a public post.

State the scope and exit plan

Decide whether this is a first exploration, a quest-focused run or a repeat visit. Explain any optional objectives before players commit their evening. Agree what happens when the finish time arrives while content remains unfinished.

Choose a contact point outside the game so a disconnected player can report a problem. The host should know when to wait and when to postpone. None of those decisions needs a member's real name, credentials or private account screenshot.

Discuss the return to outdoor questing as well as entry. Players may want to finish different hand-ins afterward; say which are included in the advertised session. Do not quietly extend a short dungeon invitation into several hours of escorting the whole party around the world.

Make the party easier to lead

Assign a pull caller, a first target and relevant control jobs based on the abilities people actually have. Agree on mana pauses and an emergency signal. Keep loot expectations explicit, including named hard reserves and the handling of off-spec items.

This resource does not contain verified boss timings, safe-pull boundaries or recommended stat thresholds. A first group should observe and discuss an unfamiliar situation, not rely on a confident instruction copied from another game version. Review a specific encounter observation before turning it into permanent tactics advice.

For items, inspect the Forever database and read source/build labels. Missing stats or a historical external record are reasons to investigate, not permission to invent an upgrade recommendation.

Close the loop after the session

Create a real session through native events when the host and time are confirmed. Review all defaults, especially ruleset, faction, duration and admission. Participants should use the stated signup destination rather than maintaining a second roster in chat.

Afterward, send one reproducible finding to dungeon review: date, client build, levels, the section checked and a precise correction. Explain whether it was observed in game or read from a source. Obtain permission before publishing names or screenshots. The next version should be more useful because the evidence improved, not merely because the page became longer.

Find your next group