> For the complete documentation index, see [llms.txt](https://matt-creppet.gitbook.io/matt-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://matt-creppet.gitbook.io/matt-docs/installation.md).

# Requirements and installation

## Requirements

* A Minecraft Java server running Spigot, Paper or Purpur.
* Minecraft 1.20 through 26.3 is the intended compatibility range. The automated test matrix checks selected API versions; it does not certify every server build in that range.
* The Java version required by your server. Regen Zone uses Java 17 bytecode, but this does not let a newer Minecraft server run on an older Java runtime. For example, Paper 26.1 and later requires Java 25 according to [Paper's installation documentation](https://docs.papermc.io/paper/getting-started/).
* Write access to the server's `plugins` directory and the plugin data folder.
* An operator account, or the relevant Regen Zone permissions, to administer arenas.

Folia's region-threaded execution model is not supported. Forge and Fabric are not supported plugin platforms. No claim is made for hybrid mod/plugin servers.

## Install

1. Stop the server normally.
2. Place `RegenZone-0.3.0.jar` in the server's `plugins` directory.
3. Make sure only one Regen Zone JAR is present.
4. Start the server.
5. Look for the Regen Zone text banner and completion message in the console. Loading saved arenas happens in a disk worker; wait for the ready message before administering them.
6. In game, run `/rz ayuda`. From the server console, omit the leading slash when your panel requires that format.

The first start creates `plugins/RegenZone/config.yml`. Arena files are created when captures are saved successfully.

## Optional permission manager

Regen Zone uses the server's standard Bukkit permission system. You may grant its nodes through any permission manager that supports Bukkit permissions. The plugin does not require or directly integrate with a particular permission manager.

Use `regenzone.admin` for a trusted administrator. For limited roles, grant only the nodes listed in [Commands and permissions](/matt-docs/commands-permissions.md). Every declared node defaults to operators. Granting `regenzone.menu` alone allows opening the menu but does not grant editing rights.

## First test

Use a small test arena before configuring a large production arena. Capture the original state, break a normal block, place another block in an originally empty position, and verify that both return to the saved state. Check the chosen waiting rules and material filters if either change is skipped.

## Updating

Stop the server, back up the data folder, replace the old JAR and start again. Preserve the data folder. Existing arenas do not require reselection. Existing configurations without newer keys use the documented fallback values; the plugin does not rewrite your global configuration to add every new comment automatically.

Use a full stop/start for plugin upgrades. `/rz reload` only reloads global configuration and messages; it is not a plugin hot-reloader.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://matt-creppet.gitbook.io/matt-docs/installation.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 `automate deployments from our CI pipeline` 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.