A snake moving right does not accept a direct left turn; the same rule applies to up versus down. That opposite-direction input is ignored. Returning the other way requires perpendicular turns, actual movement between them, and enough open board space for the route rather than a rapid list of button presses.
0 fruit · 3 of 144 cells · 0 steps
The game is stationary. Enable JavaScript to use the controls.
Take a break.
The board is not moving.
Select Continue whenever you are ready.
The head uses an arrow, the body fills cells, and fruit is marked ●.
Inside the game: steer with arrow keys or WASD. With the board focused, Enter or Space starts or pauses; Escape also pauses. Use Tab, then Enter or Space on the buttons.
Initial head: row 6, column 6. Heading: right. Food is placed when the game starts.
Enable JavaScript to play.
Saved locally; progress does not sync between devices.
Text describes position, heading, and food. This continuously moving game still requires following the visual board; full nonvisual accessibility is not claimed.
Choose Start, then steer with arrow keys, WASD, or the direction buttons. Eat fruit to grow by one segment and gain one point. Hitting a wall or your body ends the game. An immediate reverse turn is ignored. Pause and leaving the tab stop movement. The board is 12 × 12, and progress is saved only in this browser.
After Start, the snake moves continuously. A direction button changes the heading for upcoming movement; it does not move exactly one square and then wait for another tap. Releasing all controls therefore does not pause the round by itself.
Identify the direction the head is actually traveling before choosing a change. A direction you intended to request and a direction already applied to movement may refer to different moments. The reverse-turn restriction is about the current motion, not a guarantee that any string of rapid inputs will be stored as a future route and executed in the order you imagined.
Suppose the head is moving right and you want to travel left. One possible route turns upward, advances, and then turns left, provided every destination is legal. The first turn changes the geometry of the body only after movement actually takes place.
Pressing up and then immediately left before that intervening movement is not proof of two completed turns. Left can still be evaluated as opposite to the current rightward travel and ignored. Observe the head’s change before choosing the next turn. This explanation does not promise a universal timing interval in milliseconds across phones, browsers, or performance conditions.
Requesting the opposite direction does not stop the head before a wall, allow it to leave the grid, or wrap it around to the other side. Choose a legal perpendicular route early enough to remain within the board. The next square matters as well as the turn category.
For instance, a head moving right along the top row cannot use an upward turn as an in-bounds escape. A left request remains a direct reversal. You must evaluate the actual remaining space and body rather than assuming proximity to a wall changes the input rule. A turn made after a collision cannot rewrite the preceding step.
A perpendicular turn can still hit an interior body segment. The opposite-direction rule prevents one particular kind of reversal; it does not inspect your entire planned route and declare every accepted direction safe. Check the next landing square separately.
Tail movement can make the current final tail position free during a non-growing step, but that does not apply to every occupied square. An interior segment may remain where you are about to move. If you cannot identify the tail precisely, prefer a clearly open route instead of treating a special legal tail transition as permission to pass through the body generally.
Pause stops the round and hides the board. It is useful when leaving the activity, not a visible frozen diagram or a way to make an inverse turn legal on resuming. Continue from the position that reappears, checking its heading before repeating an input you remember planning.
The visible controls and keyboard arrows or WASD follow the same movement restrictions when keyboard focus belongs to the game. If an input seems ineffective, distinguish an ignored reversal from an inactive focus context or a round that has already ended. Local saving depends on retained browser data, not a synchronized player account. Understanding this rule can explain one observed input; it does not promise that every later collision is avoidable or that a memorized turning sequence guarantees a record score.
No. A direct opposite-direction request is ignored.
No. Actual movement must occur between turns for the intended route to be established.
No. It keeps advancing after starting; use Pause to stop the session.
No. Its destination must still respect the border and remaining body.
The paused presentation hides the board. Inspect the position after continuing.