Neon Crates: warn when a crate is stuck and offer a hint from the solver

未關閉
#126 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript
領域
frontend, game-dev

研究方向

Read games/crates/solver.ts and games/crates/rules.ts, then trace pushes and solved-state checks in games/crates/scenes/GameScene.ts:166-220. Run npm test and review the late levels in games/crates/levels.ts:175-190. Done means a push onto a non-live cell warns the player and tests cover live-cell checks; hint behavior and its open design questions still need decisions.

由索引模型根據 Issue 內容生成。

描述

enhancement help wanted severity: medium

Summary

Neon Crates gives no warning when a crate is pushed somewhere it can never leave, and has no hint. The solver that could provide both already exists in the repo, though only the tests use it.

Where

  • games/crates/solver.ts:3-5 ("used by the tests ... Not loaded by the game"), :31-47 (liveCells), :131 (solve)
  • games/crates/scenes/GameScene.ts:166-220 (step: moves and checks solved, nothing else)
  • games/crates/levels.ts:175-190 (late levels with par 50 and 68)

Details

liveCells(level) returns the cells from which a crate can still reach a target. solve(level) finds the fewest-moves path. Neither is used by the scene. The only way out of an unwinnable position is repeated UNDO or RESTART, with no sign that the position is already lost.

Proposal

  1. Dead-crate warning (cheap): compute liveCells once per level. When a push lands a crate on a cell that is not live, tint the crate red, play a short buzz and show an "UNDO?" banner. This means moving liveCells into rules.ts or bundling solver.ts.
  2. Hint: give solve an optional start state and a node limit, and add a HINT action. It flashes the next push direction, or shows "NO SOLUTION FROM HERE".

Who benefits

Players on the harder levels, who otherwise push for dozens of moves after a crate is already stuck and then give up. Touch players have only the UNDO and RESTART buttons today.

Open questions

  • Should hints be free, limited per level, or block the par trophy?
  • Should a hint search run in a Worker on large levels?

Acceptance criteria

  • Pushing a crate into a non-target corner shows the warning.
  • Unit tests cover the live-cell check on several levels.

Getting started

  • Relevant files: games/crates/solver.ts, games/crates/rules.ts, games/crates/scenes/GameScene.ts
  • How to run tests: npm test

Filed by repo-audit/full-audit at a93de2e. Severity: medium. Effort: M. audit-key: enhancement|games/crates/scenes/GameScene.ts|hint

主要語言
TypeScript
星號
3
分支
3
平均合併
10 小時 22 分鐘
30 天內合併 PR
6

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/GH-Arcade 的其他 Issue

查看 TMHSDigital/GH-Arcade 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。