Neon Crates: play pasted levels in standard box-pushing notation

Aperta
#139 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
game-dev

Direzione di ricerca

Read games/crates/rules.ts lines 45–69 to understand parseLevel, then trace level selection in games/crates/scenes/SelectScene.ts and progress handling in games/crates/progress.ts. Check how existing tests are organized before running npm test. Done means valid pasted levels can be played, invalid input explains why it was rejected, and tests cover board-size and crate/target checks.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement help wanted severity: low

Summary

Neon Crates ships 15 levels, and its level parser already reads the standard box-pushing text notation. Letting players paste a level in that notation would give them something to play after level 15.

Where

  • games/crates/rules.ts:45-69 (parseLevel): accepts # . $ * @ + space -, and throws on anything else or a missing or doubled robot
  • games/crates/levels.ts:3-8, games/crates/scenes/SelectScene.ts
  • games/crates/progress.ts:33-43: progress is keyed by level name

Proposal

  • Add a CUSTOM entry to the select screen that takes pasted text, through a textarea overlay or a clipboard read on a user gesture.
  • Parse the text with parseLevel, and reject levels over the board size limit or with unequal crate and target counts.
  • Play custom levels without trophies, and keep their bests under a separate key validated like cleanProgress.
  • Treat the text as outside input: cap its length, and never render it as HTML.

Who benefits

Players who finish all 15 levels. Large free collections exist in exactly this notation.

Open questions

  • How should multi-level collections be handled (blank-line separated, with ; titles)?
  • Is clipboard read acceptable on iOS, or is a textarea needed?

Acceptance criteria

  • Pasting a valid level plays it, and pasting an invalid one shows why it was rejected.
  • Tests cover the size and crate/target checks.

Getting started

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

Filed by repo-audit/full-audit at a93de2e. Severity: low. Effort: M. audit-key: enhancement|games/crates/rules.ts|custom-levels

Lingua principale
TypeScript
Stelle
3
Fork
3
Merge medio
10h 22m
PR unite (30g)
6

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TMHSDigital/GH-Arcade

Tutte le issue di TMHSDigital/GH-Arcade

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.