Button prompts: universal placement glyphs (positions, no platform symbols) #2106

Closed
opened 2026-11-11 03:01:10 +00:00 by blessedplummer · 1 comment
blessedplummer commented 2026-11-11 03:01:10 +00:00 (Migrated from github.com)

Players on generic/unnamed controllers (and Steam Input remappers) get prompts labeled for someone else's buttons: Switch, Xbox, or PlayStation symbols that don't match what's in their hands.

Request: a universal prompt preset whose glyphs show button placement instead of symbols — e.g. face-button positions (top/bottom/left/right diamond), shoulder/stick positions — so every prompt reads correctly regardless of controller brand or remap. It would sit alongside the existing Switch/Xbox/PlayStation presets, not replace them.

Scope: the in-game prompts first; the sheet-music buttons (#1622) have the same problem and could share the set. No new input mapping needed — purely a glyph preset.

Players on generic/unnamed controllers (and Steam Input remappers) get prompts labeled for someone else's buttons: Switch, Xbox, or PlayStation symbols that don't match what's in their hands. Request: a universal prompt preset whose glyphs show button *placement* instead of symbols — e.g. face-button positions (top/bottom/left/right diamond), shoulder/stick positions — so every prompt reads correctly regardless of controller brand or remap. It would sit alongside the existing Switch/Xbox/PlayStation presets, not replace them. Scope: the in-game prompts first; the sheet-music buttons (#1622) have the same problem and could share the set. No new input mapping needed — purely a glyph preset.
NotRexed commented 2026-11-11 21:25:10 +00:00 (Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2504, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2504 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.

Thanks for the report. Reports of the same problem are now collected in #2504, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2504 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#2106
No description provided.