Player guide
Help us reproduce it: a practical beta report guide
A useful beta report tells us what you tried, what appeared and what happened next. You do not need to diagnose the problem or know how the game is built.
Start with one clear example
Give the report a short title that describes the result: “The screen did not update after signing in” is more useful than “It is broken.” Keep separate problems in separate reports so each can be followed clearly.
Write the steps in order, starting from the last point that worked. Name the action you selected and quote any visible message exactly. If you do not remember a step, say so rather than filling it in.
Tell us what changed
Describe what you expected and what you actually saw. Include whether the issue happened once or more than once, and the approximate time with your time zone. If you already tried reloading or signing in again, mention what changed; you do not need to repeat an action with an uncertain outcome just to create a report.
Device context helps: desktop or phone, browser name and version if known, and whether the page was in portrait or landscape. If a screen layout is the problem, a screenshot can show details that words miss.
Use this short template
- Title:
- Approximate time and time zone:
- Device and browser:
- Steps before the issue:
- Expected result:
- Actual result or exact message:
- Happened once or repeatedly:
- What changed after any reload or sign-in already attempted:
Share the useful part, not your credentials
Crop screenshots to the relevant area and check them for private account information. Do not post passwords, email verification or password-reset links, session tokens, or another player’s private information. Full browser logs can contain private details; a visible message and a clear sequence of steps are a better starting point.
Use the official community links on this site to share your report. This guide describes how to give useful feedback; it does not announce a new game feature, supported district or release date.