Help Center

Player Support

Use this page to recover accounts, troubleshoot common browser issues, and understand the fastest self-service path for gameplay, profile, and notification problems.

Updated June 13, 2026

Account and sign-in help

If you cannot sign in, start with password recovery and then return to the sign-in screen once you receive a reset link. Session problems are often resolved by refreshing the browser after the platform rotates your session in the background.

If a page redirects you back to sign-in, verify that your browser allows cookies for the site and that you are using a supported loopback hostname consistently during local development.

  • Use password recovery for forgotten credentials
  • Allow site cookies so refresh-session rotation can succeed
  • Avoid mixing localhost and 127.0.0.1 tabs during the same troubleshooting session

Gameplay troubleshooting

If a room, leaderboard, or tournament screen looks stale, refresh the page once and re-enter from the latest lobby or leaderboard entry point. The platform is designed to recover state from the server rather than trusting stale client data.

For notification issues, check the notification center first. Browser push depends on service-worker and notification support in the current browser and may be unavailable in restricted environments.

  • Re-enter matches and rooms from the lobby if a stale page was left open
  • Use the notification center to verify unread alerts and push support state
  • Check public profiles and leaderboards when verifying rank or wallet disputes

Safety and fair-play reports

Suspicious match behavior, abusive chat, and repeated exploit attempts are reviewed through the platform’s moderation, audit, and fraud-analysis systems. Support evidence is strongest when you can reference the match, leaderboard, or tournament context in question.

For local or managed deployments, route escalations through the operator or moderation process attached to your environment. The support center is designed to point players toward the correct in-product evidence and recovery flow.

  • Record the match code, tournament, or player profile involved in the issue
  • Use public profile and leaderboard links to provide consistent identifiers
  • Do not share secrets, raw tokens, or browser storage contents when reporting an issue