Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

For each game tick, code computes legal next moves and facts such as food distance, reachable space, and dead ends. Jev chooses among those directions from a rendered board and strategy; the game controller accepts only a legal choice that arrives before the tick deadline, otherwise it continues straight or uses a fallback.

What Jev decides

Choose the next legal moveExample answers · not a recorded Jev response · Source ↗
Question 1 · move
YOUR APP
INSTRUCTION

Choose the direction the snake’s head moves on the next step. Every listed direction is safe for this step; prefer a move that preserves reachable space and avoids a dead end.

STATE

A 5×3 Snake board: head at row 1, column 3, heading right, with open cells above, ahead, and below; the request also includes food and per-move safety facts.

JEV · CHOICE
  1. up
  2. right
  3. down

App workflow

  1. Analyze legal moves

    The game engine computes safe directions and move facts from the current board.

  2. Build the request

    The request includes a board rendering, coordinates and heading, food information, grid size, strategy, and per-direction facts.

  3. Choose a direction

    Jev returns a Choice among the listed legal directions.

  4. Advance the tick

    The controller validates the choice and plays it at the fixed tick boundary; late or failed responses use a fallback.

Why it is interesting

The request supplies exact, code-computed consequences for each safe move, letting Jev choose among constrained actions while the engine retains game rules and timing.