Skip to content

boneyard: mobile input redesign — 12+ command keys, and q-quaff violates the q-means-Back reservation #53

Description

@BCook98

Boneyard reads w/a/s/d + arrows (movement), >/< (stairs), l/f/e (bones), q/r/g/c/b/m (items/UI), and contextual digits 1–9 (gate kits, shop, dying words). Two problems from the 2026-06-11 catalogue controls audit:

  1. Touch: declaring 12+ controls (kit v2.10.0) overflows the deck's chip row — playable but cluttered. The game wants a designed mobile input scheme (e.g. context-sensitive actions on Confirm — loot/respect/descend depending on the tile — which would also reduce desktop key load).
  2. q = quaff violates the platform controls convention that q means Back in every context except text entry. A keyboard player pressing q expecting to back out drinks a healing draught instead. Worth fixing regardless of mobile: move quaff to another key.

Arrows already work for movement, so the game is partially touch-playable today; it ships accepted-degraded in v1 of the mobile-controls work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions