# Text parsing

### Introduction

In staff++ there are messages file which contain most of the text used within staff++.

### New lines

New lines can be achieved using 2 ways

#### \n notation

```
ban-permabanned-kick: "[Banned] You have been permanently banned\nfrom this server"
```

#### YAML multiline notation

```
ban-permabanned-kick: |
    [Banned] You have been permanently banned 
    from this server
```

### Tooltips

Tooltips are supported in the newest version of staff++.\
These can be configured by using the notation:

#### \[tooltip|\<hoverable text>|\<tooltip text>]

#### Example

\[tooltip|&6%player%''s|&6%player%\n&7This guy] armor has been removed!

![](/files/5xe8Va14ZMXmTutz6fOj)

### Basic colors

Basic colors are supported using **"&"**

![](/files/RBh7Ka9wrrxZAsV7eRLK)

### Hex Colors

In versions >= 1.16 hex colors are supported using hex notation

```markup
#FF0044This is in some color. #EE8833This is another color.
```

### Gradients

In versions >= 1.16 gradient colors are supported using:

```markup
<#00d8e6>This is gradient</#8ae0e6>
```


---

# Agent Instructions: 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:

```
GET https://wiki.staffplusplus.org/general-information/other/text-parsing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.