First Light: Betocsin
README.md
console
The controls a CARD answers to: the title, the how-to handbill, the pause card and the two end cards.
It is live exactly while a card is up. game/screens/Screens.component
activates it the instant one goes up and releases it when the last one comes
down, and it stands the whole player group down while it holds — so one press
means one thing and the crane cannot be dropped through a menu.
| Control | Keyboard | Controller |
|---|---|---|
navigate | arrow keys | left stick |
navigateAlt | W / S | d-pad |
confirm | Enter, Space | A (south) |
back | Backspace, Esc | B (east) |
resume | Esc, P | Start |
An axis2 evaluates one binding per device class, so no single control can
carry both the arrows and W/S, or both the stick and the d-pad. navigateAlt
is the other half of each pair, and the screens feed both into one focus ring.
None of the five declares a touch binding. On a phone the card's own rows ARE the control: a tap points the focus at a row and confirms it in one gesture, and an on-screen stick over a menu would be a second, worse way to do what the finger is already touching.