Gapcraft

The gap must work twice

A platform gap first works as a drawing. Its spacing, rhythm and silhouette suggest how someone might cross it. Then it has to work as movement. Gapcraft is interested in the point where those two versions disagree, because that disagreement gives the maker a concrete next edit.

The checker uses the same integer physics as play mode. This shared model makes a found route meaningful: it can be replayed as a sequence rather than represented only by a success badge. The maker can inspect where the route collects a washer, changes direction or reaches a safe platform.

A bounded search also requires an honest kind of failure. Reaching the search limit does not establish that a level is impossible. Preserving that distinction keeps the checker from becoming a false authority over the maker's idea. The next step might be another edit, a manual attempt or a simpler route whose behavior is easier to understand.

The local workshop uses a 24-by-14 board with platforms, spikes, collectibles, a start and an exit. The player must collect every washer before leaving. Edits support undo and redo. Play, bounded route checking and solution replay help inspect the design, while level-code export and import carry the board between browsers without an account.

Check a route and replay the exact inputs before calling the level possible. Notice the consequence before adding another step. This presentation does not connect a hosted service or issue a token; its claim is the small interaction you can actually inspect.