🧰 Name the state before trying a repair
When the 20-0 game is not loading, the first useful observation is what you can actually see. A cover waiting for Play, a blank opened frame, a profile prompt, and a selected card waiting for placement are different states.
The player may simply be waiting for its start action.
Loading, connection, or an embedded-content restriction may need inspection.
The live game is asking for a session condition, not another display size.
A selection or placement step may still be incomplete.
Keep the exact visible message. “It does nothing” hides the distinction that determines the next check.
The initial cover is intentional
The homepage starts with a local cover and a Play button. The live game is loaded after that deliberate action. Seeing the cover before you press Play is therefore expected behavior.
If the game was previously closed with Restart, the cover returns. Pressing Fullscreen can enlarge that cover without launching the game, because display and loading controls have separate jobs.
Start with the visible button state before diagnosing a blank network response. It is a simple check that does not discard an existing draft or change browser settings.
🔍 Choose the branch that matches the screen
Use the least disruptive check first
| Observation | First check | Before doing anything more disruptive |
|---|---|---|
| Cover remains | Press the actual Play control once. | Confirm whether a live frame appeared. |
| Opened area is blank | Check the connection and read any browser message. | Note the time and state before closing or reloading. |
| Profile or sign-in prompt | Read the game’s displayed access requirement. | Keep the exact message; a display change is not a response to an account requirement. |
| Card detail opens but no pick commits | Check the legal highlighted destination. | Inspect the selected player and remaining role. |
| Only the local checklist will not persist | The browser may restrict local storage. | The checklist can still be used during the current visit. |
| Only fullscreen fails | Try the site’s expanded display path. | Separate display support from whether the game itself loaded. |
A visible live interface narrows the problem
If the game’s own controls or access message appear, some live content has loaded. That observation is different from an entirely empty opened area. Record the exact state rather than describing both as the same failure.
If the game displays a profile or sign-in message, record that message as the visible state. More of the live interface has loaded than in a completely blank player. Closing it repeatedly will not tell you which condition the message is asking you to meet.
If the board itself is visible, use the selection and placement states before assuming a legal-position rule is a broken button.
When the opened frame stays empty
First check whether the rest of the page is readable and whether the browser displays a connection or blocked-content message. A static guide can remain available while the live game needs a working network connection.
If you use a content restriction, school network, or managed browser, inspect its visible message. Do not disable protections you do not control or assume a restriction proves the game is unavailable everywhere. A different policy can affect the same page differently.
One deliberate retry can help distinguish a transient load from a persistent condition. Before reloading, accept that the current player session may be interrupted. Do not repeat restarts while expecting them to preserve an unsaved draft.
Keep checklist storage separate from game access
This site’s homepage checklist stores its selections locally when the browser permits it. Failure to retain those ticks does not establish that a roster is corrupted or that the game’s sign-in state needs to be erased.
The guide’s temporary worksheets also do not promise a saved history. A note disappearing after reload can be expected behavior rather than evidence of a failed server submission.
Before clearing any site data, identify the state you would lose. Local checklist ticks, temporary guide notes and the game’s own session are different. Use the checklist reset for the guide’s ticks when that is the only problem; it does not repair a game login or placement.
Prepare a report someone can reproduce
A useful 20-0 game troubleshooting note names the page, the visible state before the problem, the action you tried, and the exact message afterward. Add the browser and device type if they help distinguish a display problem.
Leave passwords, recovery details, private invitation tokens, and account information out of screenshots. A cropped image of the affected control is usually more useful than the entire screen.
Use the feedback builder to organize a page-specific report. For display-only trouble, the native-versus-expanded guide offers the next relevant check. Stop when the actual cause is identified instead of applying every possible repair.