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

Ouverte
#126 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
frontend, game-dev

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
TypeScript
Étoiles
3
Forks
3
Merge moyen
10 h 22 min
PR mergées (30 j)
6

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TMHSDigital/GH-Arcade

Toutes les issues de TMHSDigital/GH-Arcade

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.