This Updates hub is the dated record for the Low-Budget Repairs base game. It currently has no approved child patch pages because the product is still coming soon and no public semantic version label has been established. The timeline below uses official Steam sources and keeps the Demo AppID separate.
Current release status
The official store page lists Low-Budget Repairs for release on 2026-08-13 and says the base game is not yet available. The latest official community feed gives the unlock time as 17:00 CEST. These values were checked 2026-08-09 and should be rechecked when the release window arrives.
Demo milestone
The official feed announced that the free Demo became available on 2026-07-24 and links AppID 3642880. Demo availability is an update event for the related product, not evidence that the base game launched. A future update entry should label the AppID in its title or metadata.
Price and wishlist challenge
The 2026-08-08 announcement stated a $19.99 price and described discount milestones tied to wishlists. It also reported 1,120,000 wishlists at that time. These are dated announcement values, not permanent price or player metrics. The announcement must be linked whenever those numbers are repeated.
Earlier development communication
The 2026-06-26 announcement gave the concrete release date after a delay and said the story was complete while technical polishing continued. The 2026-04-14 Devlog described completed storylines, characters and locations and ongoing bug fixing and system behavior work. These posts are useful historical context; neither establishes a public version number.
How this hub is maintained
Check the official Steam store update history and Steam Community announcements. Record the date, headline, AppID, release state, branch or version when officially stated, platform scope and a short original summary. Do not turn every trailer or wishlist post into a patch note.
For each future item, keep a compact record of what changed for a player and what did not change. Separate store metadata, a developer announcement, a Demo event and a released patch so the history remains searchable without implying a mechanic that the source never described. This distinction matters during the launch transition, when a planned date can coexist with an unavailable base game.
Reader checklist
Before acting on a date, open the linked official post. Confirm whether it applies to the base game or Demo. Check the current store page for changes to release state, price, requirements and features. If a community source reports a hotfix, wait for an official confirmation or label it as community reported with the observed build.
FAQ
Is there a public version number?
Not in the sources checked for this audit. Do not use SteamDB changenumbers or BuildIDs as semantic versions.
Is the Demo the base-game update?
No. AppID 3642880 is a separate Demo product.
Where should patch notes go?
Here after an official patch or hotfix exists and the article can state its date, scope and source.
Timeline record
On 2026-06-26, the official feed announced the 2026-08-13 release date after the team needed more time for technical polish. The post said the story was complete while code still needed final work. This is a release-state explanation, not a public version label.
On 2026-07-24, the official feed announced the free Demo and linked AppID 3642880. The announcement described the beginning of the story and unique characters and problems. Keep this item under the Demo scope whenever a future timeline turns it into a dedicated entry.
On 2026-08-06, the feed described one week until launch and repeated the 2026-08-13 date. On 2026-08-07, it linked the release trailer. On 2026-08-08, it stated a $19.99 price, a 17:00 CEST release time and a wishlist discount challenge. These items are official announcements checked 2026-08-09 and should retain their dates.
How to add a patch entry
Use a patch child only when an official post states a patch, hotfix or released change with enough detail for a substantive page. Include the headline, date, base-game or Demo AppID, public version if stated, branch when relevant, platform and a short original summary. Link the source close to the claim.
Do not call a trailer, wishlist milestone or translation request a patch. Those are announcement types with their own maintenance meaning. Do not infer a future roadmap from a sentence that only says the team is polishing.
Check the launch transition
When the store changes from Coming Soon to available, update the release-state copy and add the official unlock evidence. Recheck price, system requirements, feature labels and supported languages. Keep pre-release pages as dated launch context if they still help players understand the Demo/base-game boundary.
Reader questions
Where is the current source?
Start with the official Steam store and Community All News pages linked below. A third-party countdown is not a release authority.
Does a wishlist number belong in an evergreen guide?
Only as a dated announcement note. It is not a permanent game mechanic or player-count measurement.
What if an official page and a community post disagree?
Use the official current page for identity, release and feature facts. Preserve the community observation as such only when it has an exact date and product scope.
Sources: https://store.steampowered.com/app/3167920/LowBudget_Repairs/ and https://steamcommunity.com/app/3167920/allnews/ (checked 2026-08-09). This is a zero-child substantive hub; no update cadence or future patch is inferred.
This chronology is intentionally factual and compact. It gives the reader a dated source trail without claiming that the announced launch time, price, wishlist count or Demo behavior will remain unchanged.
The next maintenance pass should check the official page again after the planned launch and only then decide whether a substantive patch child is justified.