> For the complete documentation index, see [llms.txt](https://jester.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jester.gitbook.io/docs/tokenomics/favour/seasons.md).

# Seasons

Every year, the court turns through four Seasons. To keep things fresh and cultural, each year
\
carries a different thematic set of names, always under the “Season of …” banner. Badges
\
can be earned in each season for different reasons which may add bonus Favour or multipliers in subsequent seasons or years. \
\
**Examples:**
\
Year 1 (Option A – Regal/Martial Cycle)
\
Season of the Crown
\
Season of the Sword
\
Season of the Harvest
\
Season of the Revels
\
Year 2 (Option B – Bestial-Court Cycle)
\
Season of the Lion
\
Season of the Stag
\
Season of the Falcon
\
Season of the Bear \\

\
**Each Season concludes with Spoils distribution, resets all Favour, and begins the next**
\
**chapter.**

{% hint style="info" %}
*Dev’s Note: This framework is both simple and immersive. “Season of …” is easy to*
\
*remember, but the rotating themes add lore and culture. It also improves the usability of the ecosystem by gamifying it, while ensuring the underlying architecture is clean and professional.*
{% endhint %}

***

**Seasonal Reset**

At the end of each Season:
\
All Favour is tallied and reset to 0.
\
Holders retain their tier if requirements are met.
\
Referrals remain tied, but only generate Favour if active in the new Season.

{% hint style="info" %}
*Dev’s Note: Resets keep competition alive and stop runaway winners. Each Season feels like a new tournament, refreshing hype and giving everyone a fair shot.*
{% endhint %}


---

# 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://jester.gitbook.io/docs/tokenomics/favour/seasons.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.