games: add Key and Door for directed-maze planning

Abierto
  • ¿Algo no está bien?
#67 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
nextjs, react, typescript
Área
frontend, game-dev, testing

Línea de trabajo

Start by reading the shared game lifecycle and the existing game implementations; the issue does not name specific files or tests. The work includes puzzle generation, stateful key and door rules, learning and timed modes, controls, and browser coverage. Done means the listed rule and generation tests pass, reachability checks account for key and door dependencies, and the browser test confirms collecting keys, exiting, and restarting resets inventory and timers.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement games help wanted

Part of #24. Depends on #58.

Student problem

Students need practice planning a route that satisfies collection and movement constraints before reaching an exit.

Scope

  • Present a grid maze with a start, required keys and an exit.
  • Define directed/one-way passages, blocked edges and locked doors explicitly. Exit success requires all stated keys.
  • Start with one key on a small board, then add a second key and larger boards at documented levels.
  • Generate or curate reachable puzzles by checking the full state of position, collected keys and unlocked doors.
  • Explain illegal moves and show a valid route in learning mode. Timed practice uses the shared lifecycle without showing the solution during a round.
  • Provide keyboard/directional controls, understandable symbols and free guest access.

Done when

  • Tests cover one-way movement, blocked/locked passages, key collection, premature exit, win conditions and deterministic generation.
  • Reachability validation accounts for key/door dependencies rather than checking each cell in isolation.
  • A browser test collects the required keys, exits and restarts without retaining inventory or timers.
Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
8 h 58 min
PR fusionados (30 d)
37

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de procoderji-com/procoderji

Todos los issues de procoderji-com/procoderji

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.