This is the evidence-led update tracker for How Many Dudes? base game, Steam AppID 3934270. It separates a release milestone from a support advisory, a patch or hotfix, a prelaunch feature announcement, and a roadmap statement. That distinction matters at launch: a new Steam post does not automatically mean the executable changed.
The base game entered Full Release on July 30, 2026. The official Store and News Hub do not publicly state a full-release semantic version in the material checked on 2026-08-01. Old labels such as v0.1.41-rc.13 appear in the News Hub’s Demo history and must not be attached to the released base game.
Current verified status
The newest official item observed is the July 31 notice about a launch error affecting some non-English users. It gives a Windows 11 Smart App Control workaround. This tracker classifies it as a support advisory, not a named patch, because the post does not say a new build was deployed.
The July 30 post is the release milestone. It confirms the game is out and says the developers expect improvements and quality-of-life work while gathering feedback. It does not publish a committed roadmap, delivery date, or patch cadence. Future work should be recorded here only after the team gives it a concrete official status.
The Store currently describes a base game with 42 roster Dude Types across six Families, hundreds of Relics and Trinkets, three challenge Tiers, Daily Dude and Ensemble Mode, Steam achievements, Steam Cloud, Family Sharing, and Steam Timeline. These are current product facts, not a list of changes attributed to the July 31 advisory.
How this timeline is classified
Release means the base product or a separately identified product became available. Patch or hotfix requires evidence that game code or data changed. Support advisory gives troubleshooting guidance without necessarily changing a build. Feature or compatibility announcement describes support planned or available around launch. Roadmap requires a concrete developer commitment; an intention to listen and plan is not enough.
Every entry below names its type and links the official timeline used to verify it. When one News Hub page contains several products, the summary states whether the claim belongs to AppID 3934270, Demo AppID 4248000, or a device-specific support context.
2026-07-31 - Non-English Windows launch error advisory
Type: Support advisory
Butterscotch Shenanigans reported a launch error affecting non-English users and directed affected Windows 11 players to turn off Smart App Control through Windows Security. The post presents a workaround; it does not identify a new semantic version, BuildID, patch, or permanent code fix.
- Applies to the described non-English-user launch prompt, not every crash or performance problem.
- Changes a system-wide Windows security feature, so players should read Microsoft’s current Smart App Control documentation before acting.
- The related evergreen page is the Launch Errors guide, which includes the security tradeoff and escalation packet.
Source: Official How Many Dudes? Steam News Hub
2026-07-30 - How Many Dudes? entered Full Release
Type: Release milestone
The official launch post announced that How Many Dudes? was available. It described the project as a deep, strange roster-building game and directed players to the base Store page. The Store identifies the canonical product as AppID 3934270 and lists Butterscotch Shenanigans as both developer and publisher.
- Full Release is the correct lifecycle label; the public post does not call the base build version
1.0. - The developer said feedback would shape improvements, quality-of-life work, and later plans, but did not promise named features or a schedule.
- Base-game facts should use the released Store, official Dudex, and current guide rather than importing Demo patch notes.
Source: Official How Many Dudes? Steam News Hub
2026-07-23 - Demo update and progress-transfer confirmation
Type: Prelaunch and migration notice
One week before release, the developer announced an updated Demo and confirmed that Demo progress would still carry into the full game. The post explicitly distinguished the Demo’s smaller Dude selection from the 42 Types planned for the full release.
- The transfer statement establishes a supported Demo-to-full-game relationship.
- It does not make Demo AppID 4248000 a source of current base-game balance or version labels.
- Players with a failed transfer should preserve both product identities and use the official migration path rather than copying unverified files.
Source: Official How Many Dudes? Steam News Hub
2026-06-18 - Steam Deck input and cloud announcement
Type: Device compatibility announcement
The developer described an official Steam Input profile for Steam Deck, with an on-screen cursor, mapped buttons, and touchscreen support. The announcement also said Steam Cloud and the developer’s Rumpus cloud service were intended to support movement between devices by launch.
- This is evidence for Steam Deck play and a developer-supplied input profile.
- It does not establish a native Linux build; the base Store publishes Windows as the native operating-system requirement.
- Current cloud-conflict behavior should be verified in the released client rather than inferred from a prelaunch promise.
Source: Official How Many Dudes? Steam News Hub
Product and version boundaries
The timeline’s primary scope is the base Game at AppID 3934270. Demo AppID 4248000 appears only where a transfer or historical comparison requires it. The Supporter Pack at AppID 4815310 and the downloadable Soundtrack at AppID 4769790 are separate products and should not be described as gameplay patches.
Steam bundles shown around the base Store are commercial groupings, not editions or release branches. Mobile releases and legacy browser demos are also separate platform contexts. A feature present there is not automatically a Steam base-game fact.
Do not turn SteamDB changenumbers or BuildIDs into player-facing version names. They can help detect that depot metadata changed, but only a developer post or public client label can supply an official patch name and scope. The current public semantic version remains NOT PUBLICLY STATED.
What the launch post does and does not promise
The July 30 announcement says the team expects a wave of improvements and quality-of-life features while it reviews feedback. It also says exact plans were not yet known and would be shared as they solidified. That is a posture statement, not a dated roadmap.
Accordingly, this hub does not list speculative balance changes, future Dudes, new modes, DLC gameplay, or a patch timetable. Community requests can identify demand, but they become update entries only when official evidence describes a change, support action, or commitment.
The July 31 item likewise remains a support notice until an official source says a changed build replaced the workaround. If a later post announces that outcome, it should receive its own dated entry and link back to the launch-error support page.
Maintenance rules for future entries
Check the official Steam News Hub and the developer’s How Many Dudes? blog tag. Confirm the calendar date, exact product, platform, and whether a build changed. Read the whole source rather than classifying from the title.
For a real patch, summarize player-visible changes by system and identify affected evergreen guides. Update a Dude, Relic, mode, or support page only when the patch materially changes its advice. Keep historical wording in the timeline while making the current guide accurate.
For a support advisory, state the exact symptom and risk of the workaround. For a release or related product, record the AppID and product type. For a roadmap item, distinguish committed work from exploration and preserve any date or uncertainty the developer gave.
Recheck volatile Store facts such as achievement counts or supported-language presentation when they are mentioned. Do not copy price, discount, review totals, or concurrent-player counts into evergreen update summaries unless the historical metric is central and dated.