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

# Installation

Download Reverse, install the plugins your setup needs, and make your first replay.

Download Reverse from the marketplace where you purchased it. For your first test, install **recorder and player on one server**.

## Before you begin

* Run your server with **Java 21**.
* Check that your Minecraft version and server software are supported by the release you downloaded.
* Have access to the server's `plugins` folder and console.
* Allow the server to reach the internet for activation and automatic dependency downloads.

## Install in three steps

{% stepper %}
{% step %}

### Choose your plugins

| I want to…                            | Install                                                     |
| ------------------------------------- | ----------------------------------------------------------- |
| Record and watch on one server        | Recorder + player                                           |
| Record gameplay                       | Recorder on the gameplay server                             |
| Run a dedicated viewing server        | Player on the replay server                                 |
| Let players select replays in a lobby | Lobby on the selection server, player on the replay servers |

Install the lobby on a Minecraft server behind your proxy, not in the proxy's plugins folder.
{% endstep %}

{% step %}

### Install your download

1. Stop the server.
2. Open the download and follow any included instructions. If it is an archive, extract it first.
3. Copy the `.jar` for each role you need into the server's `plugins/` folder.
4. If you are updating, replace the previous jar for that role rather than keeping both versions installed.

Keep the filenames supplied with your download. You do not need to compile anything or download the API to run Reverse.
{% endstep %}

{% step %}

### Start once, configure, and restart

Start the server and let Reverse create its configuration files. Check the console for startup errors, stop the server, make your configuration changes, and restart.

For a local first test, keep the default storage and leave networking disabled. Follow [Your first replay](/get-started/quick-start.md) before setting up a multi-server network.
{% endstep %}
{% endstepper %}

## Dependencies

Reverse downloads the libraries it needs automatically. Your server needs an internet connection and permission to write to its plugin folders.

If you use SlimeWorldManager or ASP templates, install and configure that world manager separately. Follow the [terrain guide](/configure-and-customize/terrain.md) for that optional setup.

If a download fails, check internet access and the first related console error, then restart after fixing the cause.

## Where are the settings?

| Plugin   | Configuration files                                                              |
| -------- | -------------------------------------------------------------------------------- |
| Player   | `plugins/reverse-player/config.yml`, `messages.yml`, `layout.yml`                |
| Recorder | `plugins/reverse-recorder/config.yml`, `messages.yml`                            |
| Lobby    | `plugins/reverse-lobby/config.yml`; messages and menus are sections in this file |

Local recordings are stored in `plugins/recordings`. Keep that folder when moving or backing up the server.

{% hint style="info" %}
**Start with the generated files.** Examples in this wiki show settings to merge into your configuration, not a reason to delete the rest of it.
{% endhint %}

## Activation

Follow the activation instructions provided with your purchase. If activation fails, check that the server can reach the internet and contact support with the console error and your release version. Keep license details private when sharing logs.

## Check that it works

* [ ] The plugins start without errors.
* [ ] Your test account has the [permissions](/use-reverse/commands.md) it needs.
* [ ] You can save a short recording and watch it back.
* [ ] A second account sees only the recordings it is allowed to access.

{% content-ref url="/pages/xw85fNuk32xRg8bLZUU4" %}
[Your first replay](/get-started/quick-start.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 by asking a question.

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

```
GET https://docs.marioded.com/get-started/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.