> For the complete documentation index, see [llms.txt](https://docs.metacces.com/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metacces.com/whitepaper/metacces-general/ar-vr-game/game-structure/game-seasons/introduction.md).

# Introduction

In Metacces, the game does not proceed at a steady pace, but pulses with life through the symbolic seasonal system (Seasons) — which are temporal cycles launched periodically, and transform the experience into a renewed journey interconnected with the evolution of the digital world.

Seasons are not just "periodic updates," but are the pulse of the collective consciousness of the game; the way the system breathes, changes, and evolves.

Each season represents a new symbolic gateway, opening before players a world of interactive stories, mental tasks, rare rewards, and strategic opportunities. They are decisive moments that reshape the course of narrative, game rules, and community dynamics.

Here, the player is not just an interactor with the game... but a partner in making its symbolic history.


---

# 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.metacces.com/whitepaper/metacces-general/ar-vr-game/game-structure/game-seasons/introduction.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.