> For the complete documentation index, see [llms.txt](https://docs.olziedev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.olziedev.com/projects/playertrade/configuration/menu.md).

# Menu Configuration

## Menu Creation

In Player Trade you customize the menus that are provided by the plugin, please note that you cannot create new menus that aren't already provided by the plugin. You can change how the menu is displayed and how it works.

Please note all the menu tags show here aren't ALL the tags, but the basic & default tags for all menus. Some menus may add more tags, these are added to the config by default.

### Menu Size

When creating a menu, you need to specify the size of the menu. You need to specify multiples of 9 only as each of a chest is 9 slots. The maximum of slots you can have is 54 (9\*6) 6 being the max of rows.

Here is an example on how to use the menu size, below in the example the size of the menu contains 27 slots and will be 3 rows.

#### Configuration Example

```yaml
menu: # The menu name goes here, you cannot change this.
  size: 27 # The size of the menu, must be a multiple of 9.
```

### Menu Title

When creating a menu, you need to specify the title of the menu. You may use color codes in your title. You cannot have multiple lines in a title, this is a limitation of Minecraft.

Please note server version 1.17.10 does limit titles to be 32 characters including color codes.

Here is an example on how to use the menu title, below in the example the title of the menu will be "My lovely menu" in aqua.

#### Configuration Example

```yaml
menu: # The menu name goes here, you cannot change this.
  size: 27 # The size of the menu, must be a multiple of 9.
  title: "&bMy lovely menu" # The title of the menu.
```


---

# 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://docs.olziedev.com/projects/playertrade/configuration/menu.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.