> For the complete documentation index, see [llms.txt](https://grp-development.gitbook.io/solid-scripts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://grp-development.gitbook.io/solid-scripts/resources/solid-chat/in-game-setup/overhead-text.md).

# Overhead text

/me and /do shown above the player's head.

`/me` describes an action and `/do` describes the scene. The text shows in a bubble above the player's head for everyone nearby, and as a line in their Local tab.

#### Settings

Found in `/chatsetup` > Overhead text.

| Setting                     | Default | Description                                                            |
| --------------------------- | ------- | ---------------------------------------------------------------------- |
| Enabled                     | On      | Shows /me and /do above the player's head.                             |
| Action command              | `me`    | Rename it if another resource already owns /me.                        |
| Scene command               | `do`    | Rename it if another resource already owns /do.                        |
| Distance (metres)           | `15`    | Players inside this many metres see the text, from 1 to 100.           |
| Base duration (ms)          | `2500`  | Starting display time of a line.                                       |
| Duration per character (ms) | `65`    | Extra time for each character.                                         |
| Minimum duration (ms)       | `3000`  | Shortest time a line stays up.                                         |
| Maximum duration (ms)       | `12000` | Longest time a line stays up.                                          |
| Maximum stacked lines       | `3`     | Lines that can stack above one player, from 1 to 10.                   |
| Maximum characters          | `160`   | Longest overhead message.                                              |
| Cooldown (seconds)          | `1`     | Wait between two roleplay messages.                                    |
| Show your own overhead text | On      | Players also see their own text above their head.                      |
| Require line of sight       | On      | Hides the text behind walls.                                           |
| Height above head (metres)  | `0.4`   | Extra height above the head, from 0 to 2.                              |
| Bubble size                 | `1.0`   | Size of the bubbles, from 0.5 to 2. `0.8` is smaller, `1.3` is bigger. |

#### How long a line stays

A line stays for the base duration plus the time per character, kept between the minimum and the maximum. With the defaults, a 40 character line stays 2500 + 40 × 65 = 5100 ms, about five seconds.

When a new line goes over Maximum stacked lines, the oldest one goes away.

#### Who sees it

Only players within Distance and in the same routing bucket see the text. Players who walk into range see the lines that are still up, and players who walk away stop seeing them. With Require line of sight on, the text also hides behind walls.

{% hint style="warning" %}
Overhead text needs OneSync, because the server reads player positions to work out who is nearby. Without it, /me and /do tell the player it is unavailable. The rest of the chat works without OneSync.
{% endhint %}

#### Command conflicts

qb-core, esx\_rpchat and other resources often have their own /me and /do. When another resource registers the same command, the server console warns you on start. Rename SOLID Chat's commands here, or switch them off.

Your own resources can show overhead text too, with the [showOverhead export](https://grp-development.gitbook.io/solid-scripts/resources/solid-chat/exports-and-events/server-exports#showoverhead).


---

# 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://grp-development.gitbook.io/solid-scripts/resources/solid-chat/in-game-setup/overhead-text.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.