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

# Choose your setup

Understand the three plugins and choose a deployment that fits your server.

Reverse records a world's gameplay as a timeline and sends that timeline back to viewers as a replay. It is useful for match reviews, moderation tools, and post-game viewing. It is not a screen recorder: the viewer's Minecraft client renders recorded entities, terrain, and supported effects.

## The three plugins

| Plugin             | Install it on                              | Responsibilities                                                                         |
| ------------------ | ------------------------------------------ | ---------------------------------------------------------------------------------------- |
| `reverse-recorder` | The gameplay server                        | Starts recordings, captures events and terrain, and saves recordings.                    |
| `reverse-player`   | The server where people watch              | Loads recordings, creates playback sessions, and provides playback controls.             |
| `reverse-lobby`    | An optional selection lobby behind a proxy | Shows the catalog and transfers a player to a replay server. It does not render replays. |

These are independently deployed plugins. A recorder does not need the player installed, and a player server does not need the recorder. The lobby is a Bukkit plugin, not a proxy plugin.

## Choose a deployment

{% tabs %}
{% tab title="One server" %}

### Try Reverse locally

Install recorder and player on the same server. Leave networking disabled. The defaults use a common `plugins/recordings` folder, so the player can see recordings made by the recorder. Each plugin keeps its own configuration folder.

**Best for:** a first installation or a small single-server setup.

[Continue to installation →](/get-started/installation.md)
{% endtab %}

{% tab title="Dedicated replay server" %}

### Keep gameplay and viewing separate

Install recorder on gameplay servers and player on a dedicated viewing server. Configure a shared SQL database on both. Without a lobby, players can join the replay server and choose a recording there.

**Best for:** separating replay activity from your gameplay servers.

[Plan shared storage →](/configure-and-customize/storage.md)
{% endtab %}

{% tab title="Proxy network" %}

### Add a replay selection lobby

Install recorder on gameplay servers, lobby on a selection server, and player on one or more replay servers. Share replay storage across all three roles. Enable the same availability backend on lobby and player, and use proxy server names for node IDs.

**Best for:** a network with a selection lobby and one or more replay workers.

[Follow the network setup →](/use-reverse/network.md)
{% endtab %}
{% endtabs %}

## What a recording consists of

There are three related kinds of data:

1. **Replay events:** entity changes, blocks, supported sounds and effects, and other recorded actions.
2. **Metadata:** replay UUID, owners, name, description, timestamps, and a terrain identifier.
3. **Terrain:** initial chunk snapshots stored separately from the event container.

{% hint style="info" %}
**Keep events and terrain together.** A `.rpl` file alone is not a complete terrain backup. Redis coordinates servers; it does not hold your replay archive.
{% endhint %}

## Requirements and compatibility

* Run your server with **Java 21**.
* Check the marketplace listing for the Minecraft versions and server software supported by your release.
* Install the **same Reverse release** on your recorder, player, and lobby servers.
* For the most predictable results, record and watch on the same Minecraft version. Older versions may not display blocks or effects introduced in newer ones.

Not sure which download to use? Start with the installation instructions supplied with your marketplace purchase.

## Where to go next

* First installation: [Installation](/get-started/installation.md)
* First recording: [Quick start](/get-started/quick-start.md)
* Integrating a minigame: [Recording API](/api-how-to-guides/recording.md)


---

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