Sound Not Playing
Custom sounds from a resource pack do not play and the log notes a missing sound event. The pack's sounds.json does not correctly register the sound under the key the game expects.
What does this error mean?
Custom sounds must be declared in sounds.json, mapping a sound event name to the audio files. A 'missing sound event' means the game asked for an event that the pack did not register, or registered under the wrong key.
Missing sound event
Most Common Causes
- A sound event missing from sounds.json.
- A typo in the event name or file path.
- Audio not in the required .ogg format.
- Files in the wrong sounds/ directory.
- Invalid JSON in sounds.json.
How To Diagnose
- Note the missing event name from the log.
- Open sounds.json and check that event is defined.
- Confirm the referenced .ogg files exist at the listed paths.
- Validate the JSON syntax.
Recommended Fixes
- Register the event
Add the missing sound event in sounds.json pointing to the correct .ogg file(s). - Fix paths and names
Match event names and file paths exactly, including namespace. - Convert to OGG
Ensure audio is Ogg Vorbis (.ogg), the only format Minecraft accepts. - Validate the JSON
Run sounds.json through a validator to catch syntax errors.
Frequently Asked Questions
Ogg Vorbis (.ogg). Other formats will not play.
Under assets/<namespace>/sounds/, referenced by sounds.json without the extension.
The game requested an event sounds.json never defined, add it or fix the name.