Butterscotch Shenanigans published an official Steam Deck announcement on June 18, 2026. It explains that How Many Dudes? was designed around clickable interfaces and supplies an official Steam Input profile for controller-style play. The profile retains an on-screen cursor, maps the A button to clicking and the B button to going back, and can be used alongside the Deck touchscreen.
This is device-compatibility evidence, not a native Linux claim. The base game’s Store requirements list Windows 10/11 as the native operating system and do not publish a native SteamOS or Linux requirement.
Start with the official input profile
Open the game’s controller-layout screen in Steam and select the developer-provided or official layout before creating a custom map. Confirm that the active layout belongs to How Many Dudes? AppID 3934270 rather than the Demo or a community profile with a similar name.
Test the basic navigation described by the developer: move the cursor, click a visible UI element with A, and return with B. Then open a Dude, Stat, Relic or referenced term. The game’s information model depends on clicking detailed UI, so a layout that only starts battles is incomplete.
If the official layout is missing, record the Steam client channel, SteamOS version and active compatibility selection. Restart Steam and check the layout again before overwriting controls. A custom profile can be a temporary test but should be labeled as such in a support report.
Choose touchscreen or cursor by task
The announcement explicitly supports touchscreen use and describes the interface as naturally clickable. Touch is useful for large buttons and direct inspection. Cursor controls can be more precise for small tooltips, densely packed Relics or UI elements near screen edges.
Test each input method separately. If touch opens an element but A-click does not, the problem is likely mapping or cursor focus rather than the whole screen. If neither works on one specific element, record the menu and target.
Avoid changing many bindings at once. Reassign one control, verify the result, and keep a copy or screenshot of the official layout. This makes it possible to restore the developer baseline after an experiment.
Preserve clickable detail during a run
The developer guide encourages clicking unfamiliar Stats, icons and terms, and the Deck announcement explains why a cursor remains present. Use that detail access before binding a Trinket, choosing a Relic, or interpreting a boss modifier. Handheld play should not turn a readable decision into a guess.
Increase UI scale only through the current game or Steam controls and verify that tooltips still fit. Test a menu before a critical battle so a scale or resolution change does not hide a purchase or target.
When a dense late-run Relic row becomes harder to select, compare touch and cursor rather than repeatedly clicking. Record which method and UI element fails if official support needs a reproduction.
Treat SteamOS as compatibility, not native support
The native requirement block on the Store lists Windows, a 64-bit processor and OS, DirectX 11, and Windows-focused minimum hardware. Running on Deck through Steam’s compatibility environment does not rewrite that product statement.
Do not publish Windows file paths, Windows 11 Smart App Control steps, or driver instructions as if they apply directly to SteamOS. The July 31 non-English launch advisory is a Windows 11 route. A Deck launch issue needs SteamOS, compatibility selection, client and AppID context.
Likewise, a Deck success does not prove generic Linux-distribution support. The official announcement is specific to Steam Deck input and play. Other Linux environments may differ in runtime, display, storage and input behavior.
Handle cloud state carefully
The June announcement said Steam Cloud and the developer’s Rumpus cloud service would be available by launch for moving between Deck and other devices. The released Store currently lists Steam Cloud. That supports a cloud feature claim but not every conflict, merge, or cross-platform direction.
Before moving between devices, let the current session close cleanly and allow Steam to finish synchronization. If Steam displays a conflict, stop launching on both devices and identify the last known-good progress and timestamp before choosing a copy.
Do not delete local data merely to force a sync. Ask official support for the current storage and backup procedure, especially when Demo progress transfer or another platform is involved. Keep AppID 3934270 distinct from Demo AppID 4248000.
Test docked variables one at a time
Confirm the game in handheld mode first. Then attach the display and test resolution and scaling. Add the external controller or keyboard after the picture is stable. This separates display negotiation from input order and layout problems.
If an external controller takes the wrong slot or loses the cursor action, reopen the active Steam Input layout and verify device order. Do not assume a layout built for the Deck controls maps every external controller identically.
For an unreadable or cropped UI, record display resolution, refresh context, game display mode and whether returning to handheld restores the screen. Avoid forcing unsupported launch flags from an unrelated game’s guide.
Send a Deck-specific report
Begin with AppID 3934270, Steam Deck model, SteamOS version, Steam client channel, compatibility selection and active Steam Input layout. State whether the issue occurs with touchscreen, trackpad/cursor, A-click, an external controller or all methods.
Include the exact screen and smallest reproduction sequence. For a launch problem, say whether a process or window appears. For cloud state, include device order and last known-good progress without posting account credentials or private tokens.
Check the current official Steam News Hub before reporting. A later input profile or compatibility post should supersede the June announcement, while the native-platform boundary remains controlled by the Store requirement page.