> 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/customization/single-plot-area.md).

# Single plot area

This is a new feature added in PlotSquared v5.12.0, that allows you to create plots one by one inside of ordinary (not a plot world) worlds. The process is quite simple:

## Setup

1. Create a square/cuboid selection using WorldEdit's wand (`//wand`). The lowest Y value in the selection will be the plot height, and determines where you teleport by default, where the floor is generated when using `/plot set`, etc.
2. Use `/plot area single <name>`, where `<name>` is a unique identifier. This will be used when teleporting to the area, etc.
3. The area is now created.

When creating the area, PlotSquared saves a schematic which will be used when regenerating the area when using `/plot clear`, `/plot delete` and other regenerative commands. Thus, the plot can be cleared to restore it to its original state.

The plot area settings can be modified just like normal area settings.


---

# 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/customization/single-plot-area.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.