> 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/setting-up-the-plugin.md).

# Setting up the plugin

Now it is time for setting up the plugin!

{% stepper %}
{% step %}

### Download the plugin.

You have 2 options toget the plugin:

1. **Buy it for €20 from BuiltByBit.**
2. **Get a 3 day trial from me, but you'll need the following for that:**
   1. Server IP
   2. Some basic information about the server and why do you need the plugin.

{% hint style="danger" %}
**DISCLAMER**: We recommend to buy the plugin or use the official period and **NOT** pirating the plugin! **You're putting yourself at risk from downloading a modified version of the plugin that may potentially contain malware or other malicous code!** **You aren't going to get any support if you are using an unofficial version on your server!**

We recommend you to buy the plugin **as you'll receive the proper support by the developer of the plugin and support me as a solo developer!**
{% endhint %}
{% endstep %}

{% step %}

### Download FAWE (FastAsyncWorldEdit)

The next step is to download the dependency for Solar.

{% embed url="<https://modrinth.com/plugin/fastasyncworldedit>" %}
{% endstep %}

{% step %}

### Install the plugin and FAWE on the server

Here is a little GIF about how should the installation look but it might be different depending where you install it!

<figure><img src="https://1962647993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYqPqLKmpRmjcGMNoNoVZ%2Fuploads%2FqEVjk7hJSNnvLaRovEex%2FAnimation.gif?alt=media&amp;token=0371a4b1-7d2a-426c-8661-dff0546bfbde" alt="Installation process"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Start the server!

It depends where you install it but you should see this as that means that the plugin has been installed on the server!

```log
[Solar] Enabling Solar v1.0.0
[12:51:11 INFO]: [Solar] Hooks:  FAWE
[12:51:11 INFO]: [com.j256.ormlite.table.TableUtils] creating table 'player_stats'
[12:51:11 INFO]: [com.j256.ormlite.table.TableUtils] executed create table statement changed 0 rows: CREATE TABLE IF NOT EXISTS `player_stats` (`id` INTEGER PRIMARY KEY AUTOINCREMENT , `uuid` VARCHAR NOT NULL , `kit` VARCHAR NOT NULL , `wins` INTEGER DEFAULT 0 , `losses` INTEGER DEFAULT 0 )
[12:51:11 INFO]: Loading 0 persistent chunks for level 'minecraft:arenas'...
[12:51:11 INFO]: Preparing spawn area: 100%
[12:51:11 INFO]: Prepared spawn area in 1 ms
[12:51:11 INFO]: [Solar] Loaded in 0 arena(s)!
[12:51:11 INFO]: [Solar] Loaded in 0 kit(s)!
```

{% endstep %}

{% step %}

### And you are ready to go!

If everything shows as the above congrats you just installed solar on your server!

Next you could setup a kit for the plugin!
{% endstep %}
{% endstepper %}


---

# 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/setting-up-the-plugin.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.