> 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.md).

# Guild System

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.

At the heart of SHODO's social dynamics lies the Shards, a cornerstone empowering founders to foster a vibrant player community. This structure unlocks a realm of game-related perks, such as exclusive quests, guild bosses, tournaments, and other features exclusively available to guild members.

Guild Rewards Guild Owners can set the percentage of rewards distributed to Fraction and Guild Seat owners, however keep in mind Seasonal rewards for Seat owners are not divided equally to all members. Rewards are largely based on performance, with those who earn more trophies and higher rankings receiving a larger share of the pot. For instance, if the Guild Owner sets 80% rewards for Guild Seats, this distribution heavily depends on members' contributions within the guild


---

# 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.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.