> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/nativedb-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/nativedb-documentation/classes/gamegameaudiosystem.md).

# gameGameAudioSystem

## Description

Responsible for managing all audio-related functionality within the game. This system controls everything from background music and sound effects to character dialogue and environmental sounds.

Game sounds can be browsed and listened to on [SoundDB](https://sounddb.redmodding.org/).

Sounds can be replaced with [REDmod](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/modding-tools/redmod/audio-modding), with predefined [audio parameters](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/modding-tools/redmod/audio-modding#parameters).

If you need more control over how sounds can be played in-game, you might want to consider [Audioware](https://cyb3rpsych0s1s.github.io/audioware/).

## Functions

#### Play(eventName: CName, opt entityID: entEntityID, opt emitterName: CName) -> Void

Play a sound by its event name, optionally specifying an entity as emitter with its name.

Emitter name is used with chatters and subtitles.

#### Stop(eventName: CName, opt entityID: entEntityID, opt emitterName: CName) -> Void

Stop a previously played sound, optionally defined on an entity with specific name.

#### Switch(switchName: CName, switchValue: CName, opt entityID: entEntityID, opt emitterName: CName) -> Void

Switch from one sound to another, optionally specifying an entity as emitter with its name.

#### VoIsPerceptible(entityId: entEntityID) -> Bool

Whether entity's voice (a.k.a voiceover) can be heard from where player stands.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.redmodding.org/nativedb-documentation/classes/gamegameaudiosystem.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.