1. The arena is still loading

Keep the tab visible and read the loading message. The arena needs game assets and browser initialization before it can accept input. The displayed stages describe startup work; they are not a download-speed measurement. Check whether other websites load and pause large background downloads. If the page shows a retry action after a failure, use that action once and watch whether the stage changes.

Repeatedly refreshing starts the process again and can hide the original error. Record the message and approximate waiting time before retrying. If the same stage fails again, include that detail when contacting support.

2. The arena is blank or JavaScript is disabled

The playable arena requires JavaScript and a browser capable of running the 3D game. The written guides remain readable without starting the game. Enable JavaScript for this site if you intentionally disabled it. If a browser extension blocks scripts, test with that extension disabled for this site only, rather than weakening unrelated browser security settings.

Try an up-to-date browser and note any graphics error. A page loading successfully does not prove that its game renderer initialized. Do not install software advertised by an unrelated popup as a supposed requirement.

3. Keys scroll the page or do nothing

Click inside the game window and close an open menu before testing W, A, S, and D. The browser sends keys to the focused element; a selected text box or the outer page can receive them instead of the arena. Check the Controls panel for your saved bindings. Test one key without holding boost or another modifier.

If a mouse action opens a browser menu, restore focus to the game and test again. Record whether the issue happens in solo, a room, or both.

4. The page works on my phone but I cannot drive

The site has mobile layouts for reading, browsing the leaderboard, and creating or joining rooms. That does not mean the current game has a complete touch-driving interface. Use a keyboard and mouse for the controls described in these guides. A phone can still help you read a room code or instructions, but joining from it may occupy a room seat without giving you practical driving controls.

5. The bot match takes longer to start than free play

The selected opponent needs additional resources and initialization. Watch the opponent-loading message instead of assuming the already-visible arena means everything is ready. Closing the match setup cancels the pending opponent preparation; opening it again begins a fresh attempt. If you repeatedly see an error, note the chosen difficulty and whether free play itself remains responsive.

6. My friend cannot join the room

Compare the six-character code carefully or copy a fresh invite link from the active room. Verify that the host is still in the intended session. Check the four-seat capacity, including places briefly reserved after a disconnect. A private room is absent from the public directory, so use its invitation instead of searching the list.

If the error says the room no longer exists, create a new one and share the new code with everyone. Avoid reusing an old message without checking the active room.

7. The room is open but Start match is unavailable

Check the roster. Every online player must choose a team, and red and blue must each have at least one online player. Only the host can start the match. A single player can enter free practice after selecting a team, but cannot start a scored match alone. Practice remains practice until the host deliberately starts a match with an eligible roster.

8. A public room is missing or its count changed

The public lobby refreshes periodically and also offers a manual refresh. Rooms can become full, lose their host, or disappear when all players leave. The list is a recent summary, not a reservation for a seat. The actual join request checks the current state. Refresh the directory once, then use the room's current invitation if you are coordinating with its host.

9. A player disconnected and the clock paused

If one team has no online players, the match clock pauses. A briefly disconnected player can reconnect within about 30 seconds using the same browser tab session. Opening another browser does not carry the same reconnect token. An intentional Leave action releases the seat immediately. If the host leaves, another online player can become host; the server does not depend on the original host's page staying open.

10. Movement feels delayed or the image stutters

Compare solo and multiplayer on the same device. If both stutter, close demanding tabs and check whether changing an available graphics setting helps. If only a room feels delayed, pause network-heavy activity and test a stable connection. These comparisons narrow the problem but do not prove a specific cause. Avoid presenting an estimated delay as a measured ping.

Do not ask everyone to refresh simultaneously. Have one player reconnect while another stays in the room so you can see whether the session remains active.

11. A finished game is missing from the leaderboard

Finishing and publishing are separate actions. Use Submit to leaderboard for an eligible completed result, or check the leaderboard for pending matches. Practice and early exits do not create normal submissions. Goals expire from the rolling 24-hour window according to their original event time; submitting later does not extend that window.

Your identity is tied to a browser cookie. A private window or cleared cookies can produce a different identity. A team's total is also not necessarily the same as one player's credited goals.

12. I need a clean test or a support report

Before clearing site data, understand the consequences: saved settings and names can disappear, the anonymous leaderboard identity can change, and clearing tab storage can prevent a reconnect. Try a separate browser profile for diagnosis first, keeping the original session intact. Do not assume deleting local data also deletes server records; use the privacy contact process for data requests.

For support, include the page, approximate time and timezone, browser and operating system, mode, visible error, and shortest sequence that reproduces it. Remove personal information from screenshots. Do not send cookies, reconnect tokens, passwords, or complete browsing history. Email the address on the contact page; there is no promised response time or automated recovery service.