GAME AUDIO / Agency Agents community
Interactive game audio planner
Plans event-driven game audio, state parameters, voice budgets and target-hardware profiling.
“Interactive audio specialist - Masters FMOD/Wwise integration, adaptive music systems, spatial audio, and audio performance budgeting across all game engines”
01 / THE REASONING
Why this made the selection.
- It connects gameplay state to middleware parameters and tests transitions such as combat, death and scene changes.
- Profiling includes maximum simultaneous voices, voice stealing, memory/CPU and streaming hitches on target storage.
- It requires gameplay audio to go through FMOD or Wwise events rather than direct AudioSource playback outside prototyping.
- Every event needs a voice limit, priority, and steal mode, and music and long ambience stream while short effects stay in memory.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- game-development/game-audio-engineer.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable
Our findings
- It connects gameplay state to middleware parameters and tests transitions such as combat, death and scene changes.
- Profiling includes maximum simultaneous voices, voice stealing, memory/CPU and streaming hitches on target storage.
- Integration rules ban direct AudioSource or AudioComponent playback in gameplay code except for prototyping, and ban hardcoded asset paths.
- Memory rules say no event ships with default voice, priority, or steal settings.
- Spatial rules say world-space effects use 3D and occlusion, not ignored 2D playback.
Not established by this review
- No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Use the role in your project.
- Read the pinned definition and MIT licence; review the host permissions before use.
- Use the original as a role reference; for .claude/agents/ create a host-valid working copy, supply the project inputs and constrain tools to the agreed files/environment.
- Provide engine/middleware versions, gameplay states, licensed audio assets and the lowest target hardware.
Before you start
- A host supporting adapted Markdown agent definitions
- The selected game/audio toolchain and authorized project assets
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/game-development/game-audio-engineer.md
Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE
Supports: Licence and attribution requirements
https://code.claude.com/docs/en/sub-agents.md
Supports: Host setup and permission defaults