> 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/limit-what-builders-can-do.md). # Limit what builders can do The examples use LuckPerms and a group called `builder`. Every node is listed in [Permissions](/reference/permissions.md). ## Cap the brush size Large brushes change many blocks per click. Lower `generic.max-size` in `config.yml` and run `/gopaint reload`. Builders cannot set a larger size afterwards, neither with `/gopaint size` nor in the menu. ## Take away a single command Negate its node, for example to stop builders from changing their size by command: ``` lp group builder permission set bettergopaint.command.size false ``` `/gopaint help` stops listing that command for them. ## Keep builders out of a world Add the world to `generic.disabled-worlds`; see [Disable painting in a world](/for-server-admins/disable-painting-in-a-world.md). To let a trusted group paint there anyway: ``` lp group lead-builder permission set bettergopaint.world.bypass true ``` ## Let a group reload the configuration ``` lp group lead-builder permission set bettergopaint.admin true ``` This grants `/gopaint reload`. --- # 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/limit-what-builders-can-do.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.