> For the complete documentation index, see [llms.txt](https://amgmu.gitbook.io/amgmu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amgmu.gitbook.io/amgmu/castle-siege/cs-event-mechanics.md).

# ▶️ CS Event Mechanics

<mark style="color:orange;">**Castle Siege Event Guide**</mark>

**Duration:** 1 hour **Throne Investment Time:** Up to 60 seconds

1. <mark style="color:green;">**Investment Mechanics:**</mark>
   * To claim the throne, the **Sealer** must stay within the throne area and accumulate investment time (e.g., 30 or 55 seconds).
   * If the Sealer leaves the throne area, their invested time will decrease by 1 second every second they remain outside.
   * If the Sealer does not return to the throne in time, their entire investment will be lost.
2. <mark style="color:green;">**Guild Roles:**</mark>
   * Both the **Guild Master (GM)** and the **Assistant Guild Master (AGM)** can invest in the throne.
   * However, their investments are **independent**. For example, if the Guild Master starts investing, the Assistant Guild Master cannot continue their progress and vice versa. Also, Guild members/holder must hold the switches at the same time in order for their Guild Master invest time to the throne or else if one of the holders release the switch, Guild Master will not be able to invest time on the throne.
3. <mark style="color:green;">**Winning Condition:**</mark>
   * The guild that first reaches **60 seconds of throne investment** will take control of the castle.
   * To secure victory, the guild must defend the castle for the remaining time in the event (up to 1 hour).
4. <mark style="color:green;">**Castle Ownership:**</mark>
   * The winning guild will gain control of the castle and access to the **Land of Trials** for 1 week.
   * Ownership lasts until the next Castle Siege event begins.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://amgmu.gitbook.io/amgmu/castle-siege/cs-event-mechanics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.