> 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/keep-things-running/faq.md).
# Common questions
Quick answers before you install, configure, or build with Reverse.
Looking for a quick answer? Start here. If something is already failing, use the [troubleshooting guide](/keep-things-running/troubleshooting.md) instead.
## Getting started
Do I need all three plugins?
No. **Recorder** captures gameplay; **player** lets people watch it. Put both on one server for your first test. Add **lobby** when you want a selection server that sends viewers to separate replay servers through a proxy.
[Choose your setup →](/get-started/overview.md)
Do I need a database, Redis, or a proxy?
Not for a local setup. The defaults use local storage with networking disabled.
For several machines, use shared SQL replay storage. A proxy handles server transfers. Redis is an optional availability backend; it is not where replay events or terrain are stored.
[Connect a network →](/use-reverse/network.md)
What Java and Minecraft version do I need?
Use **Java 21**. The marketplace listing for your release gives the supported Minecraft versions and server software. Keep the same Reverse release across your servers, and test a short recording after installation or an update.
Does Reverse start recording every match automatically?
Recording starts through the recorder command or an API call. Reverse does not know the lifecycle of every minigame automatically.
For automatic match recording, connect your game's start/end events to the [recording API](/api-how-to-guides/recording.md). Store the returned session ID with your match.
## Recordings and access
Can everyone watch my recordings?
With `open-access: false`, the catalog uses replay owners and administrator permissions. The recorder command adds its initiator as an owner. API integrations choose the owner list explicitly.
Be careful with `open-access: true`: it treats everyone as a catalog administrator, including management operations offered by your UI. It is more than a public Watch switch.
[Understand commands and access →](/use-reverse/commands.md)
Does adding an owner choose which players are recorded?
No. **Owners control access to the finished replay.** API participant selection controls which players are captured. Arena bounds control spatial capture. They solve different problems.
[Read the recording guide →](/use-reverse/recorder.md)
Can I move a replay by copying its .rpl file?
The file contains metadata and events, but the base terrain is separate. Move or back up the complete local storage dataset, or use shared SQL storage. Template recordings also require the referenced template on the viewing side.
[Back up the complete archive →](/configure-and-customize/storage.md)
Is this a video file I can export?
Reverse replays recorded data inside Minecraft. It does not currently provide a video-export command. The viewing client renders the supported recorded scene and actions.
## Playback and customization
Can viewers control the same recording independently?
Yes, when your integration starts separate playback sessions. A session shared by several viewers has one timeline, pause state, and speed, so its controls affect everyone in that session.
[Understand playback sessions →](/api-how-to-guides/playback.md)
Can I change the menus, controls, and messages?
Yes. Catalog menus live under `gui` in the role's main configuration. Player hotbar/HUD settings live in `layout.yml`; its sidebar lives in `messages.yml`. Use MiniMessage tags for configured colors and formatting.
[Customize menus →](/configure-and-customize/menus.md) · [Customize the viewer display →](/configure-and-customize/display.md)
Do all configuration changes apply with reload?
No. Messages, supported display/menu settings, open-access policy, and recorder radius can be updated by the role's reload handler. Storage, database connections, networking, and playback-world choices need a full restart.
[Check the reload/restart table →](/configure-and-customize/configuration.md)
## Need a different answer?
{% content-ref url="/pages/1ClQXDROKUIqEESqA9ox" %}
[Troubleshooting](/keep-things-running/troubleshooting.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/keep-things-running/faq.md?ask=&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.