Tilt Ball Maze is a five-level ball maze game in which every Arrow key or tap moves the ball exactly one cardinal cell on a 5 by 5 grid, and clearing the finish in all five original mazes produces an exact score of 1,000 points. The game treats every tilt as a single atomic step, so the ball never rolls, slides, accelerates, bounces, or depends on elapsed time. That single-cell rule is what makes Tilt Ball Maze predictable for keyboard users, touch players, slower devices, and assistive technology, and it is also the rule that the underlying test oracle replays to confirm every route. Because each step is deterministic, the same direction from the same state always produces the same next state, which means your route is fully verifiable. Nothing about the game reads a real gyroscope, accelerometer, device angle, or motion permission; the word "tilt" describes the directional control metaphor rather than a claim that the browser measures a physical board. All geometry is original to the product, every wall and hole is fixed in place, and there is no random spawning or hidden state to second-guess.
What Tilt Ball Maze Is (and What It Isn't)
Tilt Ball Maze is a deterministic, browser-based ball maze game built on five original 5 by 5 fixtures. Each fixture defines a fixed set of open cells, wall cells, hole cells, a single start, and one finish. The ball starts at the same coordinate on every run, and the same walls and holes appear in the same positions, which means the geometry you see is the geometry the game tests against.
The game runs entirely on the client. No account is required, no path is uploaded for processing, and no hardware sensor is consulted. There is no rotation of a 3D board, no momentum, no timer that keeps moving the ball after focus changes, and no random spawning of obstacles. Direction choices, paths, collision history, and scores stay in the browser tab.
That last point matters for the search query "ball maze game." Many results describe 3D tilting boards or physics-driven rolling balls. Tilt Ball Maze is neither. It is a grid puzzle with one-cell transitions, and that is the difference that the rest of the article is built around.
How to Play Tilt Ball Maze
Follow this exact sequence to clear a single level and start working toward the 1,000-point finish.
- Open the board and read the visible markings: BALL marks the runner, # marks a wall, O marks a hole, END marks the finish, and * marks a cell already added to your completed path.
- Choose one Arrow key or one on-screen direction button for a single fixed-cell step up, down, left, or right.
- Watch the status text beside the grid update after every press: it shows the current row and column, successful moves, distinct failures, the last failure type, the level number, and your running score.
- If the destination is a wall, a hole, or off the 5 by 5 board, the step fails atomically. The ball stays where it is, the successful move count does not increase, the completed path does not change, and the score is unchanged.
- If the destination is an open cell, the ball advances exactly one cell and that coordinate is appended to your completed path. The successful move count increases by one.
- Land on END to bank exactly 200 points and unlock the next maze at its own start position. Successful moves and the path reset for the new maze, while total score and completed-level count carry over.
- Stay aware of your failure count. Two different wall or hole signatures in the same level freeze the run until Restart.
- Repeat for all five original mazes. Your total score stops at an exact 1,000.
Walls, Holes, and the Atomic Step Rule
The difference between a wall and a hole matters because they are separate failure types. Reaching a # cell or stepping past the 5 by 5 board edge both record as wall collisions. Stepping onto an O cell records as a hole collision. In either case, the step fails atomically, and the attempt leaves position, path, successful move count, and score exactly as they were before the keypress.
The one-cell step rule is central. A single tilt never rolls until a wall, slides across multiple cells, accelerates, bounces, or depends on elapsed time. That fixed transition keeps the result predictable: the same direction from the same state always produces the same next state, whether you press the key quickly or slowly, on a phone, on a desktop, or through assistive technology.
Failure signatures are normalized, so repeating the same failed direction from the same coordinate is deduplicated and does not consume the second distinct failure. A different failure, however, creates a second signature and deadlocks the run. The first level is deliberately constructed so that both failure types are reachable from the opening cell: moving beyond the left boundary records a wall collision, while moving upward reaches a hole. That setup lets the two-distinct-failure deadlock be tested without corrupting or resetting the ball's position.
For a broader view of how wall collisions interact with scoring in keyboard maze games, see Do Wall Collisions Lower the Score in Maze Game?, which covers a related mechanic in a different grid game.
The 1,000-Point Route and Verified Shortest Paths
The five original mazes share an exact point schedule and an exact minimum step count. Clearing the finish in any level always adds exactly 200 points, and finishing all five always lands on a total of exactly 1,000 points. The table below summarizes the verified shortest routes through each level and how the cumulative score grows as you clear them.
| Level | Shortest path (fixed steps) | Points awarded on finish | Cumulative score after level |
|---|---|---|---|
| 1 | 8 | 200 | 200 |
| 2 | 8 | 200 | 400 |
| 3 | 8 | 200 | 600 |
| 4 | 8 | 200 | 800 |
| 5 | 6 | 200 | 1,000 |
| Total | 38 | 1,000 | 1,000 |
The five shortest distances, 8, 8, 8, 8, and 6, were confirmed by a private breadth-first search owned by the test oracle. The oracle treats walls and holes as blocked, recomputes the shortest reachable distance to every finish without calling the product movement reducer, and then replays the literal safe route both through the oracle and through the product state. That two-layer check confirms all five levels are completable, confirms the shortest step counts, and confirms the exact 200-point increments on the way to 1,000.
After the fifth finish, the final board remains frozen with its completed path visible. There is no bonus for finishing faster, no penalty for taking more steps than the shortest route, and no way to earn more than 1,000 points from the published five mazes.
Two-Failure Deadlock, Restart, and What Resets
Once a run is deadlocked, every directional button and state transition is frozen until Restart. Restart does not modify part of the current object; it rebuilds the complete opening state. After Restart, level one is restored, the original start coordinate is restored, the successful move count returns to zero, the completed path returns to a single-cell path at the start, failure signatures are cleared, the last failure is cleared, the completed-level count returns to zero, the score returns to zero, and controls are active again.
Automated tests compare the Restart output directly with a fresh initial state, so the rebuild is bit-for-bit identical to a brand-new tab. Unknown commands, empty values, non-string values, completed-state input, and deadlocked-state input are all treated as atomic no-ops; they neither move the ball nor consume any failure slots.
Controls, Accessibility, and Privacy
Controls are intentionally explicit and stable. Four native buttons form a directional pad, and the focusable game area accepts the four Arrow keys. Keyboard handling is scoped to that area rather than attached globally to the browser window, which preserves a clear focus boundary. No timer keeps moving the ball after focus changes, so tabbing away and back does not advance the run.
Every directional button has at least a 44-pixel interaction height for touch play, and the native button element provides standard Enter or Space activation. Accessible cell labels name only the visible row, column, and board role, so screen readers receive the same geometry the player sees. The visual board communicates all playable geometry without color-only meaning, which keeps the game usable in high-contrast modes.
Because the game never reads a real gyroscope, accelerometer, device angle, motion permission, or hardware sensor, you can play the full five mazes on a desktop, a tablet, or a phone without granting motion access. Direction choices, paths, collision history, and scores stay in your browser. The shared GameShell that wraps the game also provides score handling, local best-score behavior, deterministic Restart, and a Boss Key for situations where you need to clear the screen quickly.
If you want to practice maze navigation broadly before tackling the deadlock mechanic, the guide How to Avoid Common Mistakes in a Maze Game walks through the kind of planning that makes single-step grid games easier to clear.