Context
Found in the BMS spec-compliance audit. Per hitkey's command memo, visible notes span #xxx11-1Z (1P) / #xxx21-2Z (2P); the alphabetic tail is used by keyboard-mania-style and other extended-lane charts.
Current behavior
Only 11-19 / 21-29 are extracted as playable notes — packages/player/src/playable-notes.ts accepts lane characters 1-9 only. The 24 KEY SP / 48 KEY DP lane-mode estimation and key bindings exist in packages/player/src/core/lane-layout.ts, but the extended channels themselves never become score/judge targets, so such charts play silent and judgeless.
This is currently a documented limitation (docs/player-spec.md BMS support matrix), so this issue is the tracking item for lifting it.
Suggested scope
- Extend the playable-channel classification (
@be-music/chart channel predicates + playable-notes.ts) to the alphabetic lane range.
- Wire the extracted notes into the existing 24/48-key lane layouts and input bindings.
- Cover with extraction + judging tests and update the support matrix in
docs/player-spec.md / .ja.md.
Context
Found in the BMS spec-compliance audit. Per hitkey's command memo, visible notes span
#xxx11-1Z(1P) /#xxx21-2Z(2P); the alphabetic tail is used by keyboard-mania-style and other extended-lane charts.Current behavior
Only
11-19/21-29are extracted as playable notes —packages/player/src/playable-notes.tsaccepts lane characters1-9only. The24 KEY SP/48 KEY DPlane-mode estimation and key bindings exist inpackages/player/src/core/lane-layout.ts, but the extended channels themselves never become score/judge targets, so such charts play silent and judgeless.This is currently a documented limitation (
docs/player-spec.mdBMS support matrix), so this issue is the tracking item for lifting it.Suggested scope
@be-music/chartchannel predicates +playable-notes.ts) to the alphabetic lane range.docs/player-spec.md/.ja.md.