> For the complete documentation index, see [llms.txt](https://whitepaper.lastodyssey.io/lastodyssey/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.lastodyssey.io/lastodyssey/5.-gameplay/war-of-thorne/rules.md).

# Rules

### General Rundown&#x20;

<table><thead><tr><th width="163.33333333333331">Week 1</th><th width="128">Week 2</th><th width="154">Week 3</th><th width="166">Week 4</th><th width="163">Week 5</th><th width="172">Week 6</th><th width="167">Week 7</th><th width="174">Week 8</th><th width="165">Week 9</th><th>Week 10</th></tr></thead><tbody><tr><td>Stage 1</td><td>Rest</td><td>Stage 2</td><td>Rest</td><td>Stage 3</td><td>Rest</td><td>Stage 4</td><td>Rest</td><td>Stage 5</td><td> Rest</td></tr></tbody></table>

* The entire season spans 70 days, comprising the 5 stages and the subsequent rest periods. After the final stage, there will be a scheduled break before starting a new season.
* Each season consists of 5 stages, with each stage lasting for 14 days (2 weeks). The first 7 days are the ***War Phase***, followed by a 7-day ***Rest Phase***.

### Arrangement of Each Stage

<table><thead><tr><th width="152.33333333333331">Date</th><th width="125">Time</th><th>War Phase</th></tr></thead><tbody><tr><td>Monday</td><td>UTC 00:00</td><td>Server matching</td></tr><tr><td>Tuesday</td><td>UTC 16:00</td><td>Outter Fortresses activated</td></tr><tr><td>Wednesday</td><td>UTC 16:00</td><td>Outter Ruins activated</td></tr><tr><td>Thursday</td><td>UTC 16:00</td><td>Inner Fortresses activated</td></tr><tr><td>Friday</td><td>UTC 16:00</td><td>Inner Ruins activated</td></tr><tr><td>Saturday</td><td>UTC 16:00</td><td>The Throne activated</td></tr><tr><td>Sunday</td><td>UTC 12:00</td><td>Stage ends</td></tr></tbody></table>

### Details of Each Stage

* Monday UTC 00:00: The event kicks off with Server Matching, where participants are matched and assigned to teams or servers.
* Tuesday UTC 16:00: The Outer Fortresses come to life, offering participants access to strategic positions, challenges, and valuable resources.
* Wednesday UTC 16:00: The Outer Ruins awaken, inviting participants to explore ancient structures, solve puzzles, and uncover hidden treasures.
* Thursday UTC 16:00: The Inner Fortresses spring into action, presenting teams with more challenging defenses, puzzles, and opponents.
* Friday UTC 16:00: The Inner Ruins are activated, providing participants with the opportunity to brave perilous traps, confront formidable adversaries, and discover ancient artifacts.
* Saturday UTC 16:00: The pinnacle of the event arrives as The Throne is activated, becoming the center of fierce competition where teams vie for control and the associated advantages.
* Sunday UTC 12:00: The Stage draws to a close, marking the end of the event.


---

# 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://whitepaper.lastodyssey.io/lastodyssey/5.-gameplay/war-of-thorne/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.
