> 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/for-server-admins/upgrade-from-bettergopaint-1.md).

# Upgrade from BetterGoPaint 1.x

BetterGoPaint 2 runs only on Paper 26.1.1 or newer with Java 25. If your server stays on Minecraft 1.21, keep BetterGoPaint 1.1.x.

1. Back up `plugins/BetterGoPaint/`.
2. Update the server to a version listed in [Supported versions](/reference/supported-versions.md) and switch it to Java 25.
3. Update FastAsyncWorldEdit to 2.16.1 or newer.
4. Replace the BetterGoPaint jar in `plugins/` with the 2.x jar.
5. Start the server. Your `config.yml` is kept; its keys did not change. BetterGoPaint rewrites the comments and adds the new key `generic.check-for-updates`.
6. Check the console for `config.yml: … has the invalid value` warnings and fix the named keys. See [Console messages](/reference/console-messages.md).
7. Review your permissions:
   * `/gopaint reload` now needs `bettergopaint.command.admin.reload`. Groups that have `bettergopaint.admin` keep it, because `bettergopaint.admin` grants that node.
   * `/gopaint size`, `toggle`, `info` and `help` each have their own node. They default to `true`, so groups with `bettergopaint.use` keep every subcommand. See [Limit what builders can do](/for-server-admins/limit-what-builders-can-do.md) to take one away.

Brush items that builders exported with 1.x keep working. Each one is converted to the new format the first time someone paints with it.

If something goes wrong, stop the server, put the 1.x jar and your backup back, and start it on the old Minecraft version again.


---

# 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/for-server-admins/upgrade-from-bettergopaint-1.md?ask=<question>&goal=<user_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.