Why does the game count loops?
Complete Demo recordings show a loop counter increasing after endings. The counter helps track repeated runs, but current public evidence does not prove that a particular number automatically unlocks a secret short-Demo ending. MrClockWorks reached double-digit loops while testing choices without finding an additional verified conclusion.
The Steam description promises that the eventual game can use information gathered on earlier playthroughs, hidden objects and routes, and events aligned with real-world time. Those are important future systems, but they should not be presented as already solved Demo mechanics.
Why can the game resist closing?
The official itch.io page warns that Nate may react when the player tries to close the game. Recorded runs show a fourth-wall line after an exit attempt. Earlier builds also requested administrator access for stronger fourth-wall behavior, but the creator released an update on July 14 stating that administrator access was no longer required.
Do not advise players to grant administrator access to an old build merely to reproduce the effect. Download the current archive from the creator, and use the normal operating-system controls if the application must be closed.
Where does the native Demo save progress?
The creator's July 12 short-Demo update says save data is stored in the Windows Registry, so deleting the game folder alone may not reset progress. That explains why a loop count can survive a reinstall of the extracted files.
Registry editing can damage unrelated settings. This guide does not recommend deleting unknown keys. Players who need a supported reset method should ask the creator for the exact current key or an in-game reset option.
Which hidden details are visible now?
Recorded Demo routes contain changes in healing presentation, a loop counter, exit-aware dialogue, and optional request scenes. These are observable variations. They are not proof of a separate ending unless the game displays a distinct conclusion or the creator confirms one.
The community has also noticed references such as the transformation request and a numerical manga reference in dialogue. Those details are useful for a reference guide, but they do not currently change the verified five-outcome route map.
A safe secret-hunting checklist
- Record the Demo version or download date before testing.
- Change one dialogue choice per loop instead of randomizing everything.
- Record displayed Mood changes and the exact ending label.
- Test real-world-time claims only after confirming they apply to the current Demo, not merely the future full game.
- Preserve original saves before attempting any reset.
- Treat an animation or dialogue variation as an observation until it produces a reproducible route change.
What remains a player theory?
No reviewed source proves a fixed gesture code, a special ending at a particular loop count, or a currently active real-time route in the short Demo. A player has publicly asked the developer for hints about the Steam page's “specific times,” but no confirming answer was visible when this guide was checked.
That uncertainty is worth documenting. It gives the community a useful test list without turning speculation into fake certainty.
See the Demo update history before reproducing an older exit or route bug. The Nate lore guide separately labels what the current story confirms and what remains interpretation.
Sources
Checked August 17, 2026 using the official project page, the creator's no-administrator update, the Steam description, and the complete community playthroughs cited in the endings guide.