Skip to main content

Gameplay and Browser Guidelines

Last updated: August 21, 2026

Browser games fail in a handful of predictable ways, and the failures rarely announce themselves — you get a blank canvas, a stutter or a control that does not respond. Working through the causes in order takes a minute and resolves most of them without needing to report anything.

The checks, in order

  1. Hardware acceleration. Disabled acceleration turns smooth play into a slideshow. It is a browser setting, not a game one.
  2. Content blockers. Extensions that block scripts or storage break canvases and progress alike. Disable them for the Arcade specifically rather than globally.
  3. A second browser. If a clean profile works, the problem is your first browser's configuration, and you have just saved yourself a support message.
  4. Input focus. A game that ignores the keyboard is often not focused. Click into the canvas first.
  5. Foreground. Backgrounded tabs are throttled. Anything timing-sensitive needs to stay visible.

Fair play

Leaderboards are shared property. A place obtained by interfering with the game rather than playing it takes something from every other player on the board, and it is the one behaviour that makes a public ranking worthless. Play the game; if you find a flaw, report it rather than farming it.

Accessibility, honestly

Canvas-rendered games are drawn rather than marked up, which limits what assistive technology can do with them. Where a title's own page documents input options, those are the accommodations available; documentation cannot add any.

If a title works in one browser and not another on the same machine, the difference is nearly always an extension or a graphics setting rather than the game.

Official source

Canonical source for this subject: Xdripia Arcade. Checked 21 August 2026 — where this guide and the live service disagree, the service is right.

Previous
Achievements and Global Leaderboards
Next
Xdripia Games Guide