# 🪖 Kits

## Commands & Permissions

* [Commands](https://nightexpress.gitbook.io/sunlight/general/commands#kits-module) link.
* [Permissions](https://nightexpress.gitbook.io/sunlight/general/permissions#kits-module) link.

## Features

* ✅ **GUI Based**. Browse, edit & obtain kits using simple and intuitive GUIs.
* ✅ **Kit Preview**. Preview kit's content with a customizable GUI.
* ✅ **Bind to Player**. Bind kit's items to a player to prevent share of kit items.
* ✅ **Cooldowns**. Set cooldown for each kit, or make them one-timed.
* ✅ **Cost**. Set money cost for each kit.
* ✅ **Custom Item Support**. Supports all kind of custom items and NBT data.
* ✅ **Commands**. Set custom commands for each kit to execute when player gets that kit.
* ✅ **Permission Requirement**. Set kit to require a permission for being able to use it.

## Configuration

### Kit Edition & Creation

By default there is **/editkit** command that opens **Kits GUI Editor**. There you can create new kits and edit existing ones.

It's very simple, just make sure to read button's descriptions.

### Custom Items

While there is full support for any kind of custom items, it's **highly recommended** to use the **Commands** feature to include items from **custom item plugins** <mark style="color:blue;">(e.g. ItemsAdder, Oraxen, etc.)</mark> in your kits.

Otherwise those items will not reflect changes made in the original their plugin's configuration and may even refuse to work properly.

### Cost

Currently, only the **Vault** compatible economy plugins are supported for the **Cost** feature.&#x20;

It's planned to integrate dynamic currency system in future updates.


---

# 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://nightexpress.gitbook.io/sunlight/modules/kits.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.