> 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-builders/share-a-brush-as-an-item.md).

# Share a brush as an item

You can bake the current brush settings into an item and hand it to another builder.

1. Hold any item that is not a block and not the brush item, for example a stick.
2. Open the brush menu and left-click the item onto the brush slot (the brush item in the second row, slot 10 in the [brush menu reference](/reference/brush-menu.md)).

   ![Brush menu with the brush item in the second row, slot 10, which is the target of the left-click](https://862810040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3dAk0UjgUbQUOWgnpUwe%2Fuploads%2Fgit-blob-5bfd0668a3bc3f53d2759887cb64cf96145c3234%2Fmenu-sphere-default.svg?alt=media)
3. The item now carries the brush, its size, the palette and every brush setting.

Right-clicking with that item paints with the stored settings, independent of the holder's own brush. The holder still needs `bettergopaint.use`.

The settings are stored in the item's data, not in its name or lore. Renaming the item in an anvil or editing its lore does not change the brush.

## Items exported with BetterGoPaint 1.x

Older items kept their settings in the lore. They still work: the first right-click reads the lore, uses the configured default for any line it cannot read, and converts the item to the new format.


---

# 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-builders/share-a-brush-as-an-item.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.