Find your footing.

Explore available WoW Forever dungeons in 3D, inspect creatures and potential loot, and build a route with pulls and floating notes. You can also inspect a combat log to see what your run recorded.

Exploring and local log analysis do not need an account. Create a confirmed account when you want to save a plan online.

Start in the explorer and use the dungeon selector. Browse all dungeons shows the catalog; the dungeon directory is another way to choose a map.

Once inside, drag to look around and click a creature to open its guide. Use the Plan tab when you are ready to sketch a run.

They are reference data, not a live connection to your game. A dungeon may use historical geometry, creature placements, or representative models. Open Source details in the dungeon panel for that package’s context.

Potential loot does not guarantee a drop. Current servers may differ from the imported data, and item details from outside services can be unavailable.

Drag to look around. Press V to switch between click to move and WASD. Hold Shift while moving to sprint. Shortcuts pause while you type or use a dialog.

Travel to the selected creature

F

Teleport to a visible surface

Double left-click

Place a floating note

T

Hide / restore the interface

I

Map / walk view

M

Explore / plan mode

E / P

Search creatures / browse loot

/ / L

Save plan

Ctrl / ⌘ S

Undo / redo

Ctrl / ⌘ Z / Ctrl / ⌘ Shift Z

Cancel or stop / show shortcuts

Esc / ?

Screenshot view hides the interface and markers; take the screenshot with your usual device controls. Press I or Esc to restore the interface.

Double left-click a visible floor or shore to teleport to a suitable landing. This works in both movement modes. You can continue walking afterward; teleport is a single action.

You can also select a creature and press F to visit its viewpoint. The lower-left map supports zooming and panning: select a spot, choose a ground layer if offered, then use Jump here.

When placing a note or drawing a route, clicks belong to that tool. Press Esc to finish or cancel it first. The viewer does not reproduce all in-game jumping and swimming.

1. Open Plan and create a pull.
2. Select creatures, then use Plan this pull to add them. Ctrl + click selects several creatures.
3. Add route stops with Add here or Draw route. Use Walk route to preview.
4. Add floating notes for positioning, skips, or reminders. Creature tactical notes can record danger, priority, crowd control, and interrupts.
5. Use Save plan to keep the finished plan online, or Export plan to keep a file.

A drawn route is your plan, not a recording of a previous run.

Press T, then click a visible floor, wall, object, or creature. Write the message and save the note to your plan. Click a marker to read or edit it; Move pin changes its anchor.

Notes are plain text and belong to the plan. Saving a note updates your current draft; use Save plan or Export plan before closing the page.

1. In WoW, open Options → Network and enable Advanced Combat Logging. If the menu differs in your client, search Options for “advanced combat logging.”
2. Before your first pull, enter /combatlog in chat. Check the game’s message confirms logging has started.
3. Play your run normally. At the end, enter /combatlog again and confirm logging has stopped.
4. Find the file in that client’s Logs folder, then open it in the log inspector.

The command toggles logging, so check the chat message each time. Turning it on after a pull cannot recover earlier events. Advanced logging adds fields; it does not guarantee that every player has continuous position data.

Look in the Logs folder inside the WoW client you actually launched. Files are usually named WoWCombatLog… and end in .txt.

• Windows: in Battle.net, select your game version and use its options menu → Show in Explorer. Open the active client folder, then Logs.
• macOS: use the corresponding Show in Finder option, then open the active client’s Logs folder.

Install locations and client folder names vary. If several versions are installed, compare the file’s modified time with the run you just finished. A _classic_beta_ log is only the right file when that is the client you played.

Choose a raw combat log ending in .txt or .log, or a .gz compressed log. ZIP archives must be extracted first. Screenshots, damage-meter exports, and links to reports are not raw combat logs.

The current file limit is 512 MiB. Compressed logs also have a 2 GiB decompressed limit. A file under the limit can still be too demanding for a device with little available memory; a smaller recording is easier to inspect.

The importer recognizes the WoW Forever advanced-log signature: format 22, project 18, build 1.60.1. Recognition identifies a format, not proof of the server the file came from. Other formats may be rejected or have incomplete results.

It finds visits in your file, then summarizes the selected visit’s damage and healing activity, casts, deaths, encounters, and available position samples. You do not need positions for all five players to use the report. Missing positions leave combat analysis available.

Open Recorded positions to scrub through the horizontal coordinates that were actually recorded. You can export an anonymous summary for inspection. This preview does not publish a report or create a shareable replay automatically. Amounts are recorded totals, not verified effective DPS or HPS.

Import the original file. The inspector separates visits using the location changes it records and starts with a relevant dungeon visit when one is recognized. Use Choose a visit above the report to select another visit. Each choice analyzes that portion of the file locally.

Returning to the same dungeon can create another visit. Check the visit’s event count and encounters to find the section you want. If the file has no location markers, it is analyzed as an unspecified session. Observed players are not a verified party roster; city events and transition records can include bystanders.

You can play or scrub the Recorded positions view now. It is a horizontal coordinate plot of observed players, creatures, and pets. It does not show the dungeon’s 3D geometry or reconstruct a complete walking route.

A player does not need coordinates for the other four party members to inspect their own recorded samples. Actors disappear when their observations become stale, so missing movement is visible. Dungeon floors, height, and accurate placement in the 3D explorer still need validation before full 3D playback is available.

A combat log records events. Some events include a position for one actor; they are not a continuous recording of the whole party. A report can be useful with partial coverage or no positions at all.

Coverage shows which actors have usable samples. A player can have casts or healing events and still have no recorded positions. In the coordinate view, an observation is displayed for up to five seconds; gaps are left empty. Large recordings may have their displayed samples thinned, with a notice, to keep playback responsive.

Enable advanced logging before recording. Some beta files contain valid advanced fields even when their header says logging was disabled; the importer checks the actual record layout and explains that discrepancy. It cannot restore coordinates that were never recorded.

No additional addon or desktop uploader is required for this import workflow. Use the game’s built-in combat logging, then select the file in your browser.

An addon that starts logging for you may be convenient, but it cannot restore events that were never recorded. Always confirm the game is logging before the first pull.

The log inspector processes your selected file in your browser. It does not upload the raw log, require an account, or automatically save the analysis to our servers or browser storage. Closing or reloading the page clears the current analysis.

An exported summary is a separate file you control. Review it before sharing: removing player names does not make the details of a run impossible to recognize. Ordinary website requests still use our hosting services; see the Privacy Policy.

Saving a plan online requires a full account with a confirmed email address. Your ForeverDungeons account is separate from your Blizzard account. Never enter your Blizzard password here.

You can explore and edit a draft before signing in. Use Export plan to keep a local copy. Unsaved draft edits can be lost when the page closes or reloads.

A local Studio account is separate from a hosted website account. Local plans are not automatically uploaded.

• Private: ordinary access is limited to your account.
• Unlisted: anyone with the link can open it and forward the link.
• Public: anyone can view the plan without signing in.

A shared plan opens read-only until the viewer makes a copy. People who can view a plan can copy, export, or screenshot it. Changing visibility cannot recall copies they already made. Private plans are access-controlled, not end-to-end encrypted.

The hosted account menu has Delete my account. It requires your current ForeverDungeons password and confirmation. Export plans you want to keep first: deletion removes the active account, saved plans, and sharing links.

For help with access, correction, or deletion, email nomabond@foreverdungeons.com. Do not email a password. See the retention details for separate provider logs, backups, and local Studio files.

1. Choose the actual WoWCombatLog… file, not a screenshot, shortcut, or damage-meter export.
2. Stop in-game logging first so the file is no longer being written.
3. Extract ZIP archives. For a damaged .gz file, try its original text log.
4. Check the supported format and size limits, then read the inspector’s specific error.

If it still fails, tell us the error text, client build, file size, and whether it is a public or private server. An anonymized summary can help when analysis succeeds. Do not send a full raw log unless we have agreed on a way to share it.

Check that you selected the right client’s file and recorded from before the first pull until the end. A late start, logging being toggled off, or an incomplete file can leave gaps.

Not every client or server supplies the same encounter metadata or actor details. An absent boss label does not necessarily mean there were no combat events, and a player with no positions may still have recorded actions.

The inspector cannot recover events that were never written. Keep the original file if you need to revisit the analysis.

The browser has to read, decompress if needed, and parse the recording. File size, event count, and your device all affect the time required. Parsing runs in a background worker so the page can stay responsive.

You can cancel and choose a smaller file. Closing other heavy tabs can help on devices with limited memory. Compression reduces the file on disk, not the amount of log data that must be processed.

Try a current browser with hardware acceleration enabled. In the viewer’s View settings, hide decorations or creatures to reduce what is drawn, and check Technical details → Performance details.

The first visit downloads the dungeon’s assets and can take longer than a return visit. If a problem persists, report the dungeon, browser, device, and any visible error. Save or export a draft before refreshing.

Check the email address you entered and look in spam or junk for the confirmation message. Use the sign-in screen’s confirmation or password-recovery option as appropriate, and use the newest email link.

If the app reports an email delivery error, contact support with the visible error and approximate time. Never send your password or the private link from an account email.