Until Then V20241122-p2p May 2026

Mark types to you directly: “You’re not supposed to see this version. They patched me. In the official release, I learn to accept death. I have a cathartic beach scene. The piano plays a resolution chord. But here? In this build?”

You press start. The pixel-art classroom flickers. A ceiling fan turns lazily. Mark, your protagonist, stares at an empty seat. “Cathy hasn’t come to school again.” The dialogue box pauses, waiting. But beneath the cozy, hand-drawn Filipino indie aesthetic, something is already broken.

This build—this specific cracked mirror of a game—understands something that later patches might try to “fix.” That grief is not a linear process. It is a memory leak. A corrupted save file you keep reloading, hoping for a different outcome. The first few hours are deceptive. You walk Mark through the motions: jeepney rides, instant noodles, awkward group projects. The glitches start small. A character’s sprite freezes for a frame too long. A piano note repeats three times. The screen ripples like heat haze over asphalt. You ignore it. “Probably just the P2P release,” you think. Until Then v20241122-P2P

The game doesn’t end. It loops back to the classroom. The ceiling fan turns. The empty seat waits. And you realize: Until Then is not a story about moving on. It is a story about choosing not to. About the beautiful, terrible decision to stay in the glitch, where the dead still text you good morning, and every memory leak is a second chance.

v20241122-P2P — not just a version number, but a timestamp of a particular fracture in reality. Mark types to you directly: “You’re not supposed

But then you meet her. The new student. Long hair, sad eyes, a laugh that echoes before she speaks. Her name is Nicole . No—that’s wrong. Her name was something else . The game stutters when you try to read her name tag. The letters rearrange themselves. C-A-T-H-Y . Then back.

You press “New Game.”

The fan turns.