Game Audio Implementation
Create an audible feedback and storytelling system that remains legible, culturally permissioned, memory-conscious, localisable and useful even when the device is muted.
Prerequisites
Load the approved game-state map, narrative/cultural governance, rights policy, localisation plan and selected engine integration constraints.
Use When
- Building an audio bible, event map, buses, adaptive score, ambience, Foley, voice pipeline, subtitle timing, spatial mix, or audio performance budget.
Do Not Use When
- Audio is only a late asset-drop or living/restricted repertoire has not been cleared.
Required Inputs
Game states and event taxonomy, narrative/cultural boundaries, rights and performer agreements, device/speaker/headphone contexts, localisation plan, engine/middleware, memory/voice budgets and accessibility needs.
Workflow
- Define audio pillars, listener perspective, silence policy, event vocabulary and required non-audio equivalents.
- Map music, ambience, Foley, UI, dialogue and creature/character states to gameplay events and priorities.
- Commission or record only after repertoire, performers, consent, credits, territories and reuse rights are clear.
- Edit, name, loudness-check, loop, tag and version source/master/runtime files.
- Implement buses, snapshots, concurrency, variation, ducking, spatial ranges, occlusion and adaptive transitions.
- Integrate subtitles, pronunciation guides, localisation context and lip/gesture timing where required.
- Profile voices, decoding, streaming, memory, CPU and package size on target devices; test speakers, headphones, mute and interruption.
Quality Standards
- Pair every gameplay-critical sound with visual or haptic communication.
- Prevent repeated sounds from becoming fatiguing through variation and concurrency control.
- Preserve source, licence, performer, consent and cultural restriction metadata.
- Make mix states recover correctly across pause, focus loss, calls, backgrounding and route changes.
Anti-Patterns
- Music carrying required information. Fix: redundant communication.
- Sacred recording used as generic ambience. Fix: permission, contextual limits or original commissioned substitute.
- Unlimited simultaneous voices. Fix: priorities, caps and virtualisation.
- MP3/streaming/compression choice by habit. Fix: measure per asset class and engine.
- Voice recorded before final terminology. Fix: language and cultural gate first.
Outputs
Audio bible; rights ledger; event/bus map; recording and localisation pack; integrated banks/assets; mix and accessibility test; performance evidence and release stems.
References
- Audio production and implementation
- Cultural, rights and localisation gates
Decision Rules
| Asset |
Default treatment |
| Short frequent effect |
Memory-resident only if measured and bounded |
| Long music/ambience |
Evaluate streaming and transition cost |
| Critical dialogue |
Subtitle, context note, pronunciation and fallback |
| Restricted or unclear repertoire |
Do not record or ship |
Read Next
Use game-testing-polish for perceptual QA and mobile-game-release-liveops for privacy and download-pack policy.
1---2name: game-audio-implementation3description: Use when designing, recording, licensing, editing, integrating, mixing, localising, profiling, or testing game music, ambience, dialogue, UI, Foley, spatial audio, and adaptive audio systems.4metadata: {portable: true, compatible_with: [claude-code, codex]}5---67# Game Audio Implementation8Create an audible feedback and storytelling system that remains legible, culturally permissioned, memory-conscious, localisable and useful even when the device is muted.910## Prerequisites1112Load the approved game-state map, narrative/cultural governance, rights policy, localisation plan and selected engine integration constraints.13<!-- dual-compat-start -->14## Use When15- Building an audio bible, event map, buses, adaptive score, ambience, Foley, voice pipeline, subtitle timing, spatial mix, or audio performance budget.16## Do Not Use When17- Audio is only a late asset-drop or living/restricted repertoire has not been cleared.18## Required Inputs19Game states and event taxonomy, narrative/cultural boundaries, rights and performer agreements, device/speaker/headphone contexts, localisation plan, engine/middleware, memory/voice budgets and accessibility needs.20## Workflow211. Define audio pillars, listener perspective, silence policy, event vocabulary and required non-audio equivalents.222. Map music, ambience, Foley, UI, dialogue and creature/character states to gameplay events and priorities.233. Commission or record only after repertoire, performers, consent, credits, territories and reuse rights are clear.244. Edit, name, loudness-check, loop, tag and version source/master/runtime files.255. Implement buses, snapshots, concurrency, variation, ducking, spatial ranges, occlusion and adaptive transitions.266. Integrate subtitles, pronunciation guides, localisation context and lip/gesture timing where required.277. Profile voices, decoding, streaming, memory, CPU and package size on target devices; test speakers, headphones, mute and interruption.28## Quality Standards29- Pair every gameplay-critical sound with visual or haptic communication.30- Prevent repeated sounds from becoming fatiguing through variation and concurrency control.31- Preserve source, licence, performer, consent and cultural restriction metadata.32- Make mix states recover correctly across pause, focus loss, calls, backgrounding and route changes.33## Anti-Patterns34- Music carrying required information. Fix: redundant communication.35- Sacred recording used as generic ambience. Fix: permission, contextual limits or original commissioned substitute.36- Unlimited simultaneous voices. Fix: priorities, caps and virtualisation.37- MP3/streaming/compression choice by habit. Fix: measure per asset class and engine.38- Voice recorded before final terminology. Fix: language and cultural gate first.39## Outputs40Audio bible; rights ledger; event/bus map; recording and localisation pack; integrated banks/assets; mix and accessibility test; performance evidence and release stems.41## References42- [Audio production and implementation](references/audio-production-implementation.md)43- [Cultural, rights and localisation gates](references/audio-rights-localisation.md)44<!-- dual-compat-end -->45## Decision Rules46| Asset | Default treatment |47|---|---|48| Short frequent effect | Memory-resident only if measured and bounded |49| Long music/ambience | Evaluate streaming and transition cost |50| Critical dialogue | Subtitle, context note, pronunciation and fallback |51| Restricted or unclear repertoire | Do not record or ship |52## Read Next53Use `game-testing-polish` for perceptual QA and `mobile-game-release-liveops` for privacy and download-pack policy.
peterbamuhigire