games: add Path Finder with rotatable arrow blocks

Offen
#66 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv

Rechercherichtung

Read the existing game implementation and the related issues #24 and #58 first; the payload names no files or test locations. Map the board controls, route tracing, puzzle generation and learning or timed modes, then define tests for rotation, tracing, generated solutions and keyboard play. Done means the listed tests pass and a browser test can solve, submit once and restart a small board.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement games help wanted

Part of #24. Depends on #58.

Student problem

Students need practice predicting how local rotations change a route through a larger board.

Scope

  • Divide an arrow board into rotatable blocks, beginning with one 3×3 block and adding larger arrangements.
  • Define controls to rotate a block's cell positions and, in a separate documented operation, rotate arrow directions inside it.
  • Trace from a stated entry to the required exit. Detect loops, empty cells, out-of-bounds paths and incorrect exits.
  • Generate boards from verified solutions and scramble only through reversible legal controls, so the visible controls can solve every puzzle.
  • Offer a route explanation/hint in learning mode and shared timed practice.
  • Provide keyboard controls and text/directional cues; keep free guest access.

Done when

  • Tests verify coordinate/direction rotation, inverse operations, tracing termination and invalid-route detection.
  • Generated boards have a checked solution reachable through the allowed controls.
  • A browser test solves a small board using keyboard controls, submits once and restarts.

Do not describe an arrow-route puzzle as a pathfinding algorithm tutorial unless that teaching content is included.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
1
Ø Merge
8 Std. 58 Min.
Gemergte PRs (30 T.)
37

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus procoderji-com/procoderji

Alle Issues in procoderji-com/procoderji

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.