> 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/community/server-rules.md).

# Server Rules

The live `/rules` menu is the final authority. This page summarizes the core expectations.

### 1. Play Fair

Do not use:

* Hacked clients.
* X-ray.
* Automated combat or movement.
* Unauthorized macros.
* Duplication.
* Packet abuse.
* Exploits that provide an unfair advantage.

### 2. Do Not Bypass Protection

Do not use bugs, glitches or desync to bypass Lands, WorldGuard, vaults, shops or other protections.

### 3. Respect Other Players

Harassment, hate speech, sexual harassment, real-world threats, doxxing and targeted abuse are not allowed.

Competitive trash talk does not excuse crossing these boundaries.

### 4. Keep Chat Usable

Do not spam, flood, advertise unrelated servers, impersonate staff or repeatedly provoke arguments.

### 5. Use Intended PvP and Raiding Mechanics

PvP and territorial conflict are part of the server. Social deception, betrayal, theft and insiding are governed by the current `/rules`.

Unintended access and exploit-based raiding are always forbidden.

### 6. No Ban Evasion

Do not use alternate accounts or another platform to avoid a punishment.

### 7. Appropriate Content

Usernames, skins, builds, signs and messages must remain appropriate for the community.

### Enforcement

Punishments depend on severity, history and intent. Staff may act on behavior not exhaustively listed when it clearly harms the server or its players.


---

# 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/community/server-rules.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.
