A black screen or WebGL2 error
Update your browser and check whether hardware acceleration is enabled. A passing WebGL2 check only confirms that a graphics context can be created; it does not guarantee enough memory or a stable frame rate.
If the screen remains empty, open the game in a full page. Report the browser version and the action that led to the problem; do not send your complete game files.
The file picker or touch controls do not respond
Open the client as a full page and rotate your device to landscape. Close other memory-heavy tabs. Use the client's own touch controls; the surrounding website does not intercept movements inside the canvas.
A phone browser may decline fullscreen or orientation locking. You can still rotate the device manually and use the full-page view.
Login or multiplayer connection fails
Check the service status page first. Our independent backend is not open yet, so retrying credentials will not bring it online. We never forward login details to the upstream service.
Once live, a version mismatch, maintenance, an expired session, and a network interruption should be handled separately. Keep the displayed error when contacting support.
A save is missing or has not synced
Do not clear site data as a first troubleshooting step. Local storage and confirmed cloud storage are different. Keep the last valid save and wait for a successful confirmation before closing a page.
Changing browser profiles, devices, or origins does not automatically transfer local saves. Cloud recovery and simultaneous-device conflict handling are pending verification.
Send a useful report
Email mooyuking@gmail.com with the page, device, operating system, browser, approximate time, and reproduction steps. Include a short error message if available.
Never include a password, recovery code, session token, private chat, or complete save file in an initial report.