Wyldheart is not yet a released base game. Its Steam base listing, AppID 3642910, remains marked “Coming soon,” while the currently playable public client is the separate Demo AppID 4475270. This page keeps dated demo patches, server changes, and release statements in one place without turning a demo hotfix into a full-game promise. It is also the complete Updates hub for the current guide pilot, so there is no child page hidden behind this navigation item.
The public demo was released on October 8, 2026 and reached version 0.7.2 the next day. The official patch posts add a Steam client build marker beginning with CL, such as CL39302 or CL39317. That marker identifies a particular shipped client revision; it is not another Steam AppID, a new product edition, or the version of the unreleased base game.
Current status at a glance
Official update timeline
2026-10-09 - Demo Hotfix 0.7.2 CL39317
Type: Demo client and online-service reliability hotfix
Source: Official Wyldheart Steam news feed
- The developer reported improvements to login and reconnect reliability.
- Server-side work was described as preparation for greater capacity under launch demand.
- The post belongs to public Demo AppID 4475270, even though it appears in the base game’s Steam community feed.
- CL39317 is the client build marker. The player-facing demo version remains 0.7.2.
For players, this is a reason to update before comparing connection failures. It is not proof that all capacity issues disappeared, nor a final statement about the base game’s eventual network architecture. If a fresh client still cannot log in, record the UTC time, region, exact message, whether solo reaches the campaign, and the official status shown at that moment.
2026-10-09 - Demo Hotfix 0.7.2 CL39302
Type: Demo lobby, saving and access hotfix
Source: Official Wyldheart Steam news feed
- The lobby join code was made visible so a host could share the actual current code.
- The Online Save checkbox was corrected to behave as intended.
- Players blocked by online connectivity received a route to continue with saving disabled.
- The developer explicitly warned that offline demo progress does not save and disappears when the session ends.
This update changes two common support answers. A join code belongs to the active lobby and is shared privately; it is not a Steam key or permanent invitation. The offline checkbox is also not a recovery tool for a valuable campaign. It lets a player test or explore without persistence. If progress matters, wait for services, leave online saving enabled, and confirm the current hotfix before committing to a long run.
2026-10-08 - Public Steam Demo Launch
Type: Separate public demo release
Source: Official Wyldheart Steam news feed
- The standalone public demo opened through Steam without requiring the older Kickstarter beta entitlement.
- Official material identifies four playable ancestries, 19 backgrounds, The Slurper’s Den opening, Rivermere, the Whisperwoods region, and additional demo dungeons.
- Parties can contain up to four players, with solo play also supported.
- Demo saves will not transfer to the future full game.
The launch defines a public evidence boundary. Reports from March preview sessions and the older beta can explain design direction, but a current instruction should be reproduced on this demo before it is presented as live behavior. The launch announcement does not provide a final demo end date, a base-game release day, or permission to carry demo saves forward.
How to check whether an update applies to you
Start with the Steam product you launched. The base store URL contains /app/3642910/, but its Download Demo action installs the related demo client. A report for Beta AppID 3643050 is not automatically a demo report. WILD HEARTS, AppID 1938010, is an unrelated game and should never supply Wyldheart patch notes.
Next, read the version displayed by the active client and allow Steam to finish updating. If an official note includes a CL number, record it exactly when available, but do not replace the public version with it. Finally, separate a client patch from service state. A client can be current while a regional login or capacity problem is still active, and a server-side improvement may take effect without introducing a new visible game version.
Use the Tech hub when an issue needs local diagnosis. Use Co-op when the current client launches but a party cannot join. For demo access, identity, save limits, and the playable slice, start with the Demo Guide.
A safe update routine
Before updating, finish an interaction and return to a stable state if the client allows it. Exit the game normally, let Steam complete the download, then relaunch. Confirm the visible version before changing graphics, input, network, or save settings. Testing one variable at a time preserves a useful comparison.
If the patch targets online services, inspect the official status page before verifying local files or reinstalling. When the service is healthy and the problem persists, restart Steam and the demo, verify installed files, and reproduce the shortest failing path. Record the product AppID, public version, build marker if published, Windows version, region, UTC time, party size, and exact error. Remove lobby codes, account names, local usernames, and private messages from screenshots.
Avoid deleting a save or configuration folder based on an unverified path. The demo’s online-saving behavior and temporary offline mode make casual “reset everything” advice especially risky. If the developer requests logs, follow the current official support instructions and keep a copy until the report is acknowledged.
What has not been confirmed
The Steam listing does not publish a fixed base-game release date. The official site has described an Early Access aim, but a target window is not an appointment. Final system requirements, optimization, controller polish, Steam Deck status, server capacity, language coverage, character options, balance, and save handling can all change before release.
There is also no basis for treating the two October 9 client builds as base-game patches. They document rapid work on the public demo after launch. Likewise, a successful offline session does not prove that an offline campaign can be preserved: the official warning says the opposite for the demo.
When this page will need revision
Recheck this hub whenever Steam changes the base listing, the official news feed posts a new client version, the status page names an incident, or the public demo becomes unavailable. At Early Access, establish a new product-and-version boundary before carrying any instructions forward. The first questions should be whether the base game uses the same AppID, whether demo saves remain excluded, what the displayed release version is, and which technical requirements or multiplayer assumptions changed.
Older entries should remain dated rather than silently rewritten into current advice. A timeline is most useful when it preserves what applied to which build while the summary and cross-links point players to the active answer.