> For the complete documentation index, see [llms.txt](https://wiki.minervasmp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.minervasmp.com/smp-information/claims.md).

# ☆ Claims

Land claims are an essential feature on Minerva SMP that let players protect their builds, farms, and personal areas from griefing or unwanted interference. With land claims, you can safely build and explore while knowing that your creations are secure. Claims give players control over who can access their land and help keep the server organized and enjoyable for everyone.

#### **Land Claims Information ♡**

☆ **What Are Land Claims?**\
ㅤ⤷ Land claims are protected areas that players can create around their builds. Within your claim, only you and trusted players can build, break blocks, or interact with containers. This allows you to safely construct bases, farms, or community builds without worrying about griefing.

☆ **Claim Rules**

* All claims must follow the **server rules**.
* No claim abuse or blocking public resources unnecessarily.
* Respect other players’ claims  do not build near, or destroy around their claimed areas.

☆ **Claim Limits**

* The number of claim blocks you start with depends on your rank (default 100 per hour).
* As you play and earn more claim blocks, you can expand your protected area.
* Higher ranks allow for larger claims, giving more space for big projects.

☆ **Trusting Players**

* You can **trust** other players to build or interact within your claim.
* Use the `/trust <player>` command to grant access and `/untrust <player>` to remove it.
* Check who has access with `/trustlist` to keep your claim secure.

#### **Land Claim Commands ♡**

**/claimslist** - Shows your current claims and how many claim blocks you have left.\
\&#xNAN;**/abandonclaim** - Deletes the claim you are currently standing in.\
\&#xNAN;**/abandonallclaims** - Removes all of your current claims.\
\&#xNAN;**/trust \<username>** - Grants another player access to your claim.\
\&#xNAN;**/untrust \<username>** - Removes a player’s access to your claim.\
\&#xNAN;**/trustlist** - Lists all players who have access to your claims.\
\&#xNAN;**/claimblocks** - Displays how many claim blocks you currently have available.\
\&#xNAN;**/claimbonus** - Shows your bonus claim blocks from rank or purchases.

#### **Land Claim Tips ♡**

♡ **Plan your claim** - Make sure your claim covers all the important areas like farms, bases, and storage.\
♡ **Use corners wisely** - Claims are rectangular, so plan efficiently to avoid wasting claim blocks.\
♡ **Trust carefully** - Only give access to players you know and trust; this prevents accidental griefing.\
♡ **Respect public areas** - Don’t claim community farms, roads, or event spaces unless permitted.\
♡ **Expand as you grow** - Save claim blocks for future builds and expansions.\
♡ **Check boundaries** - Use `/claimslist` often to ensure your land is secure and all trusted players are up to date.


---

# 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://wiki.minervasmp.com/smp-information/claims.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.
