No—Tilt Ball Maze does not use your phone's gyroscope. It uses Arrow keys or four touch buttons to create one-cell digital tilts, without reading a device angle or any motion sensor.

What “tilt” means in this game
“Tilt” is a control metaphor here. The game never requests or reads a gyroscope, accelerometer, device angle, motion permission, or hardware sensor. Rotating your phone therefore does not steer the ball. Instead, each Arrow key or on-screen direction button sends a simulated digital tilt in one of four directions: up, down, left, or right.
Every command is evaluated as one discrete step. If the destination is open, the ball moves exactly one cell and that coordinate is appended to the completed path. If the destination is blocked, the attempted move fails without changing the position, path, successful move count, or score. A tilt never rolls until it hits something, crosses several cells, accelerates, bounces, or continues because time passed.
This deterministic design means the same direction from the same board state always produces the same result. Tilt Ball Maze also runs client-side in the browser. Your direction choices, paths, collision history, and scores are not uploaded for processing, and no account is required.
How to play Tilt Ball Maze on a phone
- Open the game in your phone's browser. Go to Tilt Ball Maze. It is a browser game, so there is no gyroscope-based setup step and no account to create.
- Do not enable motion access for the game. The game itself does not request gyroscope, accelerometer, device-angle, or motion permission access. Those sensors are not part of its supported workflow.
- Read the board before choosing a direction. Locate BALL, the END square, number-sign walls, and O holes. Asterisks mark cells already included in the completed path.
- Use the four-button directional pad. Tap up, down, left, or right once. Each tap attempts one fixed-cell move; the ball does not keep moving after your finger lifts.
- Plan around walls and holes. Walls block movement, while moving beyond a board edge is treated as a wall collision. A hole is recorded as a separate collision type. Reach END without entering a hole.
- Respond carefully after a failed move. The ball stays where it was, and the completed path, successful move count, and score remain unchanged. Inspect the board before trying another direction because a second distinct failure can lock the run.
- Clear all five original mazes. Each finish immediately awards exactly 200 points and opens the next fixed level at its own starting position. Completing all five produces an exact total of 1,000 points.
- Use Restart if the controls lock. Restart rebuilds the complete opening state: level one, the original start, zero successful moves, no failures, zero completed levels, and zero score.
Phone controls and sensor behavior
The controls are explicit and stable. In particular, a physical phone tilt and a digital directional command produce different results:
| Input or device behavior | What Tilt Ball Maze does | Effect on the ball |
|---|---|---|
| Touch directional button | Sends a digital up, down, left, or right command | Attempts exactly one-cell movement |
| Arrow key in the focused game area | Sends the same kind of digital direction command | Attempts exactly one-cell movement |
| Physically tilting or rotating the phone | Does not read the device angle or motion | Produces no sensor-driven movement |
| Gyroscope or accelerometer input | Never accesses the hardware sensor | Has no effect on gameplay |
Keyboard handling is confined to the focusable game area rather than attached globally to the browser window. This preserves a clear focus boundary and avoids intercepting Arrow keys elsewhere on the page. The four touch controls are native buttons with at least a 44-pixel interaction height and standard Enter or Space activation. No timer continues movement after focus changes, and unknown or malformed commands have no effect.
How to read the maze and status information
The board uses text and symbols rather than color alone, so the playable geometry remains understandable on a small screen. The meaning of each visible mark is fixed:
| Board mark | Meaning | Effect of choosing that cell |
|---|---|---|
| BALL | The current runner position | Shows the ball's present coordinate |
| # | A wall | Blocks the attempted move |
| O | A hole | Records a separate failed-step type |
| END | The level finish | Clears the level and awards 200 points |
| * | A cell in the completed path | Shows where a successful move has already been recorded |
Text beside the grid reports the current row and column, successful moves, distinct failures, last failure type, level count, and score. Accessible cell labels identify the visible row, column, and board role. This means you do not need to infer the ball's location from color, animation, or a sensor reading; the grid and its labels expose the relevant state directly.
How collisions and the deadlock rule work
A failed step is all-or-nothing. Whether the destination is a wall, a hole, or beyond the outer edge, the ball remains at its current coordinate. The completed path does not change, the successful move count does not increase, and the score stays fixed. A failure is still recorded so the status display can show distinct failures and the last failure type.
Repeating the same failed direction from the same coordinate does not consume the second-distinct-failure allowance. Direction aliases are normalized, so the same internal direction is treated consistently. However, a failure with a different signature—such as a different direction, a different coordinate, or the other collision type—counts as the second distinct failure and deadlocks the run. Level one deliberately makes both a wall failure and a hole failure reachable from the opening cell, so blind experimentation can reveal this behavior quickly.
After deadlock, the directional buttons and state transitions are frozen until you choose Restart. Restart does not merely repair the current cell; it recreates the complete opening state. The game also ignores invalid commands and does not continue movement after the game area loses focus.
Scoring, levels, and verified route lengths
Reaching a finish awards exactly 200 points and opens the next level immediately. The successful move count and completed path reset for that new maze, while the total score and completed-level count continue. After the fifth finish, the final board remains frozen with its completed path visible.
The independently verified shortest route lengths for the five levels are 8, 8, 8, 8, and 6 fixed steps. These lengths provide a useful planning benchmark because the successful move count measures one-cell movements that reach open destinations. The stated award remains exactly 200 points per finish; shortestness is not presented as a separate score multiplier.
What physical tilting does on a phone
Physical tilting does nothing to the board because the game never observes the phone's orientation. A practical control check is to tap one legal direction on the directional pad and confirm that BALL changes by exactly one row or one column. An Arrow key produces the same one-cell result when the game area is focused.
Any tutorial that instructs you to rotate the phone to steer the ball in this specific game would be inaccurate. The supported workflow is straightforward: read the visible maze, choose one digital direction, avoid distinct failures, and use Restart if the run locks.