> ## Documentation Index
> Fetch the complete documentation index at: https://minekube.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Plugins

> Installing, managing, and understanding plugins on your Minekube AI server -- pre-installed tools, trusted sources, and Skript vs. plugins

# Plugins

Your Minekube AI server supports **Bukkit, Spigot, and Paper plugins** (.jar files) and comes with a curated set pre-installed.

***

## Pre-installed Plugins

Every server includes these out of the box:

| Plugin             | What It Does                                                          | Why It's Included                                                          |
| ------------------ | --------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| **Skript**         | Script-based custom game mechanics using a simple English-like syntax | The AI's primary tool for creating custom commands, events, and game logic |
| **skript-reflect** | Gives Skript access to the full Java/Bukkit API                       | Lets the AI write advanced scripts that can do anything a Java plugin can  |
| **PlugMan**        | Hot-reload plugins without restarting the server                      | Lets the AI install and update plugins instantly, no downtime              |

***

## Installing Plugins via AI

The easiest way to install a plugin is to ask the AI:

```
install WorldEdit
install a shop plugin
install Citizens for NPCs
find a plugin for custom enchantments
```

<Steps>
  <Step title="AI searches plugin repositories">
    The AI searches **Modrinth** and **Spiget** for the plugin you requested, finding the correct version for Paper 1.21.
  </Step>

  <Step title="AI downloads and installs">
    The plugin JAR is downloaded to the server's `plugins/` folder.
  </Step>

  <Step title="AI hot-loads the plugin">
    Using PlugMan, the AI loads the plugin without restarting the server. No downtime.
  </Step>

  <Step title="AI verifies it works">
    The AI checks that the plugin loaded correctly by looking at server logs and running a test command if applicable.
  </Step>
</Steps>

***

## Trusted Sources

The AI installs plugins exclusively from trusted, well-known repositories:

| Source       | URL                                  | Description                                            |
| ------------ | ------------------------------------ | ------------------------------------------------------ |
| **Modrinth** | [modrinth.com](https://modrinth.com) | Modern plugin and mod repository with verified uploads |
| **Spiget**   | [spiget.org](https://spiget.org)     | Spigot resource API for accessing SpigotMC plugins     |

<Warning>
  The AI will only install plugins from these trusted sources. It will not download JARs from unknown URLs, direct links, or unverified websites. This protects your server from malicious code.
</Warning>

***

## Managing Plugins

Ask the AI to manage your installed plugins:

```
what plugins are installed?
reload the Skript plugin
unload WorldEdit
disable the shop plugin
update all plugins
show me the WorldEdit config
```

***

## Skript vs. Plugin: When to Use Which

For many custom features, the AI uses **Skript** instead of installing a separate plugin. Here is how the AI decides:

| Scenario                        | AI's Approach                  | Why                                                        |
| ------------------------------- | ------------------------------ | ---------------------------------------------------------- |
| "make a /heal command"          | **Skript**                     | Simple, custom, fast to create                             |
| "install WorldEdit"             | **Plugin**                     | Complex established tool, no need to reinvent              |
| "NPC villagers that trade"      | **Plugin** (Citizens) + Skript | Core NPC system needs a plugin, custom behavior via Skript |
| "teleport to a random location" | **Skript**                     | Custom logic, lightweight                                  |
| "create a scoreboard"           | **Skript**                     | Standard Skript capability, no plugin needed               |
| "add Vault economy support"     | **Plugin**                     | Established ecosystem, other plugins depend on it          |

<Tabs>
  <Tab title="Advantages of Skript">
    * **Instant to create** -- the AI writes and enables it in seconds
    * **Easy to modify** -- just ask the AI to change it
    * **No extra JARs** -- lightweight, no dependency management
    * **Readable** -- English-like syntax you can inspect
  </Tab>

  <Tab title="Advantages of Plugins">
    * **Performance** -- compiled Java runs faster for intensive tasks
    * **Ecosystem** -- established plugins have years of testing and features
    * **Complexity** -- some things (custom packets, databases, GUIs) are easier in Java
    * **Community support** -- popular plugins have documentation and communities
  </Tab>
</Tabs>

<Tip>
  You do not need to decide between Skript and plugins yourself. Just tell the AI what you want, and it will pick the best approach. If you have a preference, mention it: "use Skript for this" or "install a plugin for this."
</Tip>