Filter keyboard rows grounded by joystick buttons before processing actions, preventing right fire from acting as A/D/E and undoing its release rotation. Arm X and Y independently so an uncentered vertical axis cannot block steering. Reproduce both defects in host regressions, retain ordinary CMOC input APIs, and update official project membership. Compact unchanged display data and make render profiling optional to preserve the original memory and stack bounds. Deliver QUADPSL02.DSK with fresh scores. Retire the old artifact from tracking while leaving the loaded local disk untouched. Host suites, official Release build and MC6809/512 KB keyboard/audio smoke checks pass. Actual joystick-port confirmation and the reported normal-window buzz remain pending.
3.0 KiB
Numbered game disks
Brian requested this delivery convention on November 11, 2026:
QUADPSLxx.DSK, with a two-digit build number and fresh high scores for each
new delivered build. Begin at 01. The current delivery is 02; the next changed delivery is 03. This number
identifies the game disk, independently of the VCC Plus application build.
| Build | Date | Filename | Contents / validation |
|---|---|---|---|
| 01 | 2026-11-11 | QUADPSL01.DSK | Title spacing, credits, scoring labels and extra standard-library mute; historical artifact in Git |
| 02 | 2026-11-11 | QUADPSL02.DSK | Fix shared fire/keyboard rows and independently arm joystick axes; see JOYSTICK_FIX.md |
Build 01 is 161,280 bytes, SHA-256:
4ac171e87c51dfd99b302b9e035a91a59c030144e5ae0661a6d2dfc84ba3a63f.
It contains only QUAD.BIN, WORDS.DAT and QPTEXT.DAT, plus the existing DOS boot
track. Neither QPSAVE file is present, so the game starts with default preferences
and an empty scoreboard, creating save data through the normal save path.
The official build recipe continues producing the clean Quadrapassel.DSK
staging artifact. After a successful qualified build, inspect its directory for
unexpected files and personal QPSAVE data, then copy it without overwriting to
the next QUADPSLxx.DSK. Verify the copy hash equals the official artifact hash
and record the delivery here. Rebuilding unchanged content does not consume a
new number; a changed delivered candidate does. Do not reuse an old numbered
filename, migrate personal scores automatically, or overwrite/remount a user's
disk. Keep numbered deliveries distinct from writable playtest copies.
The name change alone required no guest code rebuild or new gameplay test: build 01's bytes match the already-tested artifact. It does not establish that the reported normal-window buzzing is fixed. Existing personal score disks and backups were left unchanged.
Brian authorized committing and pushing the implementation and build 01 on
November 11. The Git commit adding QUADPSL01.DSK records its source snapshot;
use git log -- QUADPSL01.DSK to identify that commit. The game bytes were
qualified before committing and are unchanged from the official artifact.
At the build-01 stage, Brian requested cleanup of obsolete builds. Build 01 was then the only retained current game delivery. Compiled objects, generated staging files, old probe/ staging images and host test scratch were removed after verification. Personal score backups and the mounted disk remain untouched; ignored WAV/JSON diagnostic evidence is retained while the normal-window buzz is unresolved. Historical source and selected evidence remain in Git.
Build 02 is the current clean delivery. SHA-256:
4e3af2440a3195ee5864498e39a779362988257d8a39cfc1c413157ace287a3c.
The old build-01 filename was observed loaded in VCC Plus, so that local disk is
left untouched during cleanup. Its pristine historical artifact remains in Git
history; it is excluded from future commits to protect any personal save writes.