PuzzleScript

Overview

Arrow keys move, Z undoes, R restarts, and a single screen of blocks waits to be shoved into place. This is a puzzle built in PuzzleScript — a small, open-source engine designed specifically for sokoban-style block-pushing games — and it leans on the conventions the engine is built around. Each level is one tidy screen with no scrolling, every element is a colored tile, and the rules are written in plain text at the top of the game's source, which is how the engine keeps its puzzles readable and its community shareable. The mechanic here is block-pushing: walk into a block to shove it one square, provided something is not already blocking it on the far side, and arrange the blocks onto their targets to clear the level. Multiple levels string together into a short campaign, and because the engine bakes undo into its core loop, the design assumes you will lean on it constantly rather than restart from scratch after every misstep. The result is a pure, low-friction puzzle — no inventory, no combat, no cutscenes, just you, the arrow keys, and the next arrangement to unravel.

How to Play

Move with the arrow keys, one square at a time. Walk into a block to push it in the direction you are moving, as long as the destination square is clear. Press Z to undo the previous move — keep pressing to rewind many steps back through your history. Press R to restart the current level from its initial state when you have pushed yourself into a corner. The engine's central premise is that undo is unlimited and instantaneous, so experimentation is the intended way to play: try a push, watch what breaks, and either commit or rewind. Clear a level and the engine advances you to the next.

Tips & Strategy

Treat undo as your primary tool, not a crutch. PuzzleScript levels are designed around the assumption that you will try pushes, see the consequences, and rewind freely, so the fastest way to learn a level is to push things and observe rather than plan every move from a standstill. Watch what each tile actually does — the engine lets designers define custom rules in plain text, so a green tile might be a wall in one level and a crackable surface in another, and the visual language shifts from level to level. When a level seems impossible, look for the dependency: which block has to reach its target first, because that placement unlocks or blocks another. Corners are traps in any block-pushing puzzle — a block shoved into a corner with no pull mechanic stays there forever, so press R rather than burning undo budget on a cornered block. If you undo too far, R resets cleanly to the start, which is faster than re-zapping fifty moves forward.