> For the complete documentation index, see [llms.txt](https://shodo-veil.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shodo-veil.gitbook.io/whitepaper/guild-system/guild-member-kick-policy.md).

# Guild Member Kick Policy

Anything on this page is subject to change throughout the development progress of the game. We will thoroughly test and validate any feature before it goes live.

If you have inactive guild members, worry not. SHODO VEIL now offers a Guild Member kick feature to help you in curating the right members for your guild.

Certain rules are in place to ensure fairness in Shards for all players.

#### Member Kick Policy <a href="#member-kick-policy" id="member-kick-policy"></a>

1. Guild Members cannot be kicked unless they are earning fewer trophies than the regulated trophy amount every 3 days

These numbers are set by SHODO VEIL, and can be subject to balancing if necessary.

| Guild Level | Minimum Trophies every 3 Days   |
| ----------- | ------------------------------- |
| 1           | 25 minimum trophies requirement |
| 2           | 30 minimum trophies requirement |
| 3           | 40 minimum trophies requirement |
| 4           | 45 minimum trophies requirement |
| 5           | 55 minimum trophies requirement |


---

# 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://shodo-veil.gitbook.io/whitepaper/guild-system/guild-member-kick-policy.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.