> For the complete documentation index, see [llms.txt](https://f10.gitbook.io/f1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://f10.gitbook.io/f1-docs/overview/gp-tournaments.md).

# GP Tournaments

### Grand Prix Results & Scoring System

Grand Prix results for each season are retrieved in real time via an official API.\
Points are then distributed based on:

* The cards selected for the tournament
* Their **tiers** and **rarity**
* The number of **tokens held** for driver cards

***

### Tournament Lineup

For each tournament, you can select:

* **2 Drivers**
* **1 Car**
* **1 Engine**
* **1 Engineer**

Your lineup must respect the **100-point team budget**.

***

### Budget Point System

Each team has a maximum budget of **100 points**.\
Card costs are determined by their **Tier** (not rarity), ensuring fair competition.

#### Drivers

* **Tier S+**: 30 pts
* **Tier S**: 24 pts
* **Tier A**: 19 pts
* **Tier B**: 14 pts

#### Car

* **Tier S+**: 24 pts
* **Tier S**: 20 pts
* **Tier A**: 16 pts
* **Tier B**: 12 pts

#### Engine

* **Tier S+**: 19 pts
* **Tier S**: 15 pts
* **Tier A**: 11 pts

#### Engineer

* **Tier S+**: 18 pts
* **Tier S**: 14 pts
* **Tier A**: 10 pts
* **Tier B**: 7 pts

**Example lineup:**\
2× S+ Drivers (60) + S Car (20) + A Engine (11) + B Engineer (7) = **98 pts**

You cannot stack only S+ cards, ensuring balanced and strategic team building.

***

### Card Rarity Multipliers

Card rarity directly affects how many points you earn.

* **Common**: 1.0×
* **Rare**: 1.25×
* **Epic**: 1.5×
* **Legendary**: 2.0×

Higher rarity cards have limited supply and significantly higher impact in competitive tournaments.

***

### Race Scoring

#### Driver Position Points

* 1st: +25 pts
* 2nd: +18 pts
* 3rd: +15 pts
* 4th: +12 pts
* 5th: +10 pts
* 6th: +8 pts
* 7th: +6 pts
* 8th: +4 pts
* 9th: +2 pts
* 10th: +1 pt
* 11th–20th: 0 pts
* **DNF / Not Classified**: −20 pts
* **Disqualified**: −20 pts

#### Driver Bonuses

* Positions gained: +2 pts per position
* Positions lost: −1 pt per position
* Overtakes made: +1 pt per overtake
* Fastest lap: +10 pts

***

### Car (Chassis) Scoring

Based on constructor race results:

* 1st (Constructor): +25 pts
* 2nd: +18 pts
* 3rd: +15 pts
* 4th: +12 pts
* 5th: +10 pts
* 6th–10th: +5 pts
* 11th+: 0 pts

#### Team Bonuses

* Both drivers finish in points: +10 pts
* Double podium: +25 pts

Chassis cards score based on combined team performance and constructor championship standings.

***

### Engine Scoring

* Fastest lap (your driver): +15 pts
* Fastest lap (any driver using same engine): +8 pts
* Top speed trap: +5 pts
* No reliability issues: +10 pts
* Engine failure: −15 pts

Engine cards benefit from **any driver using the same power unit** (Ferrari, Mercedes, Red Bull, etc.). Reliability is critical.

***

### Engineer Scoring

#### Strategy & Reliability Bonuses

* No reliability issues (no DNF/DSQ): +10 pts
* Perfect strategy (4+ positions gained): +20 pts
* Good strategy (2–3 positions gained): +10 pts
* Decent strategy (1 position gained): +5 pts

Strategy bonuses are calculated by comparing average driver positions **before the first pit stop** and **after all pit stops**.\
This rewards smart tire management, pit timing, undercuts, and overcuts.

***

💡 **Important:**\
All points (positions, bonuses, penalties) are **multiplied by the card’s rarity multiplier** before being added to your final tournament score.


---

# 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://f10.gitbook.io/f1-docs/overview/gp-tournaments.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.