> ## 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. # Common questions > Quick answers before you install, configure, or build with Reverse. # Common questions Looking for a quick answer? Start here. If something is already failing, use the [troubleshooting guide](https://docs.marioded.com/owners/troubleshooting.md) instead. Click a question to expand its answer. ## Getting started 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 →](https://docs.marioded.com/owners/overview.md) 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 →](https://docs.marioded.com/owners/network.md) 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. 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](https://docs.marioded.com/api/recording.md). Store the returned session ID with your match. ## Recordings and access 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 →](https://docs.marioded.com/owners/commands.md) 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. For API participants, `null` means all in-scope players and an empty set means none. Nonplayer entities remain spatially selected. The recorder command does not expose participant or bounds flags. [Read the recording guide →](https://docs.marioded.com/owners/recorder.md) 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. The body is encrypted with the key supplied during activation, so the destination server must also be able to activate before it can replay the file. [Back up the complete archive →](https://docs.marioded.com/owners/storage.md) 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. Yes. During a command-started recording, use `/reverserecorder clip 10` for the recent ten seconds or `/reverserecorder clip --from 30 --to 45` for an explicit session-relative interval. The source keeps recording, and its eventual stop saves the full history. There is no separate buffer mode or history-window setting. The clip gets a new replay UUID, reconstructs its starting state, and copies available terrain under its own identifier. Wait for its save result: terrain-copy failure is reported as degraded, while an event-save failure fails the export. [Clip commands and behavior →](https://docs.marioded.com/owners/recorder.md#clips) Normally no. Open the catalog or use Watch/Prepare command in `/reverseplayer list [page]` and save replies. Full UUIDs are available in details and hover text for manual commands or integrations. Names are readable labels, not unique lookup keys. No short-ID or prefix lookup exists. Live recorder session arguments take full UUIDs, but stop/status/clip can select your command-started session when the argument is omitted. Start/status messages provide session actions with the correct UUID. A clip identifies the exported replay, not the source recording. Playback sessions are separate identities too. Watch is shown on the recorder only when a local playback/lobby command is available; otherwise prepare the command for the replay server. Yes: set `storage.recordings-folder` and restart. Blank selects `plugins/recordings`; relative paths resolve against the role data folder's parent, and absolute paths are used verbatim. This also sets the base for a relative SQLite filename. Changing the setting does not migrate existing files. Match the resolved folder on roles sharing a local dataset. [Folder examples and backups →](https://docs.marioded.com/owners/storage.md) ## Playback and customization 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 →](https://docs.marioded.com/api/playback.md) Yes. Player and lobby catalog menus live in their own `gui.yml`. Each role reads messages from `messages.yml`. Player hotbar/HUD settings live in `layout.yml`; its sidebar lives in `messages.yml`. Use MiniMessage tags for configured colors and formatting. [Customize menus →](https://docs.marioded.com/owners/menus.md) · [Customize the viewer display →](https://docs.marioded.com/owners/display.md) 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 →](https://docs.marioded.com/owners/configuration.md) ## Need a different answer? If nothing here matches your situation, the [troubleshooting guide](https://docs.marioded.com/owners/troubleshooting.md) walks through symptoms one at a time. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.