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

# Your first replay

> Make a short recording, watch it back, and check that your setup works.

# Your first replay

Let's capture a small scene and watch it back. This walkthrough uses **recorder and player on the same server**, with default local storage and networking disabled. It takes only a few minutes.

## Before you begin

* [Install recorder and player](https://docs.marioded.com/owners/installation.md) and confirm they start without errors.
* Join the world you want to record.
* Give your test account `reverse.admin` and `reverse.player.use` using your permission plugin.
* Leave `storage.backend: spatial` and `storage.recordings-folder: ''` on both roles, so both use `plugins/recordings`. Keep the player's `network.enabled: false` for its local catalog.

> [!NOTE]
>
> You only need one server for this first test. A proxy, Redis, and a remote database can wait until local recording and playback work.

## Record and watch

**Step 1**

### Start recording

Run this in the world you want to capture:

```bash theme={null}
/reverserecorder start --name "First replay" --description "Installation test"
```

**What you should see:** a recording-started message showing its name, with Status and Prepare stop actions. Hover over the name for the full session UUID. Walk around, interact with a few blocks, and perform some visible actions. You can omit the session UUID when controlling your own command-started recording; clips have different replay UUIDs.

**Step 2**

### Stop and wait for the save

```text theme={null}
/reverserecorder status
/reverserecorder stop
```

**What you should see:** a save-completion message with a replay ID. Copy that ID for the next step.

Capture ends as soon as you stop, but storage finishes asynchronously. Wait for the completed-save result before trying to watch.

**Step 3**

### Open the recording

Open the standalone catalog:

```text theme={null}
/reverseplayer gui
```

Choose your recording, open its details, and select **Watch**. You can also start it directly:

```text theme={null}
/reverseplayer play <replay-id>
```

Use the save reply's **Watch** or **Prepare command** action, or open the catalog on your replay server. If entering the command manually, replace `<replay-id>` with the full UUID from the tooltip/details menu. `/reverseplayer list [page]` also provides clickable named entries. A recorder-only server offers Prepare command; run it on the replay server.

**What you should see:** the recorded scene and the playback hotbar.

**Step 4**

### Try the controls

Use the pause/resume item, seek arrows, speed control, and Stop item. Or try the commands below one at a time:

```text theme={null}
/reverseplayer pause
/reverseplayer seek 0
/reverseplayer forward 2
/reverseplayer backwards 1 5
/reverseplayer stop
```

`seek 0` returns to the beginning. `forward 2` moves forward two seconds. `backwards 1 5` moves back one second plus five ticks: **25 ticks** in total. These seek commands resume playback.

**What you should see after Stop:** your previous player state and inventory are restored.

> [!TIP]
>
> **Your first replay is working.** You have tested capture, persistence, loading, playback, and normal session cleanup.

## Check who can watch

The recorder command automatically makes you an owner. With `open-access: false`, an ordinary account should only see recordings it owns.

Test a second account before opening the feature to players. You can add another owner using `--owner` when starting a recording; ownership does not filter which players are captured.

## Try a clip during your next recording

While your command-started session is active, run:

```text theme={null}
/reverserecorder clip 10 --name "Last ten seconds"
```

Wait for the clip's save result, then keep playing and stop the source recording normally. The clip has its own replay ID and terrain copy; stopping still saves the entire source recording. No buffer or recording-mode setting is needed. See [clips](https://docs.marioded.com/owners/recorder.md#clips) for explicit intervals and failure outcomes.

## Something didn't work?

Don't panic — most first-run issues come from one of these:

| What happened? | Check first |
| - | - |
| Commands are missing | [Startup and installation](https://docs.marioded.com/owners/troubleshooting.md) |
| The catalog is empty | Owners, permissions, and matching storage settings |
| Entities appear without ground | [Terrain and snapshots](https://docs.marioded.com/owners/terrain.md) |
| Important actions are missing | [Capture scope and limitations](https://docs.marioded.com/owners/recorder.md) |

## Choose your next step

Ready to make Reverse your own?

* **Customize the viewer experience** — change the hotbar, HUD, sidebar, and messages in [Hotbar, HUD, and messages](https://docs.marioded.com/owners/display.md).
* **Grow beyond one server** — add a lobby and replay servers in [Lobby and proxy setup](https://docs.marioded.com/owners/network.md).


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