> For the complete documentation index, see [llms.txt](https://27rogi.gitbook.io/server-toolbox/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://27rogi.gitbook.io/server-toolbox/configuration/kits.md).

# Kits

<figure><img src="https://684403984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjqKdbFlXK03kz8Il1c%2Fuploads%2FfsS0ugHrFUPeF4DKa48u%2Fimage.png?alt=media&amp;token=aacabbd3-fd67-4809-a110-1481c4fde79f" alt=""><figcaption><p>Kit from example</p></figcaption></figure>

This mod includes basic kit system if needed. Configuring it is pretty simple, but I want to say that adding new kits using commands is prefered way because it automatically parses all JSON from item's lore and name. But you can also use simple formatting instead of JSON text.

Once kit is added players will need a `server-toolbox.commands.kits.kit.<name>` permission to get it, also you can use `server-toolbox.commands.kits.bypass.<name>` to bypass timeout.

```json5
kits {
    <kit_name> {
        items=[
            {
                // how much items will be given to the player
                count=1
                // starting item durability
                durability=0
                enchantments {}
                // item ID
                identifier="minecraft:diamond_sword"
                // lines of raw JSON or simple text with formatting
                lore=[]
                // same as lore, but only one line
                name="{\"italic\":false,\"extra\":[{\"color\":\"yellow\",\"extra\":[{\"text\":\"Killer of %player:name%\"}],\"text\":\"\"}],\"text\":\"\"}"
                // item will be placed in slot with specific number if it isn't empty
                slot=0
            },
            {
                count=1
                durability=0
                // lines with enchantement ID and it's level
                enchantments {
                    "minecraft:protection"=1
                }
                identifier="minecraft:netherite_leggings"
                lore=[
                    "{\"italic\":false,\"extra\":[{\"color\":\"red\",\"extra\":[{\"text\":\"This is the final warning!\"}],\"text\":\"\"}],\"text\":\"\"}"
                ]
                name="{\"italic\":false,\"extra\":[{\"color\":\"yellow\",\"extra\":[{\"text\":\"Gamechangers\"}],\"text\":\"\"}],\"text\":\"\"}"
                slot=1
            },
            {
                count=64
                durability=0
                enchantments {}
                identifier="minecraft:apple"
                lore=[]
                slot=2
            }
        ]
        // how long player needs to wait before using command again
        timeout=15
    }
}
// list with all players with timeouts and their expiration date
timeouts {
    "27rogi" {
        gameover {
            datetime="2023-07-18T13:16:36.231257763"
        }
    }
}

```


---

# 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://27rogi.gitbook.io/server-toolbox/configuration/kits.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.