Controls & Gamepads

These mappings come from the project author’s README at the listed commit. We have not independently tested a keyboard, controller, phone, or vibration behavior. Record your controller model and browser version when contributing a report.

Browser keyboard reference

The README groups the shoulder keys together; the pinned browser shell source assigns Q/W to L1/R1 and 1/2 to L2/R2. This is a source-code observation, not a tested controller result. The README does not document keyboard bindings for a right analog stick.

Connect a gamepad

The browser build uses the browser’s Gamepad API. The author documents analog triggers as pressure-sensitive L2 and R2 input, plus vibration when a connected controller has motors and the browser exposes that feature. Chrome and Edge are specifically mentioned for vibration support.

For a useful first check:

1. Connect the controller, open your local game page, and interact with the page.
2. Check menu navigation before testing a time-sensitive gameplay sequence.
3. Compare a face-button input with its keyboard equivalent to separate a controller problem from a game that has stopped responding.
4. If a trigger or vibration behaves differently, record the controller model, connection method, browser version, game version, and scene.

These checks are a reporting workflow, not a list of independently verified fixes. The README does not publish a certified controller compatibility list. Lack of vibration alone does not establish that the whole controller is unsupported.

Phones and fullscreen

The author documents on-screen controls for phones. That is an input feature, not evidence that either featured game reaches an acceptable frame rate on a phone. No mobile device benchmark is provided in the reviewed source.

Use F for the browser page’s fullscreen toggle. The separate native runner uses F11 for fullscreen, and its arrow keys serve as both the D-pad and left stick. Keep native and browser reports separate so that those differences do not get mistaken for regressions.

What to include in an input report

Describe the expected input and the observed result. Include whether the keyboard works, whether the gamepad appears in another game or browser, and whether the issue is continuous or limited to a scene. A short recording is more useful when it shows both the action and its result; remove personal information before linking evidence.

Use the browser check to check required browser features before a build. It does not test controller input. For a local build, begin with Getting Started. Keep a backup of your progress with the memory-card guide before changing your setup.