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

# Your first replay

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

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.

## Before you begin

* [Install recorder and player](/get-started/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.

{% hint style="info" %}
You only need one server for this first test. A proxy, Redis, and a remote database can wait until local recording and playback work.
{% endhint %}

## Record and watch

{% stepper %}
{% step %}

### Start recording

Run this in the world you want to capture:

{% code title="In-game command" %}

```
/reverserecorder start --name "First replay" --description "Installation test"
```

{% endcode %}

**What you should see:** a recording-started message with a session ID. Walk around, interact with a few blocks, and perform some visible actions.
{% endstep %}

{% step %}

### Stop and wait for the save

```
/reverserecorder status
/reverserecorder stop
```

**What you should see:** a save-completion message with a replay UUID. Copy that UUID 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.
{% endstep %}

{% step %}

### Open the recording

Open the standalone catalog:

```
/reverseplayer
```

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

```
/reverseplayer play <replay-id>
```

Replace `<replay-id>` with the UUID from the save message. Use `/reverseplayer list` if you need to find the ID again.

**What you should see:** the recorded scene and the playback hotbar.
{% endstep %}

{% step %}

### Try the controls

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

```
/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.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Your first replay is working.** You have tested capture, persistence, loading, playback, and normal session cleanup.
{% endhint %}

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

## Something didn't work?

| What happened?                 | Check first                                                         |
| ------------------------------ | ------------------------------------------------------------------- |
| Commands are missing           | [Startup and installation](/keep-things-running/troubleshooting.md) |
| The catalog is empty           | Owners, permissions, and matching storage settings                  |
| Entities appear without ground | [Terrain and snapshots](/configure-and-customize/terrain.md)        |
| Important actions are missing  | [Capture scope and limitations](/use-reverse/recorder.md)           |

## Choose your next step

{% content-ref url="/pages/EKseS6aOS6kFuyAf4SA5" %}
[Hotbar, HUD, and messages](/configure-and-customize/display.md)
{% endcontent-ref %}

{% content-ref url="/pages/sw2rn3Xw68PPxoBh1DT1" %}
[Lobby and proxy setup](/use-reverse/network.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/quick-start.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.