Entrances & building

Match the advice to your installed Demo.

Evidence checked November 3, 2026 · PC Demo

The short answer

For a Demo bug report, first launch Oboro no Ichi Demo and record the small version number at the bottom-right of its initial splash screen, the location given by the developer. Keep that installed version separate from a video date, SteamDB’s BuildID and a database “Last Record Update.” The reviewed Demo build list still ends at 25673422, October 2, 2026 at 09:18 UTC.

Checked November 3, 2026. SteamDB Demo Patches checked November 3, Los Angeles time. This is a public build-list snapshot, not a reading of your installation or proof that its BuildID equals the game’s displayed version number. These are sourced instructions and decisions, not our own gameplay test.

On this page

Make the version useful for troubleshooting

Confirm the product. The separate Demo is app 5271720; the upcoming parent game is 4559930. Their platform listings and feature sets differ.
Read the initial splash screen. Note the actual bottom-right number, or capture it if it disappears quickly. The developer requested this detail when investigating transparent customers.
Check the Demo’s Steam download/update state. Let an offered update finish before comparing the symptom again. An old video cannot tell you which build is installed on your PC.
Record the environment and symptom. Include Windows or compatibility runtime, input device and the exact action that fails. Describe whether the issue happens in the menu, placement preview or open market.

Do not replace your save, change unrelated drivers or rebuild the market just to obtain a different version label. This workflow identifies what you are using before deciding which documented check applies.

Three labels that can mean different things

Label	What it tells you	What it does not establish
In-game splash version	The label your installed game displays; useful for the developer’s report.	A direct numerical mapping to a SteamDB BuildID.
SteamDB BuildID and build date	A publicly listed uploaded Steam build.	That your local download is current, or which specific fix every untitled build contains.
Last Record Update / changenumber	When SteamDB recorded a database change.	That a new playable patch shipped at that time.

In the November 3 snapshot, the Demo’s record-update time is November 3, but its Patches table’s latest build is October 2. Treating that record timestamp as a new Demo fix would give you the wrong comparison.

What the reviewed build list actually shows

The public Patches table contains eight untitled builds from September 23 through October 2. Its newest entries are 25673422 at 09:18 UTC and 25673199 at 09:06 UTC, both on October 2. It provides no explanatory patch title for those entries.

The separate cursor-drift discussion contains an October 2 developer fix statement and player confirmation. The dates are useful context, but the reviewed source does not identify which exact BuildID carries that fix. Do not silently turn a same-day timestamp into a confirmed mapping.

Recheck the linked actual Demo Patches list when a newer release is relevant. A parent-game build or main-development fix is a different source of information.

Apply the right report to the right symptom

Transparent customers or shadows: compare the gate direction, space and historical Demo mask issue. Keep the installed version with your layout screenshot.
Cursor drifts up-left: use the dated input-fix checks and whether the menu accepts input now.
Camera or item rotation is confusing: use camera gestures versus item controls; a missing middle-mouse alternative is not proof that the gate is broken.
Undo, Photo Mode or a main-build fix is mentioned: compare the product/version before expecting it in the Demo. A development statement is not evidence that the separate Demo received it.

If the symptom remains, report the actual app, splash label, update state, environment and screenshots of the relevant panels to the developer discussion. These details help distinguish a new case from an older recording; they do not guarantee a universal repair.

A report that identifies the actual build

You have the installed product and splash label, know which public build list you compared, and can describe the symptom without confusing database timestamps or full-game promises with a Demo update.

Sources & version

No exact patch-content map, installed-build verification or new update is invented from a record-change date.