games: add Key and Door for directed-maze planning
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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.
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 1
- 平均合併
- 8 小時 58 分鐘
- 30 天內合併 PR
- 37
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
procoderji-com/procoderji 的其他 Issue
-
area:frontend bug
難度 2/5 1-3 小時 新手友好度 62/100
procoderji-com/procoderji#104 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 88/100
procoderji-com/procoderji#36 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 85/100
procoderji-com/procoderji#35 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 79/100
procoderji-com/procoderji#34 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 90/100
procoderji-com/procoderji#33 ·
維護者通常 1 天內回覆
查看 procoderji-com/procoderji 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
bug platform-android
難度 2/5 1-3 小時 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 則留言 ·
維護者通常 2 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
難度 1/5 1 小時以內 新手友好度 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆