Do not confuse demo and full reviews
The full game was still listed as coming soon at the source cut-off, and the store crawler showed no user reviews. The demo had its own Steam review display. A demo aggregate cannot be renamed as a review score for the full release.
The dated demo snapshot
Steam's demo page showed 748 user reviews and 86% positive when the ledger was accessed on 2026-08-12. Both values are live storefront data that can change. The snapshot supports only that dated description of demo reception.
What official sources cannot rate
Steam's store description can establish the listed premise and features, not whether critics or players recommend the released game. An official trailer is promotional material, not independent review evidence. Review quality, performance impressions, and value judgments need attributable post-release sources.
Read individual opinions correctly
A forum post, Reddit thread, or single Steam review can be useful as one person's experience. It should not be presented as a representative consensus or a verified mechanic. Version, play time, platform, and date all matter when someone reports a problem or preference.
What is confirmed about the game
The official Steam listing describes a single-player first-person renovation simulation by Gray2RGB. It names Simplicity Games and PlayWay S.A. as publishers and provides examples of cost-cutting repair work. Those facts give readers context, but they do not create a rating.
How to update this page
After release, check the full game's official Steam page for its own current review display. Link criticism to the original reviewer or outlet and keep Demo and full-game verdicts separate. Console review coverage and performance are Pending confirmation until sourced.
Review-source hierarchy
Steam can directly support its own currently displayed user-review aggregate for the specific app page being viewed. An outlet can support its own bylined review, and a player can support only their personal experience. Neither a trailer, an announcement, nor a community summary is a substitute for a review score.
The source snapshot showed no full-game user reviews because the full game was still coming soon. It did show a demo aggregate on the demo page, tied to a particular date. A later full-game review page must be treated as a new source rather than an update silently assumed from the demo.
Version and platform labels
Every review statement should say whether it concerns the demo, the Steam full game, or an Xbox version if and when a source names it. The demo is a separate free Steam app with selected jobs, so its impressions may not cover the full release. Pre-release footage and playtest comments should remain version-labeled even if they discuss the same broad premise.
Performance conclusions need the same care. The official PC requirements list a minimum GTX 1060 6 GB or RX 580 4 GB, but they do not contain a GT 1030 benchmark or a preset target. Compatibility on that card is Pending confirmation, and it should not be smuggled into a review conclusion.
A responsible launch update
Once the full game is available, capture its official Steam review display with the date and the exact app page. Keep the announced US$19.99 base price and 15% launch-discount milestone separate from any judgment about value. Regional price, review volume, and percentage can all move after launch.
When citing criticism, link to the original page and state whether it is editorial or user feedback. Do not average unrelated reviews into a made-up site score. This approach gives readers a clear answer about what is verified now and a transparent path for later updates.
Record review evidence accurately
A dated review snapshot should include the product it came from, the store page, and the date it was seen. The ledger's 86% positive and 748-review figures belong to the Steam demo snapshot on 2026-08-12. They should not appear in a headline that implies a full-game consensus.
The announced launch date also affects how pre-release opinion is described. A trailer reaction or playtest comment may discuss the advertised concept without reviewing the eventual commercial release. Label those sources as reactions or historical impressions, not as a verdict on the full game.
After a live full-game aggregate exists, keep it separate from the demo rather than replacing the older number in place. This lets readers compare the two contexts without false continuity. It also avoids attributing a current rating to a source that was only captured before launch.
The review article can still answer useful questions before a full-game score exists. It can identify the developer, publishers, Steam app pages, stated genre, and the available demo. None of that context carries an implicit recommendation, and it should never be presented as one.
A launch-day update should save the exact page URL, the access time, and whether the number belongs to Steam's full game or demo. If a score changes later, describe it as a later snapshot instead of revising history. This keeps a review timeline transparent for readers.
The demo snapshot is also not evidence of a particular critic opinion or a post-launch performance verdict. Its aggregate says only how Steam displayed user feedback for that demo at the recorded time. An article must not derive a score for the Xbox listing, an unverified console build, or a future mobile edition from it.
Where a review mentions a feature, compare it with an official product page before repeating it as a factual summary. The reviewer can support an experience, while Steam can support listed categories and requirements. Keeping these roles distinct makes the review page fair to readers and to the source.