Day 3 is being worked on, is not finished, and has no announced release date. That combination is the entire honest summary. Everything else circulating about Day 3 — months, weekends, countdowns — is inference built on top of development activity, and the developer has explicitly asked that outside date claims not be repeated.
Public build today: version 0.2. Day 3 is in active development. No release date, no month, and no weekend has been announced. The figures quoted below are beta-scope figures, not whole-feature percentages, and the difference matters.
What the official updates confirm
The developer publishes weekly development updates and AMA answer series on the official Tumblr, and the Day 3 posts there form a reliable record of work in progress. Recent entries describe:
- Continued coding with placeholder assets. Newly coded scenes still use placeholders and work only partially, with transitions, choices, and images to be polished once those scene decisions are settled.
- A new, very short scene referring to Columbina. Her character design is planned soon so that flashback silhouettes stay consistent.
- Beta progress. An earlier update described one part of the Day 3 beta as finished and put the beta at roughly 30–40% of the full update. A later update described being almost halfway through the content planned for the beta test.
- A larger script than Day 2, with additional bad ending content and hidden scenes described.
- Café scene work in progress, with some choices and situations needing further revision, and more sketches and possibly new backgrounds still needed.
- New sprites selected for Harlequin, Pierrot, and Jester, with revisions and new sprites for Doctor planned when development reaches his scene.
None of that is a release schedule. Writing, artwork, sprites, and programming updates confirm that development is active; they do not mean Day 3 is finished. Day 3 should only be treated as released when a new public build actually appears.
"30–40% of the full update" and "almost halfway through the planned beta content" describe different scopes. The first measures the whole update; the second measures the smaller slice of content earmarked for the beta. Neither one is a percentage of the finished game, and a beta is itself a milestone rather than a release.
Why no date is being given
The developer's position is consistent across the official FAQ and the Askbox answers: no release date has been announced, and date claims from outside the official posts should not be repeated. That is a deliberate instruction to the fandom, not an oversight.
There is practical context for it. The same period of development has included addressing unauthorised Google Play uploads, and the developer has noted that an official store release would receive its own announcement. A date announced before a build is finished, and before the distribution question is settled, would be a promise that could not be kept.
What Day 3 is expected to change
The planned shape of Day 3 is larger than what came before it, and that has direct consequences for what the current build does and does not show.
- New bad ending content is described in the development posts, which means the ending category in the build will grow beyond the single "Missing" ending that exists today.
- Hidden scenes are also described, which is a different thing from a route — a hidden scene is content, not a conclusion.
- More branches. The script is bigger than Day 2's, and the branching work described includes sections with many choices that need extra testing.
- Columbina's story. The new short scene and the flashback silhouette work both point to more of the shared backstory surfacing.
What has not been announced is any of the four planned endings shipping in Day 3. The planned endings remain planned.
What is confirmed about the release itself
Some things about how Day 3 will be delivered are settled, even though the date is not.
- It will be a public build on the official page. The developer has confirmed the itch.io page as the only official page, so Day 3 will appear there rather than through a third-party launcher or a separate store front.
- Platforms are already established. Version 0.2 exists for browser, Windows, macOS, Linux, and Android, so the same set is the reasonable expectation for Day 3 — though no per-platform release order has been announced.
- Any official store release would be announced separately. The developer has noted that a store version would get its own announcement rather than arriving quietly alongside the itch.io update.
- Unauthorised uploads are being dealt with. Time went into addressing unauthorised Google Play uploads, which is a distribution problem rather than a development one — but it does mean the route a player takes to an official release is not entirely simple yet.
How to check the current status yourself
- Open the official itch.io page and confirm the listed build is still version 0.2.
- Read the devlog entries in order. They are dated and they are first-party.
- Check the official Tumblr for the most recent weekly update and the AMA answer series.
- Treat any date you find elsewhere as unverified unless it appears in one of those places.
- Ignore countdown pages. A countdown is a fan estimate with a clock attached.
The developer has confirmed there is no official Discord server, so any server that is not linked from the official itch.io, Tumblr, Patreon, or Bluesky pages should be treated as fan-run or unauthorised. That rule applies to date announcements too: a date quoted in a fan Discord is a fan date.
What to do with the current build in the meantime
Keep your saves, note which build created them, and avoid overwriting the first-playthrough slot. When the next build arrives, read its change notes before assuming that version 0.2 route advice still applies. A prototype's branching can be reorganised between builds, and the ending list will change as the script is finished.
For the day-by-day record, see the site's Day 3 tracker, and for what the current build already contains, see the prototype guide.