games: add Motion Challenge with sliding-block variants

Aberta
#62 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
32/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
next.js, react, typescript
Domínio
frontend, game-dev

Direção de pesquisa

Start by reading the implementation and tests for the shared game lifecycle and results, then inspect the work tracked in #24 and the prerequisite in #58. Define and verify board solutions, including the advanced variants and any advertised move counts; completion means the listed movement, keyboard, learning-mode, restart, and browser checks pass.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement games help wanted

Part of #24. Depends on #58.

Student problem

Students need spatial-planning practice that rewards understanding legal moves and finding a route to an exit.

Scope

  • Build a grid with movable rectangular pieces, fixed obstacles, a target piece and a designated exit.
  • Allow cardinal sliding only when every occupied cell remains in bounds and avoids other pieces/obstacles.
  • Start with freely movable pieces; add an advanced variant with horizontal/vertical restrictions and a documented target move count.
  • Generate or curate demonstrably solvable boards. Define precisely what counts as one move.
  • Offer selectable pieces and keyboard/directional controls as an alternative to dragging.
  • In learning mode, explain a legal solution and offer a hint without presenting an unproven minimum as optimal.
  • Use the shared lifecycle/results, original boards and free guest access.

Done when

  • Tests cover footprint collisions, bounds, axis restrictions, blocked movement, reaching the exit and move counting.
  • Every shipped/generated board has a verified solution; any advertised minimum is solver-verified.
  • Browser checks solve a board using keyboard controls and restart both variants.
Linguagem predominante
TypeScript
Estrelas
1
Forks
1
Merge médio
8h 58min
PRs com merge (30d)
37

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de procoderji-com/procoderji

Todas as issues de procoderji-com/procoderji

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.