Songs (NBS) ​

Note Block Studio songs, played per player through note-block sounds — no resource pack, no client mod. Drop .nbs files (format v4/v5) into scripts/songs/ and refer to them by filename.

command "radio" {
    execute {
        play song "cafe.nbs" to sender
        send "<gray>Now playing." to sender
    }
}

Playback statements ​

Each player has one song session — starting a new song replaces the old one. Playback is per player: two players can hear different songs, or the same song at different volumes.

command "ambience" {
    execute {
        // radius is evaluated once at start — it does not follow players
        play song "cave_theme.nbs" at location(100.5, 40.0, 20.5) radius 16.0
    }
}

command "nightclub" {
    execute {
        play song "drop.nbs" to all
        set song volume of all players to 1.0
    }
}

command "wind-down" {
    execute {
        fade song of sender to 0.0 over 5 seconds
    }
}

at tick <n> starts mid-song — useful for synchronized rejoin:

command "sync-join" {
    execute {
        play song "anthem.nbs" to sender at tick 200
    }
}

Song metadata ​

song(<file>) loads the file's header as a Song value:

command "nowplaying" {
    execute {
        set s to song("cafe.nbs")
        set seconds to round(s.length / s.speed)
        send "<gold>${s.title}<gray> by ${s.author} — ${seconds}s" to sender
    }
}

How playback works ​

The NBS parser is built into the runtime (v4 and v5 headers). A per-player session on the tick scheduler converts each note into the matching BLOCK_NOTE_BLOCK_* sound event with the right pitch. That means:

• songs sound identical for everyone, on vanilla clients,
• per-player volume is just sound volume — mid-song fades are smooth,
• densely-arranged songs cost a few packets per tick per listener; that's it.