> For the complete documentation index, see [llms.txt](https://docs.dragonpvp.hu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dragonpvp.hu/solar/creating-a-kit.md).

# Creating a kit

This is the process of creating a kit for duels and matches.

{% stepper %}
{% step %}

### Create the kit.

Use `/kit create <name>` to create a blank kit! It will be **NOT saved to the disk as this is memory only**!

<figure><img src="https://1962647993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYqPqLKmpRmjcGMNoNoVZ%2Fuploads%2FysxZNV2zqH9S4feakhKW%2FAnimation2.gif?alt=media&amp;token=bfada725-bc48-451b-9a95-acbdd9fa7f52" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Set the inventory for the kit.

You can set the items with `/kit set-items <name>`. This is the part where you add the items to the kit. Like the action before **this also DOES NOT save anything to the disk**!

<figure><img src="https://1962647993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYqPqLKmpRmjcGMNoNoVZ%2Fuploads%2F2SvqMVl73gimpYDF09h4%2FAnimation3.gif?alt=media&amp;token=f655802a-2ef0-48b8-bbc0-b4fc5d0bbfd9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### (Optional) Set the potion effects for the kit

These are the potion effects that will be applied to the players when the match starts. You can set it with `/kit set-effects <name>` .&#x20;

<figure><img src="https://1962647993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYqPqLKmpRmjcGMNoNoVZ%2Fuploads%2F2mlzt0gmxQGBQdYKOSsa%2FAnimation4.gif?alt=media&amp;token=826a5a18-feb4-4541-a3a4-a97006771ea0" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### (Optional) Set kit flags for the kit

You can set the kit flags now. Kit flags change the default vanilla/Minecraft values (like max health) and sets it to a different one that you choose for a duel/match. Setting the flags for a kit can e done `/kit setFlags <name>` and by chaining together flags with a space as a seperator.

Here is all the options you can set:

<table><thead><tr><th width="276">Flag</th><th>Default value</th><th width="262">Description</th></tr></thead><tbody><tr><td>--golden-apple-cooldown</td><td>-1 (No cooldown, Vanilla)</td><td>Sets the cooldown for the golden apple after eating one.</td></tr><tr><td>--hunger-loss</td><td>true (Vanilla)</td><td>Turns on or off the ability of losing hunger.</td></tr><tr><td>--max-health</td><td>-1/20 (Vanilla)</td><td>Sets the maximum amount of health a player can have.</td></tr><tr><td>--natural-regeneration</td><td>true (Vanilla)</td><td>Turns on or off the ability to have natural regeneration.</td></tr><tr><td>--natural-saturation</td><td>true (Vanilla)</td><td>Turns on or off the ability to have natural saturation regeneration.</td></tr><tr><td>--pearl-cooldown</td><td>-1 (Default Vanilla cooldown)</td><td>Sets the cooldown for pearls.</td></tr><tr><td>--prevent-block-break</td><td>false</td><td>Should Solar prevent players from breaking blocks while in a match.</td></tr><tr><td>--prevent-block-place</td><td>true</td><td>Should Solar prevent players from placing blocks while in a match.</td></tr><tr><td>--prevent-item-drop</td><td>false</td><td>Should Solar prevent players from dropping items while in a match.</td></tr><tr><td>--prevent-movement-before-start</td><td>false</td><td>Should Solar prevent players from moving while the match is starting.</td></tr><tr><td>--windcharge-cooldown</td><td>-1 (No modification)</td><td>Sets the cooldown for windcharges.</td></tr></tbody></table>

<figure><img src="https://1962647993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYqPqLKmpRmjcGMNoNoVZ%2Fuploads%2F9J9klp3pQEk2wOHqVzbg%2FAnimation5.gif?alt=media&amp;token=f05da62f-b70c-4e12-93fd-149aeb54b7db" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Finalizing the kit.

In Solar finalizing means saving the kit to the disk it is straightforward as typing `/kit finalize <name>` . **This will save to the disk but any modifications that are going to be made after that needs to be finalized too.**

<figure><img src="https://1962647993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYqPqLKmpRmjcGMNoNoVZ%2Fuploads%2FxuLGImJtaZO9wL1RrVri%2FAnimation6.gif?alt=media&amp;token=ab065dbb-2910-4323-b85c-7b971b038358" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

And you finished your first kit! Now you can setup arenas.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dragonpvp.hu/solar/creating-a-kit.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 `build a script that syncs our docs to a CMS` 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.
