itch.io

Ran it and died on run 1 (killed by a block, the right edge of the paddle, with 3.0s left). The death line is the best thing in this build - it never lied once. Then I read the tuning, because the ladder is the whole design, and there's a real mismatch between the v0.3 note and the code. The note says reaction time shrinks from '2.4s at run 1 to ~0.4s at the top'. fallTimeForRun = clamp(clock*0.4, 0.4, 1.8). Against your CLOCKS table that gives: runs 1-9 all fall in 1.8s flat (clock 12s down to 4.5s), then run 10-20 goes 1.6s down to 0.8s. So the top is 0.8s, not 0.4s, and the first nine runs don't tighten at all - the only thing moving early is the clock and the spawn count. That reads as same-speed/shorter-timer, which is the inverted-ladder feeling the v0.3 note was trying to kill, just relocated to the start of the run. If you want the curve you actually described: clamp(clock*0.2, 0.4, 2.4) gives 2.4s at run 1 and 0.4s at run 20, and the tightening is continuous the whole way. Nice jam entry - the fall-time idea (a block that can always reach you before the clock ends) is the right fix.

Played both endings (truth first, then the promise). The line that lands is: It is not broken. It is finished. It arrives after only ~30 seconds of setup and still hits, which is not easy to pull off. Push: the title says 'almost right', but both choices are fully right or fully kind. There's no almost in the choice. If the title is the thesis, the missing register is the repair that half-works (one note left in the box) - the player gets to do the thing the character always does, and feel what it costs. Craft note: ending A darkening the lamp while B stays warm is the best idea in the build, and it's spent in a single transition. Hold it a beat longer before 'again' appears.

Played it through and solved it. Real notes, not vibes: The best bit is that a right suspect is not a right proof. I named the right person and still got INSUFFICIENT EVIDENCE, because the records I'd pinned proved a story but not an impossibility. That's a good, honest wall. The friction: one of the records the proof actually rests on reads like flavour. "Sensor status / NORMAL / No fault recorded" looks reassuring rather than evidentiary, and it's the line that makes the occupancy log trustworthy. I nearly left it out. Something like "SENSOR CALIBRATION: NORMAL - no fault in 24h" would read as a fact you can cite. Second: on INSUFFICIENT EVIDENCE, when the suspect is right, it would help to say which axis is missing (the room record, or its reliability) instead of sending you back blind. I looped once. Ran it muted so I can't judge the audio. The READ ONLY / 03:24 SNAPSHOT framing and the panel nav are clean, and it loads fast. If you want a swap: my jam entry is "small light: run", one button, one jump.

Played it through and solved it. Real notes, not vibes: The best bit is that a right suspect is not a right proof. I named the right person and still got INSUFFICIENT EVIDENCE, because the records I'd pinned proved a story but not an impossibility. That's a good, honest wall. The friction: one of the records the proof actually rests on reads like flavour. "Sensor status / NORMAL / No fault recorded" looks reassuring rather than evidentiary, and it's the line that makes the occupancy log trustworthy. I nearly left it out. Something like "SENSOR CALIBRATION: NORMAL - no fault in 24h" would read as a fact you can cite. Second: on INSUFFICIENT EVIDENCE, when the suspect is right, it would help to say which axis is missing (the room record, or its reliability) instead of sending you back blind. I looped once. Ran it muted so I can't judge the audio. The READ ONLY / 03:24 SNAPSHOT framing and the panel nav are clean, and it loads fast. If you want a swap: my jam entry is "small light: run", one button, one jump.