Sound and Particles: Give Clear Feedback on Success

Learning route

Prepare first, then do it; after seeing the result, remember to save it.

Every time a small step is completed, it is tested. Say what you expect to see first, and then use Play and Output to check it. Don't rush to write all the code at once.

Step by step

01 · Organize effects in the same Part

Create FeedbackPad and add Prompt, Attachment, ParticleEmitter, and Sound. Place the ParticleEmitter under Attachment to easily determine the particle emission position.

Audio only uses resources that you have the right to use, and which experience has access rights.

1. FeedbackPad: Size=6,1,6, Position=0,0.5,-10, Anchored=true.
2. Add ProximityPrompt, ActionText=test feedback, MaxActivationDistance=10.
3. Add Attachment: BurstPoint, Position=0,2,0; put ParticleEmitter: Burst inside.
4. Burst.Enabled=false, Lifetime=0.5 to 0.8, Speed=4 to 6, SpreadAngle=45,45; Texture can be built-in rbxasset://textures/particles/sparkles_main.dds.
5. Add Sound in FeedbackPad: SuccessSound, Volume=0.25, and leave SoundId blank first; then add Script: Feedback.

Step by step

02 · Prepare text that does not rely on sound first

Use BillboardGui to display status above the site. Text can help players who don’t turn on the sound to confirm the results, instead of using “did you hear it” as the only acceptance?

This lesson is a shared feedback platform: if one person activates it, other nearby players can also see the effect, so use a global busy lock.

1. Reads the part of the script that creates BillboardGui.
2. The text first displays "Ready", and after triggering it is changed to "Test successful! ”, and then resume after one second.

Step by step

03 · Emit once, do not leave the effect on all the time

Enabled=false does not prevent the use of Emit(20) to emit particles once. This way you can accurately control the amount of this effect instead of always turning on the Rate spray.

Skip the sound if SoundId is empty. Even if the resource does not have permission, text and particles should be effective feedback, and the mechanism cannot be stuck waiting for the audio to be loaded.

1. Paste the complete script.
2. After playing, press the prompt and observe the text and short particles.
3. Set the SoundId when there is suitable audio, and keep the volume soft.

local pad = script.Parent
local prompt = pad:WaitForChild("ProximityPrompt")
local burst = pad:WaitForChild("BurstPoint"):WaitForChild("Burst")
local sound = pad:WaitForChild("SuccessSound")
local busy = false
local board = Instance.new("BillboardGui")
board.Size = UDim2.fromOffset(220, 56)
board.StudsOffset = Vector3.new(0, 4, 0)
board.AlwaysOnTop = true
board.Adornee = pad
board.Parent = pad
local label = Instance.new("TextLabel")
label.Size = UDim2.fromScale(1, 1)
label.TextSize = 24
label.Text = "准备好"
label.Parent = board

prompt.Triggered:Connect(function(player)
    if busy then return end
    local character = player.Character
    local root = character and character:FindFirstChild("HumanoidRootPart")
    local hum = character and character:FindFirstChildOfClass("Humanoid")
    if not root or not hum or hum.Health <= 0 then return end
    if (root.Position - pad.Position).Magnitude > 12 then return end
    busy = true
    label.Text = "测试成功！"
    burst:Emit(20)
    if sound.SoundId ~= "" then sound:Play() end
    task.wait(1)
    label.Text = "准备好"
    busy = false
end)

Step by step

04 · Controlling the quantity is more important than the heap effect

Lifetime determines how long particles can live, and Speed determines the speed. With a large number and long lifespan, more particles will exist in the picture at the same time, and the equipment will need to handle more things.

Do not use fast and intense flashes to express ordinary success. Short and soft feedback is more suitable for long-term play, and should be understandable even when the sound is turned off.

1. Compare Emit(10) and Emit(20) and choose the one that can be seen clearly.
2. Try starting the volume from 0.25, without using the maximum volume.
3. Only set the SoundId after confirming that the resource has access.

Step by step

05·Try both silent and fast repeat

Turn off the computer or game volume and try again. The text should still explain what happened. Press the prompts again and again to confirm that multiple rounds of effects will not be superimposed during busy periods.

If the particles are not displayed, first check the Attachment path, Texture and emission position; if only the sound fails, check the resource permissions and Output.

1. Silent test once.
2. Press five times quickly to confirm that the feedback does not superimpose infinitely.
3. Observe whether particles are blocking the road in the smaller field of view of the device simulation.

Exit questions

Answer it yourself first, and then expand on it.

Explore further

This is where we start when we need to check the data.

The text code can be copied directly. First confirm the script type, placement, and whether this code is a complete version or a small experiment; do not run multiple versions of the same script superimposed. The source of the interface reference picture has been marked. The object names in the picture may be different from those in this lesson. Please refer to the operation steps.

• Particle emitter ↗
• Sound object ↗