> For the complete documentation index, see [llms.txt](https://docs.gearrunner.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gearrunner.app/game-modules/events-seasons-and-competition.md).

# 🏆 Events, Seasons & Competition

Competitive content keeps Gear Runner dynamic and engaging.

### Event Types

* **Daily & Weekly Missions**\
  Simple challenges that fit naturally into your routine and reward consistent activity.
* **Seasonal Leaderboards**\
  Track your progress over a season and see how you stack up against other players.
* **Limited-Time Tournaments**\
  Short, high-energy events for players who enjoy pushing their limits and competing for special rewards.

### Why Seasons Matter

Seasons keep competition fresh and fair:

* Everyone gets regular chances to start strong
* New players can jump in without feeling behind
* Goals and challenges stay exciting and varied

Rewards are designed to value **participation, consistency, and smart play**, not just how much you move in a single session.


---

# 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.gearrunner.app/game-modules/events-seasons-and-competition.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.