Sound effects toggle does nothing: no audio files are in the repository
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start with js/config.js and js/utils.js to trace the configured sound paths and playSound, then inspect index.html and the game-end handling. Check the existing README and roadmap claims against the shipped behavior. Done means the sound toggle works for all listed events or is hidden, and the README and roadmap accurately describe the result.
Written by the indexing model from the issue text.
Description
Summary
The settings panel has a "Sound effects" toggle and the README lists sound as a feature, but assets/sounds/ does not exist. Turning the toggle on gives no sound and one failed request per move.
Where
js/config.js:38-45(CONFIG.ASSETS.SOUNDSpaths)js/utils.js:184-193(playSound, failure only logged)index.html:50-56(the toggle)README.md:89,README.md:106,README.md:164(feature claims);README.md:295andCHANGELOG.md:13say the files still need addingdocs/ROADMAP.md:71(marked done)
Impact
Users enable the toggle and hear nothing. GAME_END is configured but never played.
Steps to reproduce
- Enable "Sound effects".
- Make a move. No audio; the network tab shows a failed request for
assets/sounds/move.mp3.
Suggested fix
Either add six small, permissively licensed audio files, or synthesize short tones with the Web Audio API in playSound (no binary assets needed). Until then, hide the toggle and correct the README and ROADMAP lines. Play the game-end sound on checkmate and stalemate.
Acceptance criteria
- Enabling the toggle produces sound for move, capture, check, castle, promotion and game end, or the toggle is hidden
- README and ROADMAP match what ships
Getting started
- Relevant files:
js/config.js,js/utils.js,index.html,README.md - How to run tests:
npm install, thennpm testandnpm run lint - Related docs:
docs/ARCHITECTURE.md,.github/CONTRIBUTING.md
Filed by repo-audit/full-audit at 8a2c86c. Severity: low. Effort: S. audit-key: bug|js/config.js|ASSETS.SOUNDS
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/Static_Chess
-
enhancement good first issue severity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TMHSDigital/Static_Chess#53 ·
-
documentation good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Static_Chess#49 ·
-
documentation good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
TMHSDigital/Static_Chess#48 ·
-
documentation severity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TMHSDigital/Static_Chess#47 ·
-
documentation good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TMHSDigital/Static_Chess#46 ·
All issues in TMHSDigital/Static_Chess
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
good first issue tests
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug role: dev-lead
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
briangwalker/TrussExplorer#424 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
eliasstravik/herdr-projects#1032 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100