# Core Scoring Logic (Fantasy Mode)

Rebellion’s Fantasy Mode uses a simple, transparent scoring model. Your portfolio performance is converted into a direct point score based on absolute returns. No adjustments. No rankings against other players. Just pure results based on market movement.

***

🔢 **Scoring Process Overview**

Each player builds a portfolio of 10 equally weighted assets. Your score is calculated in two steps:

***

**1️⃣ Portfolio Return**

Your return is the average of all asset performances, each weighted equally at 10%.

**Formula:**\
**Portfolio Return = ∑ (10% × % Price Change of Each Asset)**

* Each asset contributes 10%
* No custom weights, leverage, or sector bonuses
* Assets with 0% price change contribute 0%

***

**2️⃣ Score Conversion**

Your total return is multiplied by 100 to get your final game score.

**Formula:**\
**Score = Portfolio Return × 100**

🧪 **Example**

* 10 assets, 7-day game duration
* Your team return: +2.80%
* Final Score: 2.80 × 100 = **280**

***

🏁 **Ranking & Tie-Breakers**

Players are ranked by their **absolute score**.\
Tie-breaker: earlier valid team submission.\
No trimming or relative metrics used.

***

🔒 **Important Clarification**

Fantasy Mode uses only absolute scoring for ranking.\
There is no adjustment based on other users’ returns.\
XP (Experience Points) are awarded in official games based on your final rank.\
(See Leaderboard System for XP structure.)


---

# 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://rebellion.gitbook.io/rebellion/scoring-system/core-scoring-logic-fantasy-mode.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.