Support-safe reporting
Report an issue without leaking secrets
Use this flow when a screen looks wrong, an action fails, or current-state recovery does not help.
What to include
- Screen URL and visible screen title.
- The action clicked or command typed.
- Whether Play / Current State recovered the situation.
- Visible correlation IDs if shown.
- A sanitized debug report from /debug/sanitized-report.
- A scenario report from /scenario/report if you were playing through the loop.
Never include
- Passwords.
- sign-in session tokens.
- Cookies.
- Database credentials.
- Private keys or certificate material.
- Screenshots with secrets visible.
Useful links
Report an issue
Stuck or blocked? Use the report form and choose the closest category: stuck, combat, reward, account, typo/content, accessibility, or other.
Support ID. The form creates a support ID you can copy into a message so staff can connect your report with the safe details you provide.
Safe bundle. The bundle is player-provided context only. It excludes sign-in secrets, private files, hidden campaign truth, server logs, and model output.