THE PLAYBOOK
Connection and performance help
Troubleshoot Ball2D room admission, direct peer connections, host interruptions and browser performance.
A listed room is only the first step
Joining first contacts the room service, then establishes a direct browser connection to the host. Seeing a room or opening an invite does not guarantee that the peer connection can complete. Check that the host is still online and the room has space.
Confirm the invite code and password with the host. If the room has closed, ask for a fresh invitation. Never post passwords or host tokens in a public bug report.
When the direct connection fails
Some corporate, school, VPN and mobile networks restrict peer traffic. Try a different network or another host to isolate the cause. Ball2D does not promise a relay fallback for every network.
A browser may require a verification step before admission. Complete the visible verification normally. Repeated retries do not bypass room passwords, capacity limits or security checks.
Reduce interruptions
Keep the host tab visible and the device awake. Background throttling, sleep or closing the host can interrupt a match. Use a stable connection and close heavy background applications when frame pacing is poor.
The game targets desktop browsers with keyboard controls. A phone can read these guides, but touch gameplay and every mobile browser are not guaranteed. Browser extensions that block WebAssembly, WebRTC or scripts can prevent play.