> For the complete documentation index, see [llms.txt](https://docs.fansports.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fansports.fun/getting-started/card-package.md).

# Card Package

**Player Pack Opening** is a core feature of FanSports.fun that allows users to spend **Fan Points (FP)** to open randomized **Player Packs** and receive **Player Shares**.

Player Shares represent a user’s level of ownership in a football player.\
The number of Shares directly influences:

* Tournament performance
* Ranking points
* Reward distribution across competitive events

This mechanism introduces both strategic decision-making and excitement through randomness, while maintaining measurable value through Share quantities.

***

#### 2. Pack Structure

Each Pack contains **4 Player Cards**, with randomized players and Share amounts depending on the Pack type.

| Pack Type               | Pack Price | Player Cards | Total Shares Range |
| ----------------------- | ---------- | ------------ | ------------------ |
| **Pro Pack**            | 125 FP     | 4            | 31 – 46            |
| **Epic Pack**           | 500 FP     | 4            | 124 – 184          |
| **Legendary Pack**      | 5,000 FP   | 4            | 1,240 – 1,840      |
| **World Cup 2026 Pack** | 500 FP     | 4            | 124 – 184          |

> Each Pack guarantees the number of player cards and Share ranges as defined above.\
> Player selection remains randomized within supported leagues and events.

***

#### 3. Pack Purchase Flow

The Pack Opening process is designed to ensure transparency and usability:

1. **Pack Selection**\
   The user selects a desired Pack type.
2. **FP Balance Validation**
   * The system automatically checks the user’s available Fan Points.
   * If the FP balance is insufficient, the **Purchase button is disabled**.
   * If the FP balance is sufficient, the **Purchase button becomes enabled**.
3. **Pack Purchase & Opening**
   * The user confirms the purchase.
   * FP is deducted instantly.
   * The Pack is opened immediately.
4. **Result Display**\
   After a successful purchase, the system reveals the rewards in a dedicated result screen.

***

#### 4. Pack Opening Result Display

Once a Pack is opened, the interface displays the full reward details received by the user.

#### Information Shown to the User

**Pack Summary**

* Total combined value of the 4 Player Cards

**Per Player Card**

* Player image
* Player name
* Playing position (e.g., GK, DEF, MID, FWD)
* Number of Player Shares received

All rewards are instantly added to the user’s account and become available for:

* Squad building
* Tournament participation
* Trading within the Player Share marketplace

***

#### 5. Economic Role

Player Packs act as a primary **FP sink** within the FanSports.fun economy, ensuring:

* Continuous utility for Fan Points
* Fair distribution of Player Shares
* Sustainable player circulation across the ecosystem

This system balances randomness with defined economic boundaries, supporting long-term platform growth and competitive integrity.


---

# 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.fansports.fun/getting-started/card-package.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.