# Score System

### Score System Overview

Our score system calculates a score based on the user's activity, and rewards are settled and reset every day at UTC+8 based on this score. This allows users to receive rewards in a fair and transparent manner based on a set standard every day.

**For example**, if a specific user scores 500 in a day, and the total score of all users is 10,000 Score, the user will receive tokens equivalent to 5% of the total reward.

### Score Calculation Formula

{% hint style="info" %}
Score = Condition Modifier × (Random Base Score + Performance × Performance Coefficient)
{% endhint %}

The score is calculated based on the energy consumed by the user and the performance of the equipment when using Hunter Mode. The following factors affect the score calculation:

Condition Modifier: The score is calculated based on the energy consumed by the user. Random Base Score: A random value between 1 and 10 is added each time the score is calculated. Performance: The performance of the shoes equipped by the user affects the score. Performance Coefficient (P\_f): A coefficient that adjusts the effect of performance. Critical Event: A critical event that occurs with a certain probability and may increase the score. Chance Factor: Determines the probability that the calculated score will actually be reflected in the total score.

* **Condition Modifier:** The score is calculated based on the energy consumed by the user.
* **Random Base Score**: A random value between 1 and 10 is added each time the score is calculated.
* **Performance:** The performance of the shoes equipped by the user affects the score.
* **Performance Coefficient (P\_f):** A coefficient that adjusts the effect of performance.
* **Critical Event:** A critical event that occurs with a certain probability and can increase the score.
* **Chance Factor**: Determines the probability that the calculated score will actually be reflected in the total score.

{% hint style="danger" %}
Initial specific data for the service may be subject to change for balance patch.
{% endhint %}

### ScoreCap Increase Formula

The ScoreCap system defines the maximum daily score a user can achieve. This cap increases based on the number of NFT shoes the user owns and their rarity. Each rarity has its own multiplier, and the system applies a maximum cap to each rarity level to maintain balance.

**ScoreCap Calculation Formula**

The **ScoreCap** is calculated using the following formula:

<figure><img src="/files/v3SQU3tOnJxlccZWntWJ" alt=""><figcaption></figcaption></figure>

**Variable Definitions**

1. **BaseCap**:\
   The base score cap available to all users, regardless of NFT ownership.\
   Example: **20 Score**
2. **RarityMultiplier**:\
   The score increment per shoe based on its rarity:
   * Normal: **+10 Score per shoe**
   * Rare: **+20 Score per shoe**
   * Unique: **+40 Score per shoe**
   * Legendary: **+60 Score per shoe**
   * Mythic: **+120 Score per shoe**
3. **ShoesCount\_i**:\
   The number of shoes owned by the user for each rarity level.
4. **RarityMaxLimit\_i**:\
   The maximum score cap increment allowed for each rarity:
   * Normal: **Max +250 Score**
   * Rare: **Max +400 Score**
   * Unique: **Max +500 Score**
   * Legendary: **Max +500 Score**
   * Mythic: **Max +1000 Score**

### Conclusion

The ScoreCap system dynamically adjusts based on the number and rarity of NFT Shoes owned by a user. By setting maximum limits for each rarity, the system maintains balance while encouraging strategic collection and allocation of NFT Shoes. Players with higher ScoreCaps can unlock greater opportunities, emphasizing the value of acquiring and managing high-rarity NFTs.


---

# 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://docs.cryptohunter.world/tokenomics/shoes-nft/hp-and-energy-system/score-system.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.