Choose the matching symptom
| What you see | First action | What it does not prove |
|---|---|---|
| Hosting paused / temporarily unavailable | Read the service notice. Do not redownload or clear data. | Changing browser cannot restore a paused service. |
| Failed to fetch during download | Save the exact URL/error and retry once on a normal connection. | This message alone does not identify disk space, CORS or an extension as the cause. |
| Unsupported feature or storage error | Run the browser check, then read the named missing feature. | A browser brand name is not a capability test. |
| Preparing engine / black canvas | Keep the foreground tab open; note whether downloads have finished. | A black canvas alone does not establish a missing file. |
| Mouse will not aim | Click the canvas, then press Esc and click again if necessary. | Pointer capture and frame rate are separate problems. |
A recorded failure: “Failed to fetch”
The archived October 10 production checks include real Kino download failures at 0% and 2%. Limited command-line checks could retrieve selected files, while browser requests still failed. That combination shows why a successful file check in a terminal is not proof that the whole browser launch works.
Later controlled test runs entered the map using a temporary permission in an isolated test profile. That was specific to that environment and does not establish a fix for an ordinary visitor. Do not grant local-network access to an Internet game merely to imitate those tests.
- Record the failing map, stage, full error and browser version before reloading.
- Retry once without deleting site data. A partial verified cache can still be useful.
- Check whether the network normally permits large downloads. On a managed network, ask its administrator rather than bypassing a restriction.
- If testing an extension conflict, change one extension in a separate test profile. Keep browser security, TLS checks and system network settings intact.
- If it still fails, send the exact evidence through Contact. There is no verified universal fix for these archived failures.
Storage blocked or insufficient
A map can need substantially more decoded storage than its compressed transfer estimate. Private browsing, site-data restrictions and automatic eviction can prevent cache reuse. Browser storage estimates are approximate and are not an install-space guarantee.
- Read the named storage error, if present. Use browser settings to check available device space and site-data permissions.
- Try a normal window in the same browser. The private window has a different storage lifetime.
- Close duplicate game tabs that may be competing for memory or storage.
- Clear site data only when you deliberately want to remove its cache or a specific diagnosis requires it. Record the error first.
Graphics feature missing or a black screen
The archived build had an explicit WebGL2 path and an automatic renderer path. WebGPU and WebGL2 are different APIs; support for one does not establish support for the other. A capability check cannot recreate the engine’s full initialization.
After an authorized game service is available, one controlled comparison between the two launch modes can help isolate a renderer issue. Record which mode you used. Do not label all graphics problems “lag” or disable browser security to force a launch.
Input, cutscenes and recovery
Esc releases pointer capture. The archived tests also used Space to skip an opening cinematic. A canceled optional video request can accompany leaving a cinematic and is not automatically the same as a map downloader failure.
A freeze after entering a map is a separate report: include how long you played, the map, renderer, whether audio continued, and whether the entire tab stopped responding. Reloading can reuse retained files but does not guarantee recovery.