Guide

How to debrief a dungeon pull

Updated November 9, 2026. Facts last checked November 9, 2026.

In short

Split the log into pulls by the gaps between fights, then review the pull that went wrong.
Look at who took the damage, what killed anyone who died, and whether the same spell kept hitting the same players.
Fix one thing per pull before you try it again.

What a pull is

A pull is one fight in a dungeon, from the first damage to the last. A run is many pulls with quiet gaps between them. Reviewing the whole run at once is too much; reviewing the one pull that nearly wiped, or did, is manageable.

World of Warcraft: Forever has a lot of dungeons. A fan site reading the client data lists 31 dungeons, with 28 in the Group Finder from level 13 to 60. The method below does not depend on which one you ran.

Find the pull in your log

Turn on logging with /combatlog before the run (see how to read your combat log).
Open the WoWCombatLog-*.txt for the run and look for stretches of lines separated by quiet gaps. Each stretch is a pull.
Pick the pull by its timestamp, using the time of the death or wipe you remember.

What to check in the pull

Size and length. How many enemies, and how long did the fight last? A long fight with healing dropping off suggests the pull was too big for the group.
Damage taken. Which players took the most, and from which spells? Damage on the tank is expected; damage on anyone else may not be.
Deaths. What was the last damage before each death, and could someone have avoided it?
Repeats. If the same spell hits the same player several times, that player is probably standing in something or missing a warning.
Interrupts and crowd control. Which enemy casts went through, and which were stopped?
Cooldowns. Were defensive and group cooldowns used on the dangerous part of the pull, or saved?

Turn it into a plan

Say the fix out loud before the next attempt: who stops which cast, who uses which cooldown when, where the group stands. A plan the whole group knows is worth more than a perfect reading of a log that only you saw.

This is general advice. Battle Debrief is being built to read a pull for you and say what to change, but it is not open yet.

Questions and answers

What counts as one pull in a dungeon?

One fight, from the first damage to the last. Quiet gaps in the combat log separate one pull from the next.

How do I find a specific pull in the combat log?

Use timestamps. Note when the death or wipe happened, find that time in the WoWCombatLog-*.txt and read the stretch of lines around it.

How many dungeons does WoW Forever have?

A fan site reading client build 1.60.1.70862 lists 31 dungeons, 28 of them in the Group Finder from level 13 to 60.

Sources

Combat logging is described from our own checks of the game client on November 8-9, 2026. The review method is general advice, not a rule from a source.

Last checked November 9, 2026. If a source has changed since, trust the source.