Help with starting and playing

Before you start

Use a desktop computer with a keyboard and mouse. The game needs browser graphics, shared memory and local storage capabilities. Windows desktop Chrome has recorded standalone and local embedded runs; formal-domain availability is still being prepared.

• Keep this tab in the foreground while loading.
• Use the current website entry and a normal browser configuration.
• The configured build supplies game resources; you do not need to upload local game files.

Loading takes time, even with cached resources

The first visit transfers a substantial set of game resources. Cached files can reduce repeated transfers, but the engine, graphics and map still need to initialize. There is no fixed startup-time guarantee.

Watch the actual stage and error text inside the game. Avoid repeated refreshing while progress is changing. If an error appears, preserve its exact text before closing the game.

Ready, mouse control and sound

At Ready, follow the prompt to click inside the game picture. This user action activates the game and requests mouse capture; the website Play button alone does not establish that the map is ready.

If the mouse could not be captured, follow the on-screen prompt to click again. For sound, check game volume, tab/site mute and system output. Keep the game in the foreground.

Pause before reading help

Press Esc and confirm the game shows PAUSED. Mouse release by itself is not proof of pause. Choose RESUME CARNAGE to return, then click the picture again if mouse capture is requested.

The website player has no pause or save command. Its Fullscreen button requests fullscreen for the player area. If the browser declines, continue in the normal window. Use the browser exit-fullscreen action; some game fullscreen modes may require holding Esc.

Closing, restarting and stored data

Close game removes the current embedded instance. Opening it again creates a new instance; do not rely on closing or refreshing to preserve your round.

Resource files and settings can be stored in browser site data. Clearing that data can cause another resource transfer and reset settings. It is not a first-step fix for every loading problem. Storage availability and persistence depend on the browser.

A login screen, blank frame or browser error

A login prompt or framing error requires attention from the maintainers. Do not disable browser security, install an unknown extension or paste credentials into the website to bypass it.

For a useful problem report, record your browser/system, whether this was the first visit, the visible loading stage and the exact error. Include a screenshot without private information. Do not send cookies, Access tokens or authentication links.