The short answer

According to Eastshade's demo 0.464 notes, the clock pauses in the player menu and shops, but deliberately keeps running in flute mode. The studio's earlier time-design explanation also describes freezes during events and evenings. These statements describe documented design and demo behavior, not a hands-on verification of the September 30 full release.

Player menu and shops
Clock stopped in 0.464
Flute mode
Clock intentionally continues
Events and evenings
Freeze described by developer

What to do

  1. Identify the mode you are in: player menu, shop, flute performance or an event.
  2. Use the mode-specific rules below instead of assuming every overlay stops time.
  3. For music practice, look for the practice rooms mentioned in the 0.464 notes.
  4. If the installed build behaves differently, record the screen, mode and build; do not treat an old patch as proof of current behavior.
Documented clock behavior — demo/design scope
SituationDeveloper description
Player menu / shopSource ↗Paused in demo 0.464
Flute modeSource ↗Continues intentionally
Events / eveningsSource ↗Freeze described in time-design devlog

Why flute mode behaves differently

The patch describes the flute exception as intentional and directs players to classroom practice rooms. Opening the instrument is therefore a poor way to assume you have paused an ordinary day. This distinction matters when you are learning inputs and repeatedly consulting a song.

The older devlog explains the broader rhythm of the world, while the patch addresses specific interface states. Read them together, but keep their dates and scope visible. Neither establishes a configurable time-speed slider, a universal pause button or the exact length of a full day.

A stopped clock is not a saving guarantee

Clock behavior and save availability are separate questions. A frozen display does not establish that a save was written, and a store saving feature does not document every event restriction. Check the save interface itself before ending a session rather than relying on the clock as a success signal.

For planning, use flexible activity blocks instead of unverified minute-perfect schedules. A class event, ordinary exploration and flute practice need not share the same timing rules. After release, this table needs a fresh comparison against the actual launch build before its scope can change.

Behind this answer

Article reviewed · Demo 0.464 and developer time-design notes

  1. Demo Version 0.464Eastshade Studios · DEVELOPER · Source checked 2026-09-25 · Official source · 2026-04-09
  2. Devlog #4 | World First Design and Time in Glimmerwick!Eastshade Studios · DEVELOPER · Source checked 2026-09-25 · Official source · 2024-05-08
  3. Demo Version 0.466Eastshade Studios · DEVELOPER · Source checked 2026-09-25 · Official source · 2026-04-14
How we check sources →