What SteamDB can confirm
SteamDB can be a convenient way to look up a Steam app once its official ID is known. It is not operated by Gray2RGB, the publishers, or Valve for the purposes of this source policy. That means a SteamDB page should not replace the official Steam listing when an article makes a claim about the game.
Official Steam identifiers
Valve's metadata for Low-Budget Repairs identifies the full game as app 3167920. The separate demo is app 3642880, and its metadata connects it to the full game. These IDs are the safest bridge between an official Steam page and a third-party reference page.
Store facts from the official listing
The Steam listing names Gray2RGB as developer and Simplicity Games and PlayWay S.A. as publishers. It describes a first-person, single-player renovation simulation set around 1990s Polish flats. The official feature text gives examples such as diluted paint, uneven tiles, cheap tools, furniture handling, flooded bathrooms, and full remodels.
Keep version scope visible
The evidence ledger is a pre-release snapshot accessed on 2026-08-12. Its full-game metadata showed a planned August 13, 2026 release, while the demo was already available. A database entry does not establish that a listed feature behaved identically in a playtest, demo, and shipped full game.
Data that should be rechecked
Player counts, concurrent users, price displays, and review aggregates can change after publication. The official ledger recorded no full-game price field before release, even though Steam news announced a US$19.99 base price and a 15% launch-discount milestone. Treat third-party historical charts as dated snapshots and verify current storefront information at the official page.
Safe way to use a database page
Start with the official Steam app ID, then use a third-party page only to navigate or compare labels. Cite Steam for gameplay categories, requirements, save features, and official announcements. Build numbers, depot details, or any other SteamDB-only observation need an explicit third-party label and a date.
A practical source hierarchy
For a claim about PC availability, begin with Valve's Steam metadata API or the corresponding Steam store page. For an announced date, price, trailer, or demo event, use the official Steam news feed that published it. SteamDB belongs below those sources because it can organize Steam data without being the publisher, developer, or platform's official announcement channel.
This hierarchy matters when pages disagree or when an entry has not refreshed after a storefront change. The app ID, source URL, access date, and version should travel with any cross-reference. A reader can then distinguish a current official field from a historical third-party observation without guessing which one is authoritative.
Check the right fields
The full-game metadata is the place to verify developer, publishers, platform flags, categories, requirements, and listed Steam features. The demo metadata has its own app ID, release date, category set, and requirements, so it should be checked separately. A SteamDB page that combines or compares those records does not prove that a demo feature, depot, or status applies to the full game.
For Low-Budget Repairs, the official pre-release record lists Windows and Single-player for the full game and demo. It lists Save Anytime for both, while Steam Cloud appears on the full-game record in the official ledger. Save-file paths, demo transfer behavior, and detailed cloud behavior remain Pending confirmation rather than becoming database-derived assumptions.
Launch-day recheck checklist
Reopen the official full-game Steam page after the stated unlock before reporting a current price, review score, download state, or player figure. Confirm the regional storefront display instead of calculating a local total from the announced US$19.99 base price. If a launch discount appears, cite the current store display and the dated Steam news milestone separately.
Record whether the fact comes from the full game, the demo, Steam news, or a third-party tracking page. Do not silently replace a pre-release field with a post-launch fact. This method lets a SteamDB cross-reference stay useful while preserving the limits of the available evidence.
Record a SteamDB cross-reference
A responsible citation can name the SteamDB page as a third-party cross-reference and then give the official Steam URL that establishes the underlying claim. Include the relevant app ID: 3167920 for the full game or 3642880 for the demo. This avoids confusing an identifier lookup with a statement made by Gray2RGB, the publishers, or Valve.
If a database records a change, first determine whether it is a visible official storefront fact or a technical observation. Store categories, requirements, and price displays should be rechecked against Steam itself. Depot, branch, and build details must stay labeled as third-party observations unless an official announcement independently explains them.
The research cut-off is important because the source register captures a pre-release state. Later readers may see a released product, a current price, or reviews that did not exist in that snapshot. Preserving the date and the source hierarchy makes the article accurate without pretending that old database data is live.
The official source register itself provides a useful audit trail: S1 for the full-game metadata, S2 for demo metadata, and S3 for official news. A database lookup can sit alongside those links, but should not erase their version labels. This approach lets readers reproduce the comparison without assuming a single page owns every fact.
For any statistic visible only on a database, state exactly what was observed and when. Do not recast an unverified number as a player count, review metric, or publisher statement. The proper status is Pending confirmation until an appropriate first-party page or announcement supports it.