Reporting problems

The problem is happening now

1. Press F8 while the game has focus. It captures the scene and mouse-over before opening the report. You can also click Report a problem; on some keyboards the shortcut is Fn + F8.
2. Describe what you did, what happened, and what you expected. Include the floor or room, skill or item involved, and whether it happens every time. For clicking or audio problems, say whether you had just switched tabs or applications.
3. Review the screenshot and click Send. Wait for the sent confirmation and report reference before closing the dialog. A greyed-out button means it is still sending.
4. If sending fails or times out, choose Download a copy and keep the file. Sending is not automatically retried. You can try Send again; mention an earlier attempt if both eventually succeed.

Reports include the build number, game state, available browser and graphics details, settings, and recent performance/memory/audio observations. You do not need to collect all of that by hand. The skeletons have already filed most of the paperwork.

The browser reloaded or the game stopped responding

1. Take a screenshot of the browser warning, or copy its exact wording. “Using significant memory” is more useful than “it went funny.” Note the approximate time.
2. Send a report as soon as the page responds again. Report a problem is also available on the Enter dungeon page; you do not need to begin another run. Say that the reload or freeze happened before this report.
3. Include where you were, what was happening, roughly how long you had actually been playing, and whether the tab had been left idle. Avoid repeatedly reloading or clearing site data before reporting.
4. If you already had the console open, save or copy its messages now. An empty console is still worth mentioning.

The game periodically keeps recent session diagnostics, including a previous run. The final moments may be missing. A browser can terminate a page without a JavaScript exception; no red error does not mean nothing happened.

Prepare once, before the next incident

You can report without developer tools. For a recurring crash, reload or audio problem, leaving the console open may give us more evidence. These steps are for desktop browsers; menu wording can vary slightly by version.

Do not paste or run commands. We only need the messages already there. Leave caching and other developer settings alone.

Chrome

1. Open the game tab. On Windows/Linux press Ctrl + Shift + J; on Mac press ⌘ + ⌥ + J. Alternatively, Chrome’s three-dot menu → More tools → Developer tools, then choose Console.
2. In the Console toolbar, open Console settings (the small gear inside the Console) and enable Preserve log. This is separate from the main DevTools settings gear.
3. Clear any text filter and keep warning/error messages visible. Leave DevTools open while playing; its docking menu can move it to a separate window if it covers the game.
4. After a problem, expand the arrow beside an error to reveal its stack trace. Right-click the message area and choose Save as… to save a .log file, or copy the relevant error and its stack into the game report description. A screenshot is useful too.

Checked against Chrome’s Console reference.

Safari on Mac

1. Choose Safari → Settings → Advanced and enable Show features for web developers. Older Safari versions call this Show Develop menu in menu bar.
2. Return to the game tab. Choose Develop → Show JavaScript Console, or press ⌥ + ⌘ + C. If Web Inspector opens on another tab, choose Console.
3. Open the Console’s filter-options menu (the filter/funnel icon) and enable Preserve Log. Older versions may show that checkbox directly in the toolbar. Clear text filters and select All messages.
4. Keep Web Inspector open. If the problem returns, expand any red error, select and copy the message and stack trace, or take a screenshot. Paste relevant text into your game report description.

Apple documents enabling the Develop menu; WebKit documents the Console’s Preserve Log filter option and inspector shortcuts.

Preserve Log helps with navigation; it cannot guarantee survival of a browser process crash or memory-pressure termination. If Safari discards the log, send the game report and exact browser warning anyway.

Until next time you see the problem

• Leave the console open with Preserve Log enabled, then click back into the game. F8 must have game focus—in developer tools it can mean something else.
• When the problem occurs, capture the report before deliberately reloading. If the browser reloads by itself, report immediately from the page that returns.
• Copy the errors before closing the tab. Note whether developer tools were open and whether you were actively playing or returning from another app.
• Keep any downloaded report and console log. If sending still fails, tell the person who invited you to play; you have the evidence ready.

A useful description: “Safari on my Mac, Chopper’s floor, about 25 minutes playing. I cast Leech and switched to another app. On returning, audio clicked, then Safari reloaded with [exact warning]. This report was sent after the reload.”

Before sharing: review screenshots and console output for personal details or sensitive URLs. Game reports go to our private report store; avoid posting full diagnostic files publicly without checking them.