> 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/guides/scenes.md).

# Scenes — group, export, reuse

A **scene** is a named group of sounds that belong together: the six ambiences of your haunted manor, the full soundscape of your spawn. Scenes keep big soundscapes organized — and make them **portable**.

## Why scenes?

* **Organization** — `sounds/` gets crowded fast. A scene folder keeps one place's audio together: `scenes/haunted_manor/`.
* **Bulk operations** — delete or purge a whole soundscape in one command.
* **Portability** — export a scene with *relative coordinates* and re-import it anywhere: another corner of the map, or a completely different server.

## Anatomy

```
plugins/AuraSounds/
├── scenes/
│   └── haunted_manor/
│       ├── scene.yml          # the scene's reference point (anchor)
│       ├── creaking_floor.yml # normal sound files
│       ├── whispers.yml
│       └── organ_music.yml
└── exports/
    └── haunted_manor.yml      # exported: all positions relative to the anchor
```

The `scene.yml` **anchor** is the key idea: when you export, every source point is stored *relative to the anchor*. When you import somewhere else, you give a new anchor and every sound lands in the right spot around it.

## Commands

```
/aurasounds scene create <scene>          → create a scene (anchor = where you stand)
/aurasounds scene add <scene> <sound>     → move a sound into the scene
/aurasounds scene remove <scene> <sound>  → move it back out
/aurasounds scene export <scene>          → write exports/<scene>.yml (relative coords)
/aurasounds scene import <scene>          → import at your current position (new anchor)
/aurasounds scene delete <scene>          → delete the scene (sounds return to sounds/)
/aurasounds scene purge <scene>           → delete the scene AND its sounds
```

## Workflow example: build once, sell twice

You've built a marketplace schematic with a full soundscape:

1. Build the soundscape as a scene: `scene create bazaar`, then `scene add` each sound.
2. `scene export bazaar` → `exports/bazaar.yml`.
3. Ship that file alongside your schematic.
4. The buyer pastes the schematic, stands at the same corner, runs `scene import bazaar` — the whole soundscape lands perfectly placed, in one command.

{% hint style="warning" %}
`scene purge` deletes the sound files themselves — there is no undo. Use `scene delete` if you only want to ungroup.
{% endhint %}


---

# 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/guides/scenes.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.