> For the complete documentation index, see [llms.txt](https://wiki.auraplugins.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.auraplugins.eu/reference/configuration.md).

# Configuration

## `config.yml`

```yaml
# Prefix for in-game messages (legacy '&' codes or MiniMessage).
prefix: '&8[&bAuraSounds&8]'

# Interval (in ticks) of the task that checks player positions
# and re-evaluates conditions. 20 ticks = 1 second.
condition-check-interval: 20

# Defaults applied when a sound file omits these values.
defaults:
  volume: 1.0
  pitch: 1.0
  category: AMBIENT

# Verbose console output (sound resolution, per-player activations).
debug: false
```

### Tuning `condition-check-interval`

This is the plugin's heartbeat: how often each player's position and every relevant condition are re-checked.

* **20** (1 s) — the default; reactive and cheap for the vast majority of servers.
* **40** (2 s) — consider it above several hundred concurrent players. Sounds react slightly slower to movement; nobody will notice for ambience.
* Going below 20 buys almost nothing perceptually — not recommended.

The check runs on the main thread by design (world state like biomes, weather and regions is not thread-safe to read), and its cost per cycle is negligible: sounds are indexed **per world** and WorldGuard lookups are **cached per player per block**.

## `messages.yml`

Every player-facing message lives here, in **MiniMessage** format — colors, gradients, hover/click events all work:

```yaml
sound-created: '<green>Sound <white><name></white> created!</green>'
```

Edit freely and apply with `/aurasounds reload`. Perfect for translating the plugin to your community's language.

## The data folders

| Folder            | Contents                                                             |
| ----------------- | -------------------------------------------------------------------- |
| `sounds/`         | One YAML file per sound ([format reference](/guides/sound-files.md)) |
| `scenes/<scene>/` | Sounds grouped into a scene + its `scene.yml` anchor                 |
| `exports/`        | Scenes exported with relative coordinates                            |

Everything is plain YAML on disk: version it with git, sync it between servers, edit it in your IDE — then `/aurasounds reload`.


---

# 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 dynamically by asking a question.

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

```
GET https://wiki.auraplugins.eu/reference/configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.