Back to Blog · July 5, 2026 · Devlog
Devlog #1 - Designing a game where time only moves when you do
MOMENT started with a single question: what if the player was the clock?
Almost every action game is built on the same quiet assumption: time marches forward on its own, and your job is to react quickly enough. Bullets fly, timers tick, and the challenge is your reflexes against a world that will not wait. I wanted to see what happened if I removed that assumption completely.
So the rule of MOMENT is this: the world is frozen until your cursor moves. A small mouse movement lets every bullet creep forward, and a faster motion makes danger surge farther. Hold perfectly still, and everything on screen holds still with you.
The moment it clicked
The idea sounds simple, but the first playable build showed me something I hadn't expected: it makes you feel the cost of every motion. When a bullet is inches away, you instinctively slow down. Because slowing down also slows the bullet, tiny careful movements turn out to be very strong. You can thread a gap that looks impossible, one pixel at a time, because the danger creeps forward only as fast as you do.
The flip side matters just as much. Crossing an open space quickly is fine, even smart, because a fast flick spends little risk. But commit to a big move near danger and the world lurches forward with you. That tension between the safety of stillness and the need to make progress turned out to be the whole game.
Turning the rule into a score
Once the mechanic was fun, it needed a way to measure skill. The obvious choice, a timer, was exactly the thing I'd thrown away. So the score became the one number the mechanic naturally produces: the total distance your cursor has traveled, in pixels. Lower is better. It felt odd at first, but it fits: a great run is not the fastest one, it's the one that reached the goal with the least movement.
This reframes the whole game. You stop asking "how do I dodge this?" and start asking "what's the shortest, calmest path that still survives?" It rewards planning over panic, which felt true to the spirit of a game with no clock.
Small touches that made it readable
- A clock ring on the orb. A little hand sweeps around the player as the world advances, reinforcing that you are winding time.
- A motion vignette. The screen edges glow faintly brighter the faster you move, as a quiet reminder that motion equals danger.
- Frozen trails. Bullets leave short trails so you can read their direction even while they sit motionless.
None of these change the rules. They just make the one rule legible, so a new player understands "the world moves when I do" within a few seconds of picking up the mouse.
What's next
The core is solid, so the work now is variety and feel: more hazard types, smarter difficulty curves, and modes that ask different things of the same mechanic. The next devlog covers how one rule ended up supporting two very different ways to play.