45 lines
2.4 KiB
Markdown
45 lines
2.4 KiB
Markdown
# Development and review checklist
|
|
|
|
The CoCo 3 game is implemented. This document is a checklist for modifications,
|
|
not a product roadmap. Start with [README](../README.md), [AGENTS](../AGENTS.md),
|
|
the [behavioral specification](../SPECIFICATION.md), and the
|
|
[current status](IMPLEMENTATION_STATUS.md).
|
|
|
|
## Establish the baseline
|
|
|
|
- Build an unchanged checkout with stock VCC Plus using Release and the project Makefile.
|
|
- Keep a writable test disk separate from existing personal score disks.
|
|
- Read the installed CMOC/API manuals and discover the selected project's live MCP capabilities.
|
|
- Record the source revision, configuration, artifact hash and actual guest machine/RAM.
|
|
|
|
## Make a focused change
|
|
|
|
Keep game rules separate from display, input and disk adapters. Prefer standard
|
|
CMOC APIs. The existing bounded C graphics exception is documented in
|
|
[DECISIONS](DECISIONS.md); it does not justify unrelated low-level changes.
|
|
For a new exception, explain the player-visible need, standard API evidence,
|
|
alternatives, affected files, memory effects and validation to the fork's owner
|
|
before implementing it.
|
|
|
|
## Validate affected behavior
|
|
|
|
- Rules: spawn/collision, all rotation states, kicks, rejected moves, gravity, drops, clears, hold and shadow.
|
|
- Scoring: both formulas, resulting-level multiplication, bottom clears, score width and category identity.
|
|
- Selection: repeatable seeds, weighted selection and difficult-piece simulation without state corruption.
|
|
- Input: repeat timing, shared keyboard/button lines, both ports, calibration, pause/release and menu guards.
|
|
- Storage: save/reload, read-only/corrupt/partial data, recovery, reset/cancel and active-game eligibility.
|
|
- Display/audio: readable text, all screens, changed-region rendering and quiet intervals between effects.
|
|
- Memory: enforced code/data bounds, stack reserve, BASIC workspace and safe disk I/O.
|
|
|
|
Host tests complement actual guest play. Check 128 KB operation when a change
|
|
affects memory. A keyboard check does not establish joystick behavior; a 512 KB
|
|
run does not establish a new build's 128 KB behavior. Report unavailable checks
|
|
honestly and preserve useful fixtures and unmodified guest screenshots.
|
|
|
|
## Deliver a variant
|
|
|
|
Keep licensing and component notices, update the manual for changed controls or
|
|
rules, and document the build and loading commands. Number changed game deliveries
|
|
without overwriting old downloads or personal disks. Commit, push and publish only
|
|
within the fork owner's requested scope.
|