# Community & Social Systems

* **Global & Per Game leaderboards**

The AstroVerse leaderboard system is set across the whole ecosystem as well as into each game. Rankings are dynamic and real-time, and reset weekly and seasonally to ensure competition is fresh. The best players get bonus points, rare cosmetics, and permanent rewards that can be used in any of the games. Unique player tags in the form of custom blockchain-linked tags turn each position in the leaderboard into a source of pride among players.

* **Cross-Game Guilds**

Guilds bring players together in AstroVerse, allowing them to participate in cross-game events, accomplish common objectives, and scale guild leaderboards that reward participation. Guild-only tournaments, group activities, and unique benefits that enhance both individual and group progress will be added.

* **Seasonal Competitions & Tournaments**

AstroVerse seasons will feature high-stakes competitions, with exclusive rewards such as rare gear, cosmetic effects, and collectible badges. Seasonal ranks are regularly reset, providing every player with another opportunity to win, keeping the competitive side of the games alive and dynamic.

* **Telegram & Other Social Sharing**

Smooth social sharing features enable gamers to share scores, streaks, rare discoveries, and guild achievements to Telegram chats, groups, and other services with a single tap. Inviting friends is easy by using special referral links and codes where both the inviter and the invitee get bonuses. Each success is a moment to be shared and it brings organic growth and friendly competition throughout the community.<br>


---

# Agent Instructions: 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:

```
GET https://astroverse-1.gitbook.io/astroverse-docs/community-and-social-systems.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
