> For the complete documentation index, see [llms.txt](https://docs.leagueofthrones.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leagueofthrones.com/lotpvp-season/overview.md).

# Overview

<figure><img src="/files/NkX5klxjJnHZez7gAgkR" alt=""><figcaption></figcaption></figure>

LOT’s PVP season is redesigned based on feedbacks and data from our classic seasons, with a pivot to heavier financial part in gameplay.

LOT PVP is a map based FOMO game played in DAOs. Players conquer plots no longer through attaching them, but bidding on them in a dutch auction, winner of the auction owns the plot and shares that come with it. When plots get auctioned, the ZETA token that the bidder spent is going to several different pools, one is the Trail Blazer pool, rewarding the single player who first conquer the centre city, one is the winning DAO pool, rewarding the team who win the season, one is the plot owners pool, rewarding all plot owners according to the shares, another one is lottery pot, rewarding users who made purchase of plots or invited people to join the season.


---

# 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://docs.leagueofthrones.com/lotpvp-season/overview.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.