> 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/reference/coverage.md). # About these guides How to use these guides, examples, and version-specific instructions. This documentation is for server owners using the marketplace download and developers building against the public API. All installation and integration steps are designed to work without access to Reverse's implementation. ## Choose the right guide | I am… | Start here | | ----------------------------------- | --------------------------------------------------------- | | Installing the plugin | [Installation](/get-started/installation.md) | | Making my first recording | [Your first replay](/get-started/quick-start.md) | | Running a server network | [Lobby and proxy setup](/use-reverse/network.md) | | Updating an existing setup | [Updates and compatibility](/reference/build-and-docs.md) | | Writing an integration | [API setup](/api-introduction/getting-started.md) | | Looking for a complete code example | [Example gallery](/api-how-to-guides/examples.md) | ## Reading configuration and commands Replace command placeholders such as `` with real values. Configuration snippets show sections to merge into the generated file unless a guide says otherwise. They are not complete replacement configurations. The settings generated by your installed release and its marketplace release notes take priority when a feature changes between versions. ## Using the API examples Get the API through Maven Central and choose a version compatible with your installed plugin. `REVERSE_VERSION` in dependency examples is a placeholder to replace with that published version. Java examples describe code in **your own integration**. Complete examples are included in the documentation, along with the imports they need. Shorter excerpts assume the context introduced on that page. Examples are building blocks, not ready-to-install game plugins. Connect them to your own commands, match lifecycle, permissions, and error handling. Always test saving, playback, and cleanup with your actual server setup. ## Compatibility and support Check the marketplace listing for supported Minecraft/server versions and follow the release notes when updating. Use matching Reverse releases across your servers and compatible versions of any extensions. If something does not work, the [troubleshooting guide](/keep-things-running/troubleshooting.md) lists the most useful checks and the information to include in a support report. --- # 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/reference/coverage.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.