How Many Dudes? Support Guide

This support hub is for the How Many Dudes? base game, Steam AppID 3934270. The official Store lists native Windows support; Steam Deck play has separate developer evidence and should not be described as a native Linux release. Keep that boundary clear when reporting a problem because a Windows launch block, a Proton or Steam Input issue, and a transferred demo-save problem require different evidence.

For the current non-English Windows launch advisory, go directly to Launch Errors. The official July 31 notice recommends a Smart App Control setting change for an affected error, but that setting is part of Windows security. Read the security tradeoff before acting.

Confirm the product and platform first

Open the Steam Library properties and confirm the base game is AppID 3934270. The Demo is a different product, AppID 4248000. The Supporter Pack and Soundtrack are also separate content products. A fix or save location for one should not be assumed to apply to another.

The base Store page lists Windows 10 or 11, a 64-bit processor and operating system, DirectX 11, 500 MB of available storage, 2 GB RAM, and graphics with 512 MB VRAM. Treat those as the current published minimums checked on 2026-08-01. They establish native Windows scope, not native macOS or Linux support.

Record the operating-system edition and build, whether Windows is 64-bit, the GPU and driver version, the Steam client channel, display mode and resolution, and the exact time of the failure. A screenshot of an error is more useful than paraphrasing it, especially when Windows security names a file or publisher.

Use a reversible Windows triage sequence

Restart Steam and the computer first so a pending client or operating-system state is not mistaken for a persistent game problem. In Steam, open the game’s installed-file controls and verify the installed files. Then launch once without third-party overlays or capture tools that you can safely close and restore.

If the game opens, change one variable at a time. Test the normal display mode before changing resolution or combat speed. Re-enable optional overlays individually. This preserves the evidence needed to identify the conflict instead of producing a working state with an unknown cause.

Do not download replacement executables, DLL bundles, save editors, or “fix packs” from an unaffiliated site. Do not add broad antivirus or firewall exclusions as a first step. If Windows names a security feature, follow the current Microsoft documentation and the specific developer advisory, then decide whether its tradeoff is acceptable.

If the exact failure is the post-launch issue affecting some non-English Windows users, use the dedicated Launch Errors guide. The July 31 post is a support notice, not proof of a semantic-version patch or a permanent fix.

Separate crashes from launch blocks

A launch block occurs before the game becomes usable and may show a Windows security message. A crash begins after the process opens and may be tied to a particular menu, round, display change, or interaction. Performance degradation means the game continues but frame pacing, input response, or simulation speed worsens.

For a crash, reproduce once with a short clean sequence and record the last visible action. Note whether it recurs on the same save or mode and whether a new run reaches the same point. Avoid repeatedly opening a save if every attempt appears to damage or overwrite it.

For performance, lower one display or optional visual setting at a time and close unrelated high-load applications. Record the round, team, visible enemy scale, and whether the slowdown disappears after the battle. Community reports can suggest experiments, but they are not evidence of a universal base-game defect.

When contacting Butterscotch Shenanigans, include the base AppID, operating-system build, hardware summary, exact reproduction steps, expected result, actual result, and timestamp. Attach logs or diagnostic files only through the developer’s official support route and review them for personal information first.

Handle saves and Steam Cloud conservatively

The Store lists Steam Cloud for the base game. The developer’s Steam Deck announcement also discussed Steam Cloud and the Bscotch Rumpus cloud service ahead of launch. These facts do not establish every cross-platform direction, merge rule, or conflict-resolution behavior.

Before troubleshooting a sync conflict, stop launching the game on multiple devices. Record which device has the newest known-good progress and its last-played time. Do not choose a cloud or local copy merely because its file timestamp is newer if the client also shows recognizable progress information.

The official July 23 announcement states that demo progress can transfer into the full game. That is a documented migration relationship, not permission to manually copy arbitrary files between AppIDs. Use the in-product or official flow and keep the Demo and base-game identities distinct when reporting a failed transfer.

This page does not publish an unverified save path. Storage can differ between Steam userdata, the game’s own service, Windows profile data, and later client changes. Use the official support response or a current diagnostic path shown by the game before editing anything, and make a backup before a developer-directed file operation.

Understand Steam Deck scope

The June 18 developer announcement says How Many Dudes? can be played on Steam Deck with an official Steam Input profile. It describes the game’s clickable interface, controller mappings that retain an on-screen cursor, and touchscreen use. This is valuable device-specific support evidence.

It is not evidence of a native Linux build. The base Store requirements publish Windows as the native operating system. A Deck session may involve SteamOS compatibility technology, and its troubleshooting steps can differ from native Windows even when the same Steam account and cloud features are involved.

On Deck, confirm the official controller layout is selected before remapping everything. Test the touchscreen and trackpad/cursor behavior separately. If a UI action fails only under one input method, report the exact control and screen rather than describing the whole game as lacking input.

For docked use, separate display and input variables. Test handheld once, then connect the external display, then attach the controller or keyboard. This makes resolution negotiation, controller order, and input-profile errors distinguishable.

Protect the evidence before resetting anything

Avoid reinstalling as the first response. Verification, a clean launch, and a focused reproduction produce more information while preserving state. Reinstallation can change timestamps and cached data without addressing a cloud conflict or Windows security decision.

Before a reset or reinstall that official support asks for, capture settings, save/progression status, account identifiers that are safe to share, and the exact error. Back up only the files the official instructions identify. Never post access tokens, full account cookies, email passwords, or private crash data publicly.

If a proposed step changes a system-wide security control, pause and understand its scope. Smart App Control is not a per-game graphics toggle. Microsoft describes it as protection against untrusted, malicious, or potentially unwanted software, so the benefit of launching one application must be weighed against the wider Windows change.

Escalate with a compact support packet

A useful report starts with: “How Many Dudes? base game, AppID 3934270, Full Release, Windows build X.” Add whether Steam file verification passed, whether the issue occurs on a new run, and the smallest sequence that reproduces it. Include the exact message as text plus a screenshot if possible.

For a save issue, add the source product or device, target product or device, last known-good time, and whether the client presented a conflict dialog. For Steam Deck, add SteamOS/client version, compatibility selection if changed from default, and the active Steam Input layout.

Check the official Steam News Hub before submitting because a dated advisory may already classify the issue. Do not label a support notice a hotfix unless the developer says a build changed, and do not attach old Demo version labels to the full-release base game.

Sources

• How Many Dudes? on Steam - AppID 3934270
• Official How Many Dudes? Steam News Hub
• Official How Many Dudes? site
• Microsoft Smart App Control FAQ