Building
Sounds
A Sound is an audio clip in your pack, usually generated from a description. It either replaces a noise the game already makes (a creeper's hiss, a chest opening) or becomes a new sound that commands and plugins can play, such as a laser or a level-up jingle for your server.

Replacing a sound, or adding a new one#
Every sound in Minecraft has an event name, such as
entity.creeper.primed. You set it under Sound event when you add a sound,
and it alone decides what your sound does. There is no separate "replace"
setting.
- 1
Name it after a vanilla event
entity.creeper.primed,block.chest.open,entity.player.levelup. The pack's audio replaces the game's, everywhere the game would have played it. Nothing has to run a command, and nothing has to know your pack exists. - 2
Name it something new
custom.laser,boss.phase_two. Nothing triggers it on its own; it's a sound waiting for something to play it, by command or from a plugin.
Both land in the minecraft namespace, so a new event is played as
minecraft:custom.laser.
Making one#
Open a pack, press Add asset and pick Sound. Describe it the way you'd describe it to someone who has to make it:
a heavy iron door dragging open, stone grinding, echoing hall
| Setting | What it does |
|---|---|
| Sound event | Its name, which decides whether it replaces a vanilla sound. See above |
| Play as | The volume slider the play command uses. See Categories |
| Length | 0.5 to 30 seconds. Leave it blank and the AI picks. A sound padded with silence feels sluggish in game |
| Loop | One-shot, or Seamless loop for something that plays continuously |
| Takes | How many versions one prompt makes, 1 to 10 (4 by default) |
Takes matter most: making four and keeping the best is usually the difference between a sound that works and one that doesn't. Each take is charged, and above six they run in two batches, so it takes about twice as long.
You can also Upload audio you already have.
Choosing a take#
Every take is on the sound's page as a waveform you can play. Use this take picks the one the pack ships; the rest stay for comparison until you delete them. Generate another take adds a new one to the list without replacing any.
- Make this take its own sound copies a take you also want to keep into a
new sound on the next free event name (
custom.laserbecomescustom.laser_2), since one event plays one file. - Edit with AI describes a change ("deeper", "less echo") and generates it as a new take, so the take you had stays in the list. Audio can't be changed in place.
The event name and category can be changed later, so a sound made as a new event can be renamed onto a vanilla one without generating it again.
Hearing it in game#
A replacement plays wherever the game would have played the vanilla sound. To hear any sound on demand, first send the pack to yourself: on a server running RP Engine, our free plugin, press Sync. The sound's page then has a play command, and a button that plays it to you:
/rp sound studio:<id> @pThat's RP Engine's command, and it needs the rpengine.sound
permission (op by default). Vanilla's /playsound works too, also for
operators:
/playsound minecraft:custom.laser player @pA player can only hear a sound their pack has. Sync the pack to them first; playing an event they don't have does nothing, with no error.
Several sounds on one event#
Give two sounds the same event name and Minecraft picks between them at random each time it fires, the way vanilla gives a block several footstep noises. Nothing extra to switch on.
Categories are not a pack setting#
A sound's category (which volume slider controls it) can't be set by a resource pack on Java. The game takes it from whatever plays the sound.
That means:
- Replacing a vanilla event keeps that event's original category. Your audio replaces the creeper fuse, and it's still a Hostile Creatures sound.
- A new event has no category of its own at all. It gets one per playback,
from the
sourceargument of whatever command fires it, so in practice the category is chosen by whoever writes the command, not by the pack.
Play as in Studio is the category it puts in the commands it writes for you. It isn't stored in the exported Java pack.
Bedrock is the opposite: its sound definitions do take a category. If you've read Bedrock docs, this is the difference that catches people.
What's in the exported pack#
assets/minecraft/sounds.json
assets/minecraft/sounds/<name>.oggFiles are Ogg Vorbis, mono. Both parts matter:
- Minecraft reads Ogg Vorbis only. Ogg Opus has the same extension and plays in every desktop audio player, and the game refuses to load it.
- Minecraft only attenuates and pans a sound positionally if it has one channel. A stereo effect plays flat, at full volume, wherever the player is standing.
Sounds longer than ten seconds are marked stream, which is what vanilla does
for music and records: decoded as they play rather than loaded whole.
On Bedrock#
Sounds are included. The .mcpack carries your audio and a
sound_definitions.json that names each sound exactly as you named its event,
so the same play command reaches both editions on a server running
RP Engine and Geyser. Bedrock reads the category from the pack, so yours is carried
over (master and voice, which Bedrock doesn't have, become neutral and
player).
Replacing a vanilla sound needs the plugin
A sound named after a vanilla event, like entity.creeper.primed, replaces
that sound on Java. Geyser plays vanilla sounds under Bedrock's own names, so
on a server running RP Engine the plugin adds your replacement
under that name too, and Bedrock players hear it. A .mcpack installed by
hand, with no server involved, can't know the Bedrock name, and there the
replacement is Java-only. A few vanilla sounds are played by Bedrock itself
rather than by name and can't be replaced on Bedrock at all.