# Rewards to Teams

🛠️ **Team Creation and Costs**\
To create a team, a certain amount of cores must be paid, which varies depending on the rarity of the cards owned and the number of team members. The main advantage of playing in a team is the opportunity to play with people you know.

🏅 **Trophy Rewards**\
The trophy rewards for teams will be identical to those for single matches. The primary difference concerns the cost of creating the team and the dynamics of team gameplay.

🎁 **Rewards for Team Matches**\
In team matches, the best players from both the winning and losing teams will be rewarded with a Cypher Box. The in-game currency rewards given to teams will follow the same logic as normal matches, increasing based on the fees spent and maintaining the same proportion as a regular match.

🌟 **Bonus for the Team Creator**\
The team creator will receive a 5% bonus compared to other members, as a reward for spending the cores necessary to create the team. Therefore, all rewards will be divided among all participants, with 5% reserved for the team creator.

This structure ensures that all team members are incentivized to participate and actively contribute, while the team creator is rewarded for their initial investment.


---

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

```
GET https://whitepaper-34.gitbook.io/rivalrumble/domestic-economy/rewards-to-teams.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.