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

# Choose your setup

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

# Choose your setup

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.

> [!NOTE]
>
> **Short on time?** Install **recorder** and **player** on one server and keep everything at the defaults. That is a complete, working setup. The sections below describe the bigger options for when you outgrow it.

## The three plugins

| Plugin | Install it on | What it does |
| - | - | - |
| `Recorder` | The gameplay server | Starts recordings, captures events and terrain, and saves recordings. |
| `Player` | The server where people watch | Loads recordings, creates playback sessions, and provides playback controls. |
| `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 plugins work independently. A recorder does not need the player installed, and a player server does not need the recorder. Note that the lobby is a normal Minecraft (Bukkit) plugin — it goes in a server's `plugins` folder, not your proxy's.

## Choose a deployment

Pick the tab that matches your situation. When in doubt, start with the first one. Moving to shared storage later requires deliberate configuration and data transfer; changing a backend does not migrate saved recordings.

> [tab] 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 →](https://docs.marioded.com/owners/installation.md)

> [tab] 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 →](https://docs.marioded.com/owners/storage.md)

> [tab] 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 →](https://docs.marioded.com/owners/network.md)

## What a recording consists of

There are three related kinds of data:

1. **Replay events:** entity changes, blocks, declared world 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.

> [!NOTE]
>
> **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.

## 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](https://docs.marioded.com/owners/installation.md)
* First recording: [Quick start](https://docs.marioded.com/owners/quick-start.md)
* Integrating a minigame: [Recording API](https://docs.marioded.com/api/recording.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.