Start with a non-destructive baseline
Record the page, approximate time, browser name and version, the action you attempted, and the visible result. Then reload the page once. Avoid clearing site data, removing local assets, or rebuilding a deck until you know whether the problem is temporary; those actions can destroy the evidence or browser-only state needed for diagnosis.
Check the Known Limitations page before treating expected beta behavior as a new outage. For an online issue, ask the other player to pause and compare public state rather than repeating the action.
Sign-in or workspace does not open
Confirm that the public home, About, and Guides pages load without a login. If only the account workspace fails, verify that the browser allows the Google sign-in flow and that you selected the intended account. A content blocker, disabled third-party sign-in window, or expired session can interrupt authentication while the public site remains healthy.
Do not send screenshots that expose your Google account, email, tokens, or browser cookies. Report the stage where the flow stopped and the error text after removing personal details.
Deck import is incomplete or points to the wrong card
Keep the original shared URL and do not overwrite the last known-good saved deck. Compare the expected count, the displayed count, and the first incorrect entry. Determine whether the source omitted a card, the external ID matched a different printing, or the DM Value catalog lacks the record.
Retrying the same import many times rarely changes a deterministic match. Use the deck import checklist to collect the expected identifier and the displayed identifier, then report that pair without including unrelated account information.
Local images are missing after selection
Test one known file in a normal browser window. Check whether the browser supports the selection method, whether storage is available, and whether the card identity matches the file naming or archive structure. A file that works until the tab closes suggests private-browsing or storage persistence behavior rather than a public catalog outage.
Do not attach image collections to a support request. Report the non-sensitive filename pattern, file type, visible card identifier, and whether a reload removed the match.
Online room is stale, disconnected, or different between players
Stop all table changes. Identify the last action both players saw and compare the active turn, public card counts, and room status. Allow one reconnect or lobby return. If the screens still disagree, end the test instead of trying several conflicting corrections from both browsers.
- Pause both players and note the approximate time.
- Compare only public state and the last shared log entry.
- Reconnect once; do not repeatedly submit the same action.
- Preserve a concise description of expected and actual public state.
- Report the room symptom without private hand contents or chat history.
What a useful report contains
Use the Contact page for technical, privacy, abuse, or rights-holder questions. A useful technical report contains a short title, reproducible steps, expected behavior, actual behavior, browser details, approximate time, and whether the issue occurs in Solo Play or online. Mention any recovery already attempted.
Never include passwords, authentication codes, cookies, API tokens, payment details, local file paths containing your name, or private card images. If a screenshot is essential, crop it to the affected interface and inspect it for personal information before sending.