> For the complete documentation index, see [llms.txt](https://wiki.sempermc.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.sempermc.net/core-gameplay/teams-and-nations.md).

# Teams and Nations

SemperMC uses Lands for player territory and Nations for larger alliances.

### Building a Team

A strong team needs more than many members:

* A leader who manages permissions.
* Builders who do not automatically receive vault access.
* Combat members with replacement gear.
* Shared goals and clear rules.
* Separate public and private storage.

### Trusting Players

Use `/lands trust <player>` carefully.

Before granting access:

1. Check the role being assigned.
2. Review container, block and entity permissions.
3. Create restricted sub-areas.
4. Avoid placing every valuable item in one shared room.
5. Remove access when someone leaves.

### Relations

Lands can form allies and enemies through `/lands relations`.

Allies are useful for:

* Shared defense.
* Trade.
* Coordinated boss fights.
* Nation growth.
* War support.

Relations do not replace careful permissions.

### Nations

Nations organize multiple Lands under a larger identity. Use `/nations` to inspect available commands and requirements.

Nation systems may influence diplomacy, war participation, territory and long-term competition.


---

# 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.sempermc.net/core-gameplay/teams-and-nations.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.