> 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/character-descriptions.md).

# Character descriptions

Describe what other players can see.

## Setting a description

* `/desc` opens the panel on the **Character** tab. Write the text and click **Save** (or press Enter).
* `/desc [text]` sets the description instantly, without opening the panel.
* Click **Remove** to clear your description.

The description is shown on the character's chest in a dark box with a coloured label. It is visible to every player within `Config.player.range`, also to players who join later.

## How it behaves

* Hidden behind walls when `Config.player.lineOfSight = true`.
* Gets smaller with distance, long texts wrap into several lines.
* With `Config.player.remember = true` the description is restored automatically after reconnecting (saved on the player's PC).
* Players can turn off **Show descriptions of others** in the panel. The choice is saved per player.

{% hint style="info" %}
The text is attached to a ped bone (`Config.player.bone`, chest by default), so it does not overlap with /me /do texts above the head.
{% 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 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/character-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.