v149 · Web APIs · Input
Combo Detector
Fighting-game style combos require catching every button press in sequence, including rapid inputs between animation frames. Polling misses sub-frame presses entirely — but rawgamepadinputchange events fire for every physical button transition, making multi-input combos reliable for the first time on the web.
Registered combos
Name
Sequence
Count fired
Hadouken
↓ ↘ → A
0
Shoryuken
→ ↓ ↘ A
0
Super
A B A B
0
Quick Dash
→ →
0
Simulate button presses (or use a real gamepad)
Input buffer (last 8)
No inputs yet…
// Press the sim buttons or connect a gamepad…
Why polling misses combos: a "double-tap right" combo requires detecting two → presses within ~200ms, which may both land in the same animation frame. Poll-based code sees only one sample per rAF tick — the second → is invisible.
rawgamepadinputchange fires for each physical transition, so both presses are delivered even if they are sub-frame.
see also
- Latency Comparator — event vs poll latency numbers
- Button Timeline — 5-second timeline of events vs polls
- Input Frequency Meter — live Hz histogram
- Axes Explorer — all analog axes + buttons
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗