Skip to main content

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

1

​
Start recording

Run this in the world you want to capture:
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.
2

​
Stop and wait for the save

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

​
Open the recording

Open the standalone catalog:
Choose your recording, open its details, and select Watch. You can also start it directly:
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.
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:
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.
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:
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 for explicit intervals and failure outcomes.

​
Something didn’t work?

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

​
Choose your next step

Ready to make Reverse your own?