> For the complete documentation index, see [llms.txt](https://whitepaper.apeironnft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.apeironnft.com/apeironnft/community/esports/apeiron-guild-wars-season-2.md).
# Apeiron Guild Wars Season 2
The 2nd Apeiron Guild Wars kicked off with the release of the Battle Demo Season 2. This time, instead of speedrunning, it was a test of endurance, with players being asked how deep they could make it into the dungeon. They were shooting for Room 539, which, needless to say, is extremely deep - then we would look at the time taken to reach this room.
At the end of the season, the top communities with the highest number of cleared rooms were invited to a special tournament, a Boss Rush event. In teams of 3, communities went head-to-head to see how many bosses they could beat before dying. It was an action-packed event with some surprising upsets, dark horses, and secret strategies all playing a part in determining the winner...but ultimately it was once again PIF DAO that came out on top!
PIF winning the first two Guild Wars is certainly a statement of intent. Will they continue their dominance in Season 3? We'll see!
{% embed url="" %}
---
# 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.apeironnft.com/apeironnft/community/esports/apeiron-guild-wars-season-2.md?ask=&goal=
```
`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.