Bedrock Wiki
  • Discord
  • Contribute
  • bedrock.dev
  • MS Learn
Beginner's Guide
  • Guide
    • 1. Introduction
      guide
    • 2. Add-Ons Explained
    • 3. Software & Preparation
    • 4. Project Setup
    • 5. Create a Custom Item
    • 6. Create a Custom Entity
    • 7. Blockbench: Modeling, Texturing & Animating
    • 8. Adding Loot Tables, Spawn Rules & Crafting Recipes
  • Extra
    • a. Understanding JSON
    • b. Download Example Packs
    • c. Troubleshooting
      help
    • d. Advanced Manifest
    • e. Format Versions
    • f. Project Setup Android
Animation Controllers
  • Intro to Animation Controllers
    guide
  • Entity Commands
  • AFK Detector
  • Death Commands
  • Molang into Scoreboard
  • Respawn Commands
Blocks
  • General
    • Intro to Blocks
      guide
    • Block Components
    • Block Tags
    • Block States
    • Block Traits
    • Block Permutations
    • Block Events
      Scripts
    • Block Event Migration
      help
    • Blocks as Items
    • Multi-Blocks
    • Troubleshooting Blocks
      help
  • Sound & Visuals
    • Intro to Block Visuals
      guide
    • Block Culling
    • Block Models
      guide
    • Block Sounds
    • Block Texture Animation
    • Block Texture Variation
    • Block Tinting
    • N-Way Rotation
      guide
  • Tutorials
    • Applying Effects
      Scripts
    • Avoiding State Limit
    • Block Orientation
    • Fake Blocks
      Scripts
    • Ore Loot Tables
      Scripts
    • Tool-Based Destruction
  • Vanilla Re-Creations
    • Custom Crops
      Scripts
    • Custom Fences
    • Custom Glass
    • Custom Glazed Terracotta
    • Custom Heads
    • Custom Trapdoors
      Scripts
  • Documentation
    • Block Co-Location
    • Block Format History
    • Block Shapes
    • Redstone Components
    • Vanilla Block Models
    • Vanilla Block Sounds
    • Vanilla Block Tags
    • Vanilla Voxel Shapes
Commands
  • General
    • Intro to Command Blocks
    • Understanding Selectors
    • Functions
      guide
    • Block States
    • Coordinate System
    • Giving NBT Items
    • Scoreboard Operations
  • Commands
    • Damage
    • Execute
    • Playanimation
    • Playsound
  • On Event Systems
    • On First World Load
      function
    • On Player First Join
    • On Player Join
    • On Player Leave
    • On Player Death
    • On Player Respawn
  • Scoreboard Systems
    • Entity Counter
    • Scoreboard Timers
    • Comparing And Retrieving Scores
  • Detection Systems
    • Look Detection
    • Item Drop Detection
    • Movement Detections
    • Rain Detection
  • Techniques
    • Execute Logic Gates
      concept
    • Execute at Block Variant
    • Execution Forking
      concept
    • Binary in Commands
      concept
    • MBE - Max's Block Entity
    • FMBE - A New Way to Create Display Entities
    • Dynamic Displays
    • Orbital Camera
  • Useful Creations
    • Sphere Command
    • Compass Display
    • Custom Crafting
    • Multiplayer Position Rearrangement
      function
Concepts
  • contents.json
  • Molang
  • Namespaces
  • Overwriting Assets
  • Shaders
  • Sounds
  • Sounds (Server)
  • Subpacks
  • Texture Atlases
  • textures_list.json
Documentation
  • Advanced Molang
  • Aim Assist
  • File Types
  • Fog IDs
  • Material Configuration Description
  • Molang Queries
  • Pack Folder Structure
  • Shared Constructs
  • Sound Definitions
  • Vanilla Materials
Entities
  • General
    • Intro to Entities BP
      guide
    • Intro to Entities RP
      guide
    • Troubleshooting Entities
      help
    • Entity Events
    • Entity Properties
    • NPC Dialogue
    • Render Controllers
    • Spawn Rules
  • Tutorials
    • Area Effect Clouds
    • Coordinate Space Conversion
    • Creating Boats
    • Detecting Other Entities
    • Disabling Team Damage
    • Dummy Entities
    • Entity Attacks
    • Entity Movement
    • Entity Timers
    • Holding Items
    • Invulnerable Entities
    • Look at Entity
    • Riding Flying Entities
    • Sleeping Entities
    • Solid Entities
    • Spawning Tamed Entities
      Scripts
    • Village Mechanic
  • Documentation
    • Dummy Components
    • Non-Mob Runtime Identifiers
    • Projectiles
    • Runtime Identifiers
    • Vanilla Usage Components
    • Vanilla Usage Spawn Rules
Items
  • General
    • Intro to Items
      guide
    • Item Components
    • Item Tags
    • Item Events
      Scripts
    • Item Event Migration
      help
    • Item Catalog
    • Troubleshooting Items
      help
  • Tutorials
    • Equipment-Based Commands
    • Spawning Items
    • Throwable Items
  • Vanilla Re-Creations
    • Custom Armor
    • Custom Food
      Scripts
    • Custom Pottery Sherds
    • Custom Weapons
  • Documentation
    • Enchantments
    • Attachables
    • Item Format History
    • Numerical Item IDs
    • Vanilla Item Groups
    • Vanilla Item Tags
    • Vanilla Usage Components
JSON UI
  • General
    • Intro to JSON UI
      guide
    • Best Practices
      guide
  • Tutorials
    • Adding HUD Elements
    • Aseprite Animations
    • Buttons and Toggles
    • Dynamic Content Generation
    • Modifying Server Forms
    • Preserve Title Texts
    • Type Conversion
  • Documentation
    • JSON UI Documentation
Loot, Recipes & Trading
  • General
    • Trading Behavior
  • Documentation
    • Loot Tables
    • Trade Tables
    • Recipes
    • Item Functions
  • Tutorials
    • Randomized Structure Loot
Meta
  • Add-On Performance
  • Style Guide
  • Useful Links
  • Using Schemas
  • Version Control
  • Q&A
    • Blocks and Items Q&A 2024/08/30
    • Deferred Technical Preview Q&A 2024/02/23
    • GameTest Q&A 2021/08/06
    • Scripting and Editor Q&A 2023/09/22
    • World Generation Q&A 2024/11/15
NBT
  • General
    • .mcstructure
  • Tutorials
    • Enabling Experiments by Editing NBT
    • Extending Structure Limits
  • NBT in Depth
    • About NBT (Named Binary Tag)
    • NBT Libraries
    • Reading NBT Example
Particles
  • General
    • Intro to Particles
      guide
  • Tutorials
    • Disabling Particles
  • Documentation
    • Vanilla Particles
Scripting
  • General
    • Intro to Scripting
    • What is Script API?
    • API Modules
  • Tutorials
    • Script Core Features
    • Block Placement Prevention
    • Custom Commands
    • GameTests
    • Script Privileges
    • Script Requests API
    • Server Forms
  • Documentation
    • Engine Environment
    • Script Resources
    • Script Watchdog
    • Troubleshooting JavaScript
    • TypeScript
Servers
  • Software
    • Bedrock Server Software
  • Protocols
    • Bedrock Protocol
    • NetherNet Protocol
    • RakNet Protocol
Text & Localization
  • General
    • Intro to Text & Localization
    • Raw Text
    • Splashes
  • Emojis & Symbols
    • Fonts
    • Intro to Emojis
    • Custom Emojis
    • Input Keys
Visuals
  • General
    • Introduction to Entity Visuals
      guide
    • Bedrock Modeling
    • Custom Death Animations
    • Effects in Animations
    • Material Creations
    • Materials
    • Math-Based Animations
    • Skin Packs
  • Tutorials
    • Entity Texture Animation
    • Glowing Entity Texture
    • Hurt Animations
    • Leash Position
    • Player Geometry
    • Remove Entity Shadows
    • Retexturing Spawn Eggs
  • Ideas
    • Structure Presentation
World Generation
  • General
    • Intro to World Generation
      guide
    • Biomes
    • Client Biomes
    • Dimensions
    • Feature Types
    • Jigsaw Structures
  • Tutorials
    • Block Conditions for Features
    • Generating Custom Jigsaw Structures
    • Generating Custom Ores
    • Generating Custom Structures
    • Generating Patches
    • Heightmap Noise
  • Documentation
    • Biome Tags

Sounds (Server)

experimental
intermediate
Sounds (Server)
  • Folder Structure
  • Format
    • sound_event_name
    • duration_info
    • music_info
    • tags
    • broadcast_range
  • Script API
Related Pages
  • Sounds
Upcoming Creator Features

Server sound definitions lets behavior packs declare server-side sound definitions for sounds played from script. The game uses this metadata to track how long a sound plays, describe music, and limit how far a broadcast sound reaches.

WARNING

Server sound definitions do not register any audio. The sound event named in a definition must still exist as a custom sound added in a resource pack's RP/sounds/sound_definitions.json. See the Sounds page for how to add custom audio.

WARNING

Vanilla does not ship a server sound definitions file, so no vanilla sound has duration, music, or tag metadata. You also cannot add definitions for vanilla sounds yourself: every sound_event_name must be namespaced, and vanilla sound events such as random.pop have no namespace. Only your own namespaced sounds can be defined here.

Folder Structure ​

Server sound definitions live in a file called sound_definitions.json inside the behavior pack's sounds folder. This file shares its name with the resource pack file but has a completely different format, and the two are not related.

      • sound_definitions.json

Format ​

The file contains a single minecraft:server_sound_definitions array. Each entry in the array is one definition.

📝 BP/sounds/sound_definitions.json
json
{
    "format_version": "beta",
    "minecraft:server_sound_definitions": [
        {
            "sound_event_name": "wiki:my_cool_song",
            "duration_info": {
                "mode": "game_time",
                "seconds": 180.0
            }
        },
        {
            "sound_event_name": "wiki:my_other_song",
            "duration_info": {
                "mode": "real_time",
                "seconds": 12.5
            }
        },
        {
            "sound_event_name": "wiki:ambient_loop"
        }
    ]
}
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

sound_event_name ​

Required

The sound event this definition applies to. This is the same identifier you would pass to /playsound or playSound() in script. The identifier must include a namespace (for example wiki:my_cool_song), which means vanilla sound events cannot be given a server sound definition. It may not contain whitespace, and it is matched case-insensitively.

duration_info ​

Optional

Tells the game how long the sound lasts so it can track playback. Without this, the game has no idea when a sound ends. If present, both fields are required.

  • seconds - Length of the sound as a float.
  • mode - How elapsed time is measured:
    • "game_time" counts game ticks. Playback progress pauses while the game is paused or the tick rate slows.
    • "real_time" counts wall-clock time regardless of tick rate.

When set, the sound's progress is available through SoundInstance.durationInfo in script, and the world.afterEvents.soundCompleted event fires once the declared duration has elapsed.

music_info ​

Optional

Describes the musical content of the sound. All fields are optional.

  • genres - Array of strings.
  • moods - Array of strings.
  • artist - String.
  • title - String.
json
{
    "sound_event_name": "wiki:my_cool_song",
    "duration_info": {
        "mode": "real_time",
        "seconds": 180.0
    },
    "music_info": {
        "genres": ["electronic", "ambient"],
        "moods": ["calm"],
        "artist": "Wiki Composer",
        "title": "My Cool Song"
    }
}
1
2
3
4
5
6
7
8
9
10
11
12
13

tags ​

Optional

A map of arbitrary metadata. Each key is a tag name, and each value is either a single string or an array of strings. Neither keys nor values may contain whitespace. The game does not interpret tags itself; they exist so scripts can filter and look up definitions.

json
{
    "sound_event_name": "wiki:ambient_loop",
    "tags": {
        "category": "background",
        "regions": ["overworld", "nether"]
    }
}
1
2
3
4
5
6
7

broadcast_range ​

Optional

An XZ distance in blocks, as a float. When a sound with this definition is played as a broadcast (for example, dimension.playSound() with no target player), only players within this horizontal range of the sound's location receive it.

json
{
    "sound_event_name": "wiki:village_bell",
    "broadcast_range": 64
}
1
2
3
4

Script API ​

Server sound definitions are exposed to @minecraft/server in the beta version of the module. The main entry points are:

  • world.soundDefinitionRegistry.getDefinitions(filter?) - Returns the loaded SoundDefinition objects, optionally narrowed by a SoundDefinitionFilter. Filters can match on minDuration, maxDuration, genres, moods, artists, titles, and tags. String comparisons are case-insensitive, and an array matches when any provided value overlaps the definition's values.
  • SoundDefinition - Has soundEventId, durationInfo, musicInfo, and tags properties mirroring the JSON above.
  • player.playSound(definition) - Accepts a SoundDefinition in addition to a sound ID string.
  • SoundInstance - Returned when a sound is played. Exposes id, soundEventId, recipient, and durationInfo, which includes isActive and getPlaybackPosition().
  • world.afterEvents.soundCompleted - Fires when a tracked sound's declared duration elapses. The event's soundInstanceId matches the id of the SoundInstance that finished.

The example below plays a random calm song for a player and logs when it finishes.

📝 BP/scripts/main.js
js
import { world } from "@minecraft/server";

world.afterEvents.playerSpawn.subscribe(({ player, initialSpawn }) => {
    if (!initialSpawn) return;

    const songs = world.soundDefinitionRegistry.getDefinitions({
        moods: ["calm"],
        minDuration: 60,
    });
    if (songs.length === 0) return;

    const song = songs[Math.floor(Math.random() * songs.length)];
    const instance = player.playSound(song);

    const completed = world.afterEvents.soundCompleted.subscribe(({ soundInstanceId }) => {
        if (soundInstanceId !== instance.id) return;
        world.afterEvents.soundCompleted.unsubscribe(completed);
        player.sendMessage(`Finished playing ${song.musicInfo?.title ?? song.soundEventId}`);
    });
});
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

TIP

For the full and current API surface, see the Microsoft Learn documentation. These classes are in beta and may change between previews.

Contributors

Edit Sounds (Server) on GitHub

Bedrock Wiki by Bedrock OSS

"Minecraft" is a trademark of Mojang AB.

Bedrock OSS, Bedrock Wiki and bedrock.dev are not affiliated in any way with Microsoft or Mojang AB.

  • Privacy Policy
  • Join our Discord
  • Learn how to Contribute
  • Visit our Repository