# Sounds

## Default sounds.yml

```yaml
sounds:
  gg-wave-started-1: "minecraft:entity.boat.paddle_water:0.5:3.0"
  gg-wave-started-2: "minecraft:item.goat_horn.sound.0:0.5:3.0"
  gg-wave-message: "minecraft:block.note_block.banjo:0.5:3.0"
  purchase-message: "minecraft:item.goat_horn.sound.7:0.1:3.0"
  sale-activated: "minecraft:block.beacon.activate:0.5:3.0"
```

* `gg-wave-started-1`: This sound is played when a GGWave stars.
* `gg-wave-started-2`: This sound is played when a GGWave stars.
* `gg-wave-message`: This sound is played when a player triggers the GGWave. The pitch increases every time up until a specific point then resets again.
* `purchase-message`: This is played when a purchase is broadcasted
* `sale-activated`: This is played when a sale was activated.

## What does the value represent ?

> These are simple key value pairs. The key represents the internal sound name and the value consists of `mc sound namespace and name:volume:pitch`.

## Can I disable a sound ?

> You can disable a sound by simply setting its value to an empty string. Ex: `test-sound: ""`


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://obey.gitbook.io/wiki/storedata/sounds.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.