Probably Stolen Reviews: Launch-Week Evidence Tracker
Track Probably Stolen launch-week reviews with transparent criteria and no invented scores; the supplied evidence contains no qualifying review verdict.
What is the current review status?
Awaiting evidence. The supplied material contains no identifiable full-release critical review, scored verdict, or sufficiently detailed launch-week player-review sample for Probably Stolen. Accordingly, this page publishes no score, no review count, and no claim about consensus.
An empty tracker is more accurate than filling the page with generic praise. The game released on October 28, 2026, and this check is dated October 30, so the launch-week record is still developing. Basic release facts are documented separately on the About page.
What did the supplied sources actually contain?
The IGN material is a wiki navigation capture, not a review of the game. It links to IGN’s general review areas but provides no Probably Stolen evaluation, author verdict, or score. It therefore cannot support a statement such as “critics liked the game” or “IGN recommended it.”
The Reddit announcement thread contains enthusiastic comments from people discussing the demo, playtest, and anticipation before release. Those comments are evidence that some respondents were interested, not a representative review sample. They do not establish the quality, balance, performance, or stability of 1.0.
The supplied YouTube material consists of playtest tips and shop-mechanics demonstrations. A useful tutorial is not automatically an endorsement, and a video’s view count is not a review score. This tracker does not convert creator popularity into a verdict.
Which reviews will qualify for this tracker?
A future entry should meet all of these conditions:
- Identifiable publication or author: the source provides a stable page and a clear attribution.
- Full-release context: the text or video discusses 1.0 rather than only the retired demo or an earlier playtest.
- Substantive evaluation: it explains strengths, weaknesses, or technical behavior instead of merely announcing the game.
- Traceable verdict: any quoted score or summary can be checked at the linked source.
- Relevant date: the coverage belongs to launch week or is clearly labeled as a later reassessment.
The community directory is a place to find discussion channels, but an individual forum post still needs context before it can represent anything broader than that player’s experience.
How will reviews be compared?
Reviews will be grouped by evidence rather than averaged indiscriminately. A scored editorial review, a detailed unscored critique, and a short user comment answer different questions and should not be treated as interchangeable data.
The planned comparison fields are:
| Field | Purpose |
|---|---|
| Source and author | Make the verdict attributable and checkable. |
| Coverage date and game version | Distinguish launch impressions from demo, playtest, or patched behavior. |
| Review type | Separate editorial criticism, creator analysis, and player reports. |
| Strengths described | Record only claims supported by the source. |
| Problems described | Preserve caveats rather than extracting praise alone. |
| Score, if any | Reproduce only a published score with its original scale. |
No aggregate score will be calculated from unlike scales. No star rating will be inferred from adjectives, and no numerical sentiment percentage will be invented from a handful of comments.
What is the current launch-week review table?
| Source | Full-release review evidence | Score | Status |
|---|---|---|---|
| Awaiting qualifying sources | None in the supplied material | None published here | Awaiting evidence |
This table is intentionally sparse. It will be meaningful only after a source supplies an actual evaluation to summarize.
How should technical reports be handled?
Compatibility claims need especially careful separation from general opinion. A reviewer saying that a mouse-driven game feels comfortable on a computer does not prove Steam Deck compatibility. Controller behavior, Proton support, legibility, and performance require their own evidence.
The Steam Deck page therefore keeps compatibility Unconfirmed and does not borrow a workaround from an unrelated review. Similarly, an isolated bug report should remain an isolated report until its version and reproduction context are clear.
What can readers use while reviews are pending?
Official facts can answer whether this is the kind of game you want to investigate: it is a single-player, pixel-art cyberpunk shopkeeping sim about inspecting goods, serving customers, and managing rent. The beginner guide explains the supported opening loop, while the appraisal page shows how inspection and estimate work differ.
Those pages are mechanical documentation, not a recommendation disguised as a review. Until substantive launch criticism is available, the honest conclusion is simply that the game is out, its basic premise and platform are documented, and its critical reception remains unassessed here.