> For the complete documentation index, see [llms.txt](https://mellowcraft-plugins-and-info.gitbook.io/mellowcraftguides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mellowcraft-plugins-and-info.gitbook.io/mellowcraftguides/getting-started/claiming-your-land.md).

# Claiming Your Land

### Claiming

Claiming is done by using /kit claim, which will give you a book, a golden shovel, and a stick. If you don't like reading long books about how to claim land, easier to digest information is here to help you! \
\
To claim a piece of land, use the golden shovel that you are given, and right-click 2 diagonal corners. This will create a plot of land that is yours to do whatever you would like with (Within the rules of course!) If your space is too small, you can use the stick to figure out the border of your claim (Which will show as golden blocks), where you can then right-click the corner you would like to extend, bring out the corner diagonally to another point, where you right click again.&#x20;

### Trust and Permissions

To trust someone to build and interact fully with your claim, you can use the command  /trust \[username]. To give them access to trusting others, you can use /permissiontrust \[username], and to give a player, or all people, access to the chests of your claim, you can do  /accesstrust \[username], or /accesstrust all to give everyone access to the chests in your claim (Helpful for public mob grinders/farms).&#x20;

### Subdividing Claims

Would you like to give trust to someone, but only in specific parts of your claim? If so, you can use the command /subdivideclaim, which will then allow you to select a region of your claim that is still owned by you, but has a different trustlist to your main claim. This opens the possibility for towns, accesstrust in specific regions, and more!&#x20;

### Claimflags&#x20;

Claimflags are a way to further alter your claim. As a player, you have access to the following claimflags, which you can set with the command /setclaimflag: \
\
\- EnterMessage: Allows you to set a message that is displayed to a player when they enter your claim. \
\- NoBlockFade: Removes the ability for blocks to fade, melt, or disappear based on world conditions. \
\- NoEnter: Allows you to block all players from entering your claim. \
\- NoEnterPlayer: Allows you to block specific players from entering your claim. \
&#x20; Example - /setclaimflag NoEnterPlayer Cleons \
\- NoGrowth: Allows you to stop any plants, crops and blocks from growing in your claim. \
\- NoHunger: You will not lose any hunger while in your claim. \
\- NoMobSpawns: Blocks all **passive** mob spawns in your claim. \
\- NoMonsters: Blocks all **hostile** mob spawns in your claim. \
\- NoOpenDoors: Blocks players from opening doors in your claim. \
\- NoVineGrowth: Allows you to block vines from growing/spreading in your claim. \
\
All claimflags can be unset at any time by using /unsetclaimflag. \
&#x20;


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mellowcraft-plugins-and-info.gitbook.io/mellowcraftguides/getting-started/claiming-your-land.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
