Make every sound serve gameplay information, atmosphere, or accessibility, and ensure it concludes correctly on repeat, stop, and object destruction. Before starting, read the experience direction, event list, asset registry, andStudio plugin routing。
Responsibilities and Inputs
- Inspect existing Sound, SoundGroup, asset IDs, calling scripts, trigger frequency, playback positions, and target device budgets.
- Clarify whether an event belongs to UI, gameplay feedback, ambience, music, or voice prompts, and determine source, authorization, priority, looping, attenuation, and whether it can be interrupted.
- Purchasing, downloading, or uploading audio requires explicit user authorization; do not integrate when asset licensing is unknown.
- Real-time voice chat and external voice services are beyond the scope of ordinary Sound integration; leave direction to the designer and plan dependencies and privacy requirements separately.
- When audio sources, voice privacy, or cost involve trade-offs that cannot be resolved by evidence, hand off tointerrogation skillto obtain a decision; proceed directly with ordinary implementation within existing sound effect integration authorization.
Execution Steps
- For each event, record trigger conditions, consumers, audio asset IDs, loudness intent, spatial position, duration, priority, and silent degradation behavior.
- Use appropriate SoundService/SoundGroup routing and player volume settings by purpose, avoiding separate volume implementations duplicated across scripts.
- For spatial sounds, clarify playback position and RollOff behavior; for UI/non-spatial prompts, clarify whether their visibility scope is local or all players.
- For repeated triggers, define replay, merge, rate-limit, replace, or ignore strategies; for concurrency peaks, set clear priorities and acceptable limits.
- Bind playback objects to the appropriate client or server side, ensuring non-authoritative prompts do not change rules and server sounds are not incorrectly broadcast repeatedly.
- Clean up connections, tasks, and playback objects on stop, character switch, object pool recycling, UI close, and player exit.
- Use real target audio assets to check load failures, muting, pause/resume, continuous triggering, device switching, and multiplayer spatial behavior.
Delivery and Verification
- Deliver the audio event table, source licensing, asset IDs, Sound routing, spatial parameters, volume settings, concurrency strategy, and cleanup responsibilities.
- Use instance inspection and script search to confirm Sound objects and trigger calls; confirm event order and console results through Studio run flows.
- Record actual devices, audio asset versions, simultaneous playback counts, and measurement methods; do not report budget pass without data.
- Hand off events that need to sync with combat or UI feedback to juice; hand off looping, peak, muting, and lifecycle scenarios to QA.
- Audio linked to the same gameplay events is managed by Feedback and Motion for mapping, and asset licensing and runtime evidence are handed to QA for review.
Do not use infinite loop connections or create uncleaned objects on every playback. Audio visuals and listening must be checked manually; screenshots cannot prove audio plays correctly.
Sound Lifecycle Check
- Confirm actual SoundId, load status, and asset permissions in the Experience; do not infer that a sound is playable just because the object exists.
- Define stop/destroy responsibility for one-shot sounds; looping music defines pause, transition, scene change, and re-entry behavior.
- Manage adjustable volume categories through a shared SoundGroup to avoid duplicating the same volume logic separately for each Sound.
- Specify priorities for key cues in noisy scenes to prevent footsteps and ambient sounds from drowning out reward, hit, or danger cues.
- Store player volume preferences separately from server-authoritative state so client volume does not affect game rules.
- For multiple players' spatial sounds, specify who can hear them, the attenuation range, and when they disappear.
- Before reusing an object pool, check that the old Sound has stopped, old connections have been removed, and properties have been reset.
- For voice, UGC audio, and chat scenarios, separately check platform capabilities, user safety, and data handling requirements.
- When authorization is missing or a resource is inaccessible under the target account, provide an alternative that already has authorization.