> For the complete documentation index, see [llms.txt](https://docs.anotherlevel.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anotherlevel.it/documentation/documents/worldguard.md).

# WorldGuard

WorldGuard Integration Guide

To integrate WorldGuard with our plugin, follow these steps to ensure a seamless setup. This guide will help you to restrict access to a specific area for players without registered documents, enhancing control and gameplay dynamics.

**Requirements**

* **WorldGuard Plugin**: Ensure WorldGuard is installed and running on your server.

**Steps for Setup**

1. **Create a Region**:
   * Firstly, define a region within WorldGuard. This region will act as a controlled area where you want to enforce document registration.
2. **Set the Flag**:
   * Once the region is created, you need to set a custom flag - `documents-registration-flag` to `DENY`. This flag will prevent unregistered players from leaving the specified region until their documents are successfully registered.

By setting this flag to `DENY`, you effectively create a mechanism that ensures all players within the designated area are registered, enhancing both security and immersion within your server.

For more detailed instructions on creating regions and setting flags in WorldGuard, please refer to the official WorldGuard documentation.


---

# 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.anotherlevel.it/documentation/documents/worldguard.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.