> 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/templates-and-backups.md).

# Templates and backups

How messages look, and keeping your settings safe.

#### Templates

Found in `/chatsetup` > Templates.

Templates decide how plain messages look in the chat. Every template shows a live preview, and Edit HTML opens its code.

| Template                 | Used for                               | Placeholders                           |
| ------------------------ | -------------------------------------- | -------------------------------------- |
| Default template         | Messages with a sender                 | `{0}` is the sender, `{1}` is the text |
| Single argument template | Messages without a sender              | `{0}` is the text                      |
| Console template         | Server console lines shown in the chat | `{0}` is the text                      |

{% code title="Default template" %}

```html
<div class="chat-message"><span class="cm-author">{0}</span><span class="cm-text">{1}</span></div>
```

{% endcode %}

| Class          | Styles                                                                               |
| -------------- | ------------------------------------------------------------------------------------ |
| `chat-message` | The message. Add a style after it, like `chat-message police`, for a channel colour. |
| `cm-author`    | The sender's name.                                                                   |
| `cm-text`      | The message text.                                                                    |
| `cm-tag`       | A tag like the ones channels use.                                                    |
| `cm-id`        | A server ID badge.                                                                   |

{% hint style="info" %}
Keep a template on one line. Messages that keep their line breaks also keep line breaks and spaces inside the template.
{% endhint %}

#### Backups

Found in `/chatsetup` > Backups.

The Backups page keeps up to 12 backups, each with its date and the admin who made it. When a new one would go over 12, the oldest one is removed.

* **Before saving:** every save keeps the settings from before it, automatically.
* **Create backup:** saves the current settings by hand.
* **Load:** puts a backup into the form. Press Save changes to apply it.
* **Delete:** removes a backup after a second click to confirm.

**Export and import**

Export copies your current settings as text. Paste it into a text file to keep it, or use it to move your setup to another server. Import takes that text back into the form, and Save changes applies it.

{% hint style="info" %}
Restore defaults loads the starting values into the form. Your backups stay, so you can load your own settings back at any time.
{% 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://grp-development.gitbook.io/solid-scripts/resources/solid-chat/in-game-setup/templates-and-backups.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.