§ How to · with Picoo
How to add sound and music in Roblox Studio
By Sametcan Tasgiran, Founder & Developer·Published ·Updated
Where you parent a Sound decides whether it is 3D, global, or silent — and that is the whole bug for most "my sound doesn't work" reports.
A Sound inside a BasePart is positional. Anywhere else it is global. Getting that one rule right removes most audio problems before they start.
Positional SFX
SoundKit.playSfx(name, part) parents the effect to that part, so Roblox applies distance falloff. SoundKit.playAt(name, position) does the same at any point in the world.
Global music
The playlist runs in a LocalScript and parents each track to SoundService, so music has no position and plays at the same volume everywhere.
Overlapping one-shots
Every playSfx call builds its own Sound and removes it with Debris afterwards, so rapid hits and clicks overlap instead of cutting each other off.
Music and SFX groups
Two SoundGroups in SoundService, Music and SFX, with SoundKit.setMusicVolume and SoundKit.setSfxVolume for a settings menu to call.
Playlist with fades
Tracks crossfade over 2 seconds and are shuffled so every track plays once before any repeats.
Server-triggered effects
Server code calls _G.SoundServer.broadcast(name) or _G.SoundServer.toPlayer(player, name), with an optional position. A server-to-client RemoteEvent carries it and each client plays the sound.
Files Picoo ships for this prompt
4 files · 240 lines · one recipe call
ReplicatedStorage.SoundKit
ModuleScript every script uses: the SoundKit.Music and SoundKit.SFX ID lists, the two SoundGroups, playSfx, playAt, preload and the volume setters.
121 lines
ServerScriptService.SoundServer
Lets server code play a named effect on every client or on one, through _G.SoundServer.
24 lines
StarterPlayer.StarterPlayerScripts.SoundClient
Preloads the sounds, runs the shuffled music playlist with crossfades, and plays the effects the server sends.
95 lines
ReplicatedStorage.Remotes.PlaySound
RemoteEvent that carries effect names from the server to clients. Only the server fires it.
instance
Sample output: ReplicatedStorage.SoundKit
-- Calling :Play() on a Sound that is already playing RESTARTS it, so a single
-- shared Sound instance can never overlap with itself. Rapid footsteps, hits or
-- clicks collapse into one audible sound. Each one-shot gets its own clone.
function SoundKit.playSfx(name: string, parent: Instance?): Sound?
local id = SoundKit.SFX[name]
if not id then
warn("[SoundKit] unknown effect '" .. name .. "' — add it to SoundKit.SFX")
return nil
end
if id <= 0 then
warn("[SoundKit] effect '" .. name .. "' has no asset id yet — set it in SoundKit.SFX")
return nil
end
local s = build(id, SoundKit.SfxGroup)
if not s then return nil end
-- PARENTING IS THE 3D SWITCH. Under a BasePart/Attachment the sound is
-- positional and falls off with distance; under SoundService it is global.
-- There is no property that decides this — only where it lives.
s.Parent = parent or SoundService
s:Play()
-- Clean up after it finishes. TimeLength is 0 until the asset loads, so a
-- fixed fallback is needed or unloaded sounds would leak instances forever.
Debris:AddItem(s, math.max(s.TimeLength, 5) + 1)
return s
end
--- Positional convenience: play at a point in the world.
function SoundKit.playAt(name: string, position: Vector3): Sound?
local anchor = Instance.new("Part")
anchor.Anchored = true
anchor.CanCollide = false
anchor.CanQuery = false
anchor.Transparency = 1
anchor.Size = Vector3.one
anchor.Position = position
anchor.Parent = workspace
Debris:AddItem(anchor, 12)
return SoundKit.playSfx(name, anchor)
endHow to add sound and music in Roblox Studio
Audio in Roblox has one rule that explains most of its confusion: a Sound parented to a BasePart or Attachment is positional, and a Sound parented anywhere else is global. Distance falloff, stereo panning, the sense that a noise is coming from over there — all of it follows from parenting, not from properties.
So the first question for any sound is where it lives. Footsteps, doors, machinery, an ability impact: parent them to the part that made the noise and let the engine do the distance work. Music, UI clicks, narration: those have no position, so they belong in SoundService or a client-owned container, and trying to give them falloff just makes them quieter for no reason.
The second most common problem is the asset. Roblox audio uploaded by another account is not usable in your place unless it is public — and the failure is silent. No error, no warning, just nothing. If a sound will not play and the code looks right, check ownership before you check anything else.
Falloff is shaped by RollOffMinDistance and RollOffMaxDistance, not by lowering Volume. Volume sets how loud it is at full strength; the rolloff pair decides where full strength ends and where it fades to nothing. Hand-fading volume by distance in a loop is a common workaround for a problem the engine already solves.
For music, two things separate a game that sounds finished from one that does not: crossfading between tracks instead of cutting, and putting music and SFX in separate SoundGroups so a player can turn one down without losing the other. Both are a few lines, and both are the kind of polish players notice only when it is missing.
Picoo's sound_system recipe, which answers prompts like "add background music" or "make a sound system with music and volume settings", builds that layout in three scripts. ReplicatedStorage.SoundKit holds every asset ID and the Music and SFX SoundGroups, a LocalScript runs the playlist with 2-second crossfades, and server code plays effects for everyone or for one player through a server-to-client RemoteEvent. It never invents an ID: the six standard effect slots are filled from a Creator Store search, and a slot the search cannot fill is left as a TODO that warns when played.
See more on the Luau generator, the AI Luau script writer, the 3D model generator and the game builder, read how Picoo compares with ChatGPT, or browse the full blog.
Frequently asked
Why is my Roblox sound not playing?+
Most often the asset: audio uploaded by someone else is not usable in your place unless it is public or you own it, and it fails silently. After that: the Sound is parented somewhere with no listener path, IsLoaded is still false when you call Play, or the volume is fine but RollOffMaxDistance puts the listener outside the audible radius.
How do I make a sound 3D?+
Parent it to a BasePart or Attachment. That single fact makes it positional — a Sound in ReplicatedStorage or SoundService is global no matter what its other properties say. Then shape the falloff with RollOffMinDistance and RollOffMaxDistance.
Should sounds play on the server or the client?+
Server if everyone should hear it (an explosion, a door). Client if it is feedback for one player (UI clicks, your own ability). Playing personal feedback on the server means everyone in the server hears your button clicks.
How do I let players control music and SFX separately?+
Two SoundGroups. The recipe creates Music and SFX groups in SoundService, assigns every Sound to one through its SoundGroup property, and gives you SoundKit.setMusicVolume and SoundKit.setSfxVolume to set each group's Volume. Ask for a settings menu with two sliders in a follow-up prompt and wire it to those two functions.
Can Picoo generate the audio itself?+
Picoo builds the system around audio that already exists on Roblox. The six standard effect slots (click, hit, coin, win, lose, explosion) are filled from a Creator Store search, with each pick's name and creator in a comment next to its ID. A slot the search cannot fill stays a TODO, and playing it prints a warning. Music IDs go in SoundKit.Music, or you can give them in the prompt. An asset ID is never made up, because a made-up rbxassetid fails to load without an error.
Related Picoo prompts
Roblox magic spell system
7 files · 422 lines · one recipe call. Three scripts, a folder with two RemoteEvents, and a hotbar ScreenGui you can restyle in Edit mode.
Roblox day night cycle
Example build: 3 files · 90 lines. Picoo writes this code for each prompt, so file names and line counts vary from run to run. A full day takes 24 real minutes in this example.
Roblox emote system
Example build: 4 files · 130 lines. Picoo writes this code for each prompt, so file names and line counts vary from run to run. This one has an 8-slot wheel.