Systems / 8 min read
SpiritVale Controller Support Guide
The official 0.16 update says players can switch between Auto, Keyboard & Mouse, and Controller schemes in Settings. Auto switches based on the last input, and controller hotkeys can be rebound separately. Steam's own store metadata and handheld compatibility report now corroborate that framing, so this guide turns the confirmed statements into a setup routine you can repeat after any patch, and it separates what the developer documented from what it did not.
Start from the three documented schemes
The official 0.16 announcement names exactly three input schemes you can select in Settings: Auto, Keyboard & Mouse, and Controller. That list is the whole of what the announcement confirms about scheme selection, so treat anything beyond it — a scheme name, a preset, a per-class profile — as unconfirmed until you see it in your own client. The practical consequence is simple: begin in the scheme you expect to use for most of your play, not the one that looks most convenient for a single activity. A player who raids with a controller but manages inventory with a keyboard should start in the Controller scheme and add a keyboard fallback for menus, rather than starting in Auto and hoping it behaves consistently.
Understand what Auto actually does
The same announcement says Auto switches based on the last input. That is a behavioural description, not a rule about edge cases. In practice it means the game infers your intended scheme from whichever device you touched most recently, so a stray mouse nudge in the middle of a fight can hand control to the keyboard-and-mouse scheme without you asking for it. If you are mid-encounter and the character stops responding the way you expect, check which scheme is active before you assume the problem is a bug, a lag spike or a broken keybind. Players who share a desk with a mouse, or who use a trackpad for chat, are the most likely to trigger this accidentally. Choosing Controller explicitly removes that ambiguity for the session.
Rebind hotkeys before a group activity
The announcement says controller hotkeys can be rebound separately. That is the single most useful sentence in the note for anyone who has ever fumbled a defensive cooldown. Rebinding is a preparation task, not a reaction to a problem, and it is cheapest to do before a party session rather than during one: a group that has already pulled is the worst time to discover that your recovery skill sits under a chord you have to look down to find. Work through your keybinds in the order you actually use them — movement, primary attack, the skill you press under pressure, the skill you press when something goes wrong — and confirm each one in a low-stakes location before you commit to content that punishes a mistake.
Autotarget changes how you commit to a fight
The 0.16 announcement says an autotarget system was added for controller users. Positioning still decides which enemy is in range of you, but the assist decides which of those candidates your ability lands on, and that difference matters most in packs of mixed enemies. If you have been playing keyboard-and-mouse and switching to a controller for a boss, expect your first attempts to feel looser: you are handing over one targeting decision you used to make manually. The useful habit is to test the assist in an ordinary map before taking it into a group encounter, and to notice whether it prefers the target closest to you, the target you last hit, or the target threatening the group. Record what you observe alongside the patch version; a later rebalance can change what that observation means.
The one limitation the developer stated
The official note is explicit that most functions work with a controller but UI navigation is not supported yet. That single sentence explains the failure mode most players report first: combat feels fine and then a menu will not respond. It also tells you the correct response. Do not treat a stuck menu as evidence that controller support is broken generally, and do not rebuild your keybinds chasing it. Keep a keyboard and mouse within reach for inventory management, vendor screens, party settings, trade windows and anything else that depends on cursor navigation, and return to the controller when you are back in the world. Because the note is version-specific, this limitation is exactly the kind of statement a later patch can quietly remove — recheck a newer official post before assuming it still applies.
A repeatable setup routine
Combine the documented pieces into one pass you can run after every update. First, open Settings and confirm which of the three schemes is selected, rather than assuming your choice survived. Second, walk your rebound hotkeys in the order you use them and confirm the ones that matter under pressure. Third, spend a few minutes in a familiar, low-risk area so you can feel whether autotarget is picking the targets you expect. Fourth, open one menu with the controller and one with the keyboard, so you know the UI-navigation limitation is still the only gap. Fifth, note the patch version and the date beside anything you changed. The routine takes minutes, and it is the difference between an input problem you can describe precisely and one that just feels wrong.
What Steam's own store metadata declares
Steam's app metadata for SpiritVale carries two controller categories rather than a blanket claim: Partial Controller Support and DualShock Controller Support. The same payload lists Windows as the only platform. Those are store-level declarations made through Steamworks, and they are independent of the 0.16 patch note, which makes their agreement worth something — the word is partial, not full, and that is the store page telling a buyer to expect the same shape of support the patch note describes. Read the category list for what it contains rather than for what it omits. Steam lists the pad families the developer declared; a pad that is not named there is undocumented, which is a different thing from unsupported, and no public source on this page settles the question either way.
The Steam Deck verdict, and the caveats behind it
Steam's compatibility report resolves SpiritVale to Playable on Steam Deck rather than Verified, and it returns individual test results behind that single word. Two of those results are returned as passing — the default configuration is fully functional and it performs — while the report also returns a set of caveats: the default controller configuration is not fully functional, controller glyphs do not match the Deck device, text input does not automatically invoke the keyboard, interface text is not legible, and external controllers are not supported for the primary player. Three of those are the same story the patch note told from the software side: a working default configuration with an interface layer that trails behind it. The practical reading is that handheld play works, and that typing and reading small interface text are the two things you should plan around rather than discover mid-session.
Turning the caveats into a setup decision
Put the two sources side by side and the routine gains a sharper shape. Choose Controller or Keyboard and Mouse explicitly instead of leaving Auto to guess, because the Deck report already documents an interface layer that does not follow input smoothly. Keep a keyboard within reach for chat, naming and menus — the report's note that text input does not automatically invoke the keyboard is the same constraint seen from the hardware side, not a separate defect. Expect glyphs that do not match the device in front of you; when a prompt shows a button your pad does not have, translate it against your own layout instead of concluding that a binding is broken. And treat an external pad on a handheld as a secondary input, because the report states it is not supported for the primary player. None of that changes the combat experience, and all of it removes a category of false bug reports.
What to report, and what not to claim
If a controller action fails, the useful report names the scheme that was active, whether Auto was involved, the exact rebinding in effect, the activity or menu, and the patch version. That is enough for another player to reproduce. What is not useful is a general statement that controller support is broken, or an assertion about a hidden setting, because the official note only ever confirmed three schemes, separate hotkey rebinding, an autotarget assist and the UI-navigation gap. Keeping your report inside those documented bounds makes it far more likely that someone can act on it — and it keeps this page honest about the difference between what the developer published and what the community happens to have noticed.
Frequently asked questions
Does SpiritVale officially support controllers on Steam?
Steam's store metadata for SpiritVale carries the Partial Controller Support and DualShock Controller Support categories, and the official 0.16 note describes Controller as one of three input schemes selectable in Settings.
Is SpiritVale playable on Steam Deck?
Steam's compatibility report resolves SpiritVale to Playable, and lists caveats including controller glyphs that do not match the Deck device and text input that does not automatically invoke the keyboard.
Which input schemes does SpiritVale officially support?
The official 0.16 announcement names three schemes selectable in Settings: Auto, Keyboard & Mouse, and Controller. It does not describe any additional preset.
Can controller hotkeys be rebound?
Yes. The official 0.16 note says controller hotkeys can be rebound separately from the keyboard-and-mouse scheme.
Why does my controller work in combat but not in menus?
The official 0.16 announcement says most functions work with a controller while UI navigation is not supported yet. Keep a keyboard and mouse available for menu screens.
What does the Auto scheme do?
According to the official 0.16 announcement, Auto switches based on the last input you made, so touching a mouse or keyboard hands control back to that scheme.