> 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/features.md).

# Features

If you are not sure you should choose Solar here you can see all the features of the plugin.

### **📚 Feature list**

* **📐 Grid based arenas** — Our plugin is a bit different from other duels/practice plugins as we use a dynamic grid system instead of a pregenerated arena which allows arenas to be scaled on demand when it is needed. 
* **⚔️ Kit system** — The plugin allows you to create kits that can be used in duels and matches. Unlike other practice plugins we provide a **Flag system** which allows the players to have a temporary state *(like increased health in the match, no hunger loss...)* that will be restored once the duel ends.
* **🪓 Duel system** — The plugin provides the basic duel features that most practice plugin have.
* **🎉 Party system** — The plugin offers a party system that allows players to create **1v1, 2v2, 2v1 etc..** 
* **👀 Spectate system** — Solar provides with a builtin `/spectate <player>` command which allows anyone to spectate any match they wish!
* **🚧 Extensive queue system** — Solar allows you to create queues which can have its own team size, its own properties like ranked queues.
* **🌈 Minimessage support** — Every message that is sent to the players is serialized with MiniMessage which allows you to have clickable text, hoverable text, gradients and many more features. For full featurelist checkout <https://docs.papermc.io/adventure/minimessage/format/>.
* **📍 PlaceholderAPI support** — In most of the messages in the `language.yml` you can use placeholders. See Language configuration section for more information!
* **⚙️ Extensive configuration** — Most of the features of Solar can be configured in the major configuration files (`language.yml`, `config.yml`)
* **📊 Database integration** — Solar supports **SQLITE** *(later MYSQL)* databases to store statistics about players safely.
* **🏩 Lobby system** — After matches players are teleported a lobby that can be set with `/solar setlobby`.

## What's next?

Now that you know what are the main features of Solar. You can check out dependencies and how to install the plugin!

{% content-ref url="/pages/56a52747d54863f8df67ff3ce908938888c69b66" %}
[Custom domains](/guides/custom-domains.md)
{% endcontent-ref %}

{% content-ref url="/pages/fb922e107b31a3e9e9fcf81410029e993b0a9afc" %}
[Permissions](/core-concepts/permissions.md)
{% endcontent-ref %}

{% content-ref url="/pages/d9d593aeabc52a165190bf8c93720491a4eb9682" %}
[Automations](/guides/automations.md)
{% endcontent-ref %}


---

# 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/features.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.