> For the complete documentation index, see [llms.txt](https://black-horizon-studios.gitbook.io/emerald-ai-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://black-horizon-studios.gitbook.io/emerald-ai-wiki/emerald-profiles-and-objects/sound-profile.md). # Sound Profile

## Using the Sounds Profile A Sound Profile holds all of an AI's sound data. This allows AI the option to share the same sound data with only needing to rely on a single Sound Profile. Any changes made to a Sound Profile will affect any AI using that Sound Profile. However, as many sound profiles can be created as needed. {% hint style="warning" %} **Important:** Some sounds require an Animation Event to be played. These are covered in the tutorial sections below . {% endhint %} {% hint style="success" %} Here are the available tutorials and guides for the Sound Profile. {% endhint %}


Creating an AI's Sound Profile	CreateNewSoundProfileButton.png	Creating an AI's Sound Profile
Setting Up Footstep Sounds	SoundProfileEditor.png	Setting up Footstep Sounds
Setting Up Attack Sounds	SoundProfileEditor.png	Setting up Attack Sounds
Setting Up Warning Sounds	SoundProfileEditor.png	Setting up Warning Sounds
Setting Up Death Sounds	SoundProfileEditor.png	Setting up Death Sounds

--- # 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://black-horizon-studios.gitbook.io/emerald-ai-wiki/emerald-profiles-and-objects/sound-profile.md?ask=&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.