> 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/troubleshooting.md). # Troubleshooting Start with what you see, narrow down the cause, and get your replays working again. Choose the symptom that matches your setup. Start with the **first related error in the console**: later “command not found” messages often just mean the plugin did not finish starting. {% hint style="info" %} **Keep these details handy:** Reverse build, Java/server version, installed roles, storage backend, and replay/session ID. They make a problem much easier to reproduce. Redact credentials and license-bearing data before sharing logs. {% endhint %} ## What is happening?
The plugin does not start, or commands are missing 1. Read the first related error in the console, not just the later “command not found.” 2. Confirm Java 21 and a Minecraft/server version supported by your download. 3. Download the correct role from your marketplace purchase and remove any old duplicate jar. 4. Check internet access and permission to write to the plugin folders. 5. Follow the activation instructions included with your purchase. 6. If using SWM/ASP, confirm its installed version and dependencies are compatible. If the console reports `NoClassDefFoundError` or a missing dependency, check the earlier download/startup errors. Re-download the plugin from your purchase if necessary, and send support the full error if it continues. [Review installation →](/get-started/installation.md)
My recording is missing from the catalog * Wait for save completion, not just capture stop. * Check the replay ID in the save log. * Verify owner UUIDs and catalog admin permissions. * Check `open-access` on the server being queried. * Confirm recorder/lobby/player use the same dataset. * Look for SQL startup fallback to private local files. * Reopen the menu after metadata changes or a newly completed save. Missing and forbidden replays deliberately look alike through the catalog. This prevents the catalog from revealing unauthorized replay existence.
I can see entities, but the ground is missing * Check for a degraded-terrain result at save time. * Verify terrain indices and packs/database data were transferred along with events. * For templates, verify the exact identifier and SWM loader on the player server. * Confirm relevant chunks were loaded and captured when recording started. * Try `/reverseplayer resend` to distinguish a delivery issue from missing stored terrain. Copying only `.rpl` files or an unrelated normal world folder does not restore captured terrain. [Understand terrain storage →](/configure-and-customize/terrain.md)
The lobby says no replay server is available * Availability must be enabled on both lobby and player. * Check matching backend selection and endpoint/database. * For database availability, SQL storage must have actually opened. * Check heartbeat errors and the configured timeout; timeout must exceed two ping intervals. * Confirm each player node has its own safe node ID.
A replay is selected, but the player does not move or playback never starts A success result means a transfer message was sent, not that the proxy accepted it. Check proxy server registration, exact node names, network reachability, and BungeeCord-channel compatibility. On Velocity, check its plugin-message compatibility setting. If the player moves but playback does not start, check the player's storage access and pending-handoff processing. Handoffs expire after five minutes and are consumed once. A load failure on arrival can disconnect the viewer; keep that server's log. [Review network setup →](/use-reverse/network.md)
The standalone catalog does not open on a network replay server Standalone player menus are created only when availability is disabled at startup. In network mode, use the lobby catalog. Changing the YAML mode without restart does not create/remove the already constructed runtime components.
Sounds or visual effects are missing Reverse records supported gameplay, not a video of each player's screen. Some sounds or personal effects may not be captured, and seeking does not replay every earlier sound or animation. Try a short recording of the specific action. Custom plugin screens and resource-pack effects may behave differently from ordinary world activity.
Blocks look wrong on another Minecraft version An older Minecraft version cannot display every block added in a newer one. For the most predictable result, record and watch on the same supported Minecraft version. If a block is still missing, include the two server versions and replay ID in your support report.
The replay ends before the recorded duration Playback ends after the final tick carrying recordables, not after the wall-clock recording duration. A quiet tail can therefore disappear from playback. Use the HUD's timeline total rather than its recorded-duration field when diagnosing this.
The log reports an unknown codec or invalid container version Check that recorder, player, and any replay extensions use compatible releases. A recording created with a different version or a missing extension may not load. Do not manually edit the recording file; keep a copy and contact support with the error and the versions used to record and watch it.
My menus, hotbar, or messages look wrong * Use MiniMessage tags, not `&` color codes. * Menu slots are zero-based; player hotbar slots are 1–9. * Visibility lists require all listed states, not any one of them. * Check materials supported by your server. * Disable conflicting scoreboard/action-bar/inventory writers during diagnosis. * Keep valid speed/interval lists and unique enabled hotbar slots. [Review display settings →](/configure-and-customize/display.md)
## Is the feature available? Check the [command guide](/use-reverse/commands.md) and your release notes for the available features. There is no video-export, automatic storage-migration, or retention-scheduling command. Arena bounds and participant selection are available to game plugins through the Java API. ## Still stuck? Use the [support checklist](/keep-things-running/operations.md) to collect a reproducible case. Include the exact command, expected result, observed result, and first relevant stack trace. --- # 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/troubleshooting.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.