Steam lists full controller support for Beast of Reincarnation, and Fictions’ PC requirements recommend a controller. Exact final keyboard, mouse, and Windows controller bindings were not published in the first-party evidence checked before launch. A trustworthy controls guide must therefore start from confirmed actions and fill the bindings from AppID 2001760’s live menu.
Console screenshots are not PC mapping evidence. The same action can use different glyphs, layouts, remapping layers, or prompts on Steam.
Build the action dictionary first
Confirmed combat concepts include Emma’s movement, katana and ranged actions, guard and parry, Koo’s Bloom Art menu, FP, target interaction, and the Down opening. Exploration material also shows plant-vine traversal and stealth or falling approaches. The public tutorial should supply the exact verb used for each action.
Record the game’s label before choosing a community shorthand. “Bloom Arts” and “Down Gauge” are official terms; renaming them as spells or posture can create mismatched searches. Note whether one input changes by context, such as an ordinary attack becoming the final Down prompt near a vulnerable target.
Capture keyboard and mouse bindings
Open the PC controls menu with keyboard and mouse active. Record default movement, camera, attack, ranged action, defense, Koo command, interaction, menu navigation, target handling, and any evasive or healing action the tutorial confirms. Then inspect whether each field is remappable and whether the game warns about conflicts.
Mouse sensitivity, inversion, acceleration, raw input, and separate aim controls belong in the settings record only when visible. Do not infer them from cursor behavior in a menu. If a binding changes across gameplay contexts, list the contexts instead of forcing one flat table.
Capture controller behavior separately
Connect one supported controller at a time and let Steam and the game identify it. Record the displayed glyph family, default layout, vibration option, stick settings, and remapping support. Full controller support means the product is intended to be playable with a controller; it does not guarantee that every brand displays native glyphs or that Steam Input is unnecessary.
If Steam Input changes the presentation, record whether it is enabled and which template is active. Test direct input and Steam Input only through reversible client settings. Avoid installing controller-emulation software merely to produce a label.
Practice the duo transition
The most distinctive control transition is from Emma’s real-time defense into Koo’s slowed command menu and back. Practice the parry action until the game confirms success and FP increases. Open the Bloom Art interface, move selection, choose a target or Art as required, observe any timing prompt, and return attention to Emma’s position.
This sequence exposes conflicts that a static layout misses: a shoulder input may open a layer, a stick may change menu selection, or a confirmation glyph may differ under another device. Record the entire interaction rather than only the first button.
Test prompt switching and accessibility
Move the mouse after using a controller and observe whether prompts switch cleanly. Check whether simultaneous input is supported, whether the active glyph flickers, and whether opening the command menu changes cursor behavior. These are test results for a device and build, not assumptions from the Store badge.
Inspect the accessibility and gameplay menus for hold/toggle options, timing assistance, camera controls, vibration, subtitle presentation, and any command-timing aid. Story difficulty’s more forgiving parry setting is documented, but it should not be confused with a separate accessibility option unless the menu labels one.
Diagnose an input problem by layer
First confirm Windows detects the device. Next check the Steam controller page for the active input layer. Then inspect the game’s selected device, glyphs, and bindings. Finally test the action in a simple area. This order separates hardware, Steam Input, game configuration, and combat timing.
For a keyboard failure, look for a conflicting remap or focus problem before deleting configuration. For a controller showing the wrong glyphs, record the physical model, connection type, Steam Input state, and displayed family. For apparent parry delay, first verify frame pacing and compare ordinary menu response; one missed combat input does not prove global latency.
Publish a controls table responsibly
Every row should include action, default keyboard/mouse input, default controller input, context, remappable status, and tested version. Use an em dash for genuinely unbound actions and “not yet checked” for incomplete evidence; those states are different. Include screenshots only from the same public PC build and avoid copying a console article’s icons.
Retest after updates that mention input, controller, UI, or accessibility. Preserve an older table’s version instead of silently mixing new bindings with old descriptions.
Control-support evidence
The Steam Store listing provides the full-controller-support badge, while Fictions’ official requirements state that a controller is recommended. Official combat descriptions establish the action vocabulary. No complete final Windows binding chart was available before launch, so exact key and button claims await direct public-build capture.