Legacy Edition officially lists full controller support, gamepad recommendation, and DualSense support over USB and Bluetooth. Start with one controller and Steam’s default input behavior, verify every essential action in Bree, and only then add a second pad for split screen. Duplicate mapping layers are the most useful first suspect when two devices control the same player or one press fires twice.
Single-pad baseline
Connect before launch and test sticks, camera, confirm, cancel, pause, target lock, evade, and hero actions.
Steam Input
Use the default first; change the per-game override only when a reproducible device problem requires it.
DualSense
Both USB and Bluetooth are listed, but prompts and advanced effects should be verified on the current connection.
Second controller
Add it after player one is stable, confirm device order, then use the current split-screen join prompt.
Prove one controller works end to end
Connect the device before starting Steam and confirm it appears once in controller settings. Launch AppID 2523770, navigate the main menu, and enter Bree. Test movement and camera independently, then confirm block or evade, target lock, attack inputs, interaction, pause, and character interfaces.
Do not start by importing a community layout for the retired original game. Legacy Edition advertises refined target locking and its own controller support. The current default is the correct baseline unless a specific input fails.
If button prompts do not match the physical pad, note whether input still works. Glyph mismatch and missing input are separate faults.
Resolve double input and wrong player assignment
Close third-party remappers, virtual-controller tools, and duplicate per-device profiles. Steam Input plus another mapper can present one physical controller twice. Restart Steam after removing the extra layer and retest the menu.
For split screen, connect player one’s pad first, then player two’s. Verify Steam sees distinct devices before launching. Use the game’s join prompt and check that the second device controls a different hero. If both move player one, return to the menu and fix device order instead of continuing into a chapter.
Avoid unplugging devices while the game is saving. Reconnection can change seat order; confirm both heroes again after any resume.
Choose a Steam Input override only for evidence
Open the game’s Properties → Controller page and record the current per-game setting. Try one override at a time: default, enabled, or disabled as appropriate for the detected device. Restart the game between meaningful changes so the result is unambiguous.
Use a standard template only when the native mapping fails and the template exposes all essential actions. Check target lock, camera, and menus; a layout that moves correctly but cannot manage inventory is not complete controller support.
After finding a working mode, capture the setting and return global Steam options to their prior state if they were changed during diagnosis.
Test DualSense wired and wireless separately
The store page lists DualSense USB and Bluetooth support. Pair or connect one method, confirm the device identity in Steam, and complete the single-pad baseline. If advanced effects, glyphs, or vibration differ, describe that as connection-specific behavior rather than saying the controller is unsupported.
Bluetooth instability should be separated from game mapping: test battery, distance, interference, and reconnection in Steam before altering the in-game layout. Wired USB is a useful comparison because it removes radio conditions.
Do not assume PlayStation-style prompts are guaranteed simply because DualSense input is accepted. Verify the current public build.
Preserve controls for co-op and troubleshooting
Once both pads work, enter a safe local session and test independent pause and inventory behavior before traveling. Increase readable UI options where available for split-screen. Save the controller configuration only after every required action is covered.
For an unresolved issue, report device model, connection type, Steam Input override, other mapping software, current public branch, and the exact missing or duplicated action. That is enough for support to reproduce without exposing personal system data.
See Local Co-op for the shared-screen session and Steam Deck for Proton-specific input context.