Idea: Separate controller confirm/back mapping for menus from gameplay #1200
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1200
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported on Discord
Feature idea
Add an option to use the controller's A button as the select/action button and B as the exit/back button in menus, without swapping gameplay actions such as jump. The current swap changes gameplay too, so it doesn't meet this request.
Why?
Nintendo's A/B layout is opposite to common PC, Xbox, and PlayStation conventions. The reporter finds the existing global swap unsuitable because it would make jump use B.
Anything else
Related but distinct: Longshot #299 requests assigning JUMP as a separate button; this request is to separate menu confirm/back behavior from gameplay button mapping.
From Discord:
Clarification from the reporter: keep Link's action mapping exactly as it is; only change menu confirm/back so A selects/actions and B exits/back. In particular, don't alter gameplay actions such as jump.