> 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/worldedit-features.md).

# WorldEdit & FastAsyncWorldEdit features

{% hint style="info" %}
If you want to make other aspects of WorldEdit async as well, you could consider installing [FastAsyncWorldEdit](https://modrinth.com/plugin/fastasyncworldedit). You can find all the permissions to allow FAWE in plots [here](https://github.com/IntellectualSites/documentation/blob/main/fastasyncworldedit/basic-commands/main-commands-and-permissions.md).
{% endhint %}

PlotSquared offers several options related to WorldEdit. By default, it will do the following if you don't have the bypass permission:

* Restrict WorldEdit to plots
* Block access to potentially harmful WorldEdit commands
* Limits the max iterations with several brushes so people can't crash the server
* Limits the max volume to 50 million

The bypass permission is `plots.worldedit.bypass`. If you have this permission, you use the `/plot toggle worldedit` command to disable these restrictions.

To further extend these features, PlotSquared comes with a WE processor you can enable:

* Limits max block states and entities with editing (enable chunk-processor)
* Faster and async WorldEdit changes (enable experimental-fast-async-worldedit) (bypass this with `/plot toggle worldedit`)


---

# 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 dynamically 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/worldedit-features.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 `build a script that syncs our docs to a CMS` 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.
