> For the complete documentation index, see [llms.txt](https://intellectualsites.gitbook.io/plotsquared/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intellectualsites.gitbook.io/plotsquared/features/block-bucket.md).

# Block Buckets

## Introduction

Block buckets allow you to specify however many blocks you want, for every component of a plot. You can specify the block weight, which will determine how likely the block is to be picked from the bucket.

* `stone,grass_block,cobblestone,sandstone` will automatically infer that there should be 25% of each of the four blocks
* `stone:50,grass_block:30,sandstone:20` will use 50% of stone, 30% of grass\_block and 20% of sandstone.

## Formatting

Blocks can be in the format `namespace:block[property1=value1,property2=value2]` (The properties and namespace are optional, and `grass_block` will resolve to `minecraft:grass_block[snowy=false]`. [More info](https://minecraft.wiki/w/Block_states))

Complex patterns are also accepted:

* [FAWE Patterns](https://github.com/IntellectualSites/documentation/blob/main/fastasyncworldedit/advanced-features/patterns.md) (If you have FAWE installed)
* [WorldEdit Patterns](https://worldedit.enginehub.org/en/latest/usage/general/patterns/)

## Disallowed Blocks

To restrict what blocks are allowed for the patterns, configure the `disallowed-blocks` list in `plugins/WorldEdit/config.yml`, or `plugins/FastAsyncWorldEdit/worldedit-config.yml`.


---

# 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://intellectualsites.gitbook.io/plotsquared/features/block-bucket.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.