> For the complete documentation index, see [llms.txt](https://rayn-scripts.gitbook.io/rayn-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_description/place-descriptions.md).

# Place descriptions

Leave a description on any spot in the world.

## Placing

1. Run `/scene` – the panel opens on the **Place** tab.
2. Write the text and click **Place**.
3. Aim at the spot – a preview with a marker shows where it will appear.
4. Press **E** to place it, **Backspace** or **ESC** to cancel.

The spot must be within `Config.scenes.placeDistance` of the player. If you aim at the sky, the description is placed on the ground in front of you.

## Limits and expiry

* Each player can have up to `Config.scenes.perPlayer` active place descriptions.
* Each description disappears after `Config.scenes.lifetime` minutes (`0` = never).
* With `Config.scenes.saveToFile = true` descriptions survive server and resource restarts.

## Managing

The **Place** tab lists your active place descriptions with the time left. Click the bin icon to remove one.

Admins (ACE `rayn_description.admin`) can remove any description and clear all of them with `/clearscenes`.


---

# 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://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_description/place-descriptions.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.