> For the complete documentation index, see [llms.txt](https://docs.onelitefeather.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelitefeather.net/background/scope-and-non-goals.md). # Scope and non-goals BetterGoPaint does one thing: interactive terrain painting with a held item. Out of scope: * **Servers other than Paper.** The plugin ships a `paper-plugin.yml` and uses Paper API. Spigot, CraftBukkit and hybrid servers cannot load it. * **Folia (not declared yet).** BetterGoPaint is prepared for Folia: it schedules work through Paper's region-aware schedulers, and brush strokes only touch the world through WorldEdit. It does not declare Folia support, because stable FastAsyncWorldEdit does not support Folia yet. Support will be declared once a FAWE release does. * **Running without FastAsyncWorldEdit.** Every edit goes through FAWE; plain WorldEdit lacks the APIs the brushes use. * **Old Minecraft versions.** Only the versions in [Supported versions](/reference/supported-versions.md) are built and tested. The original goPaint covers older versions. * **Running next to goPaint.** BetterGoPaint replaces goPaint and disables itself if both are installed. --- # 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.onelitefeather.net/background/scope-and-non-goals.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.