# Initial Component Values

**Initial Values**\
Every item in the game store has an initial price set to ensure balanced figures, keeping the numbers simple and manageable. These prices represent the costs of purchases in the store for various game components.

**Store Item Prices**\
**Price of Cosmetics in shards**

* Common: 20
* Rare: 100
* Epic: 500
* Mythic: 2,500
* Legendary: 12,500
* Unique: 100,000

**Price of Skins in shards**

* Common: 100
* Rare: 500
* Epic: 2,500
* Mythic: 12,500
* Legendary: 62,500
* Unique: 500,000

**Price of Characters in shards**

* Common: 1,000
* Rare: 5,000
* Epic: 25,000
* Mythic: 125,000
* Legendary: 625,000
* Unique: 5,000,000

**Price of Power Ups in cores**

* Common: 50
* Rare: 125
* Epic: 312
* Mythic: 781
* Legendary: 2,000
* Unique: 5,000

**Initial Value of Currencies**

* shards: 200 shards = 1 dollar
* marks: 1,000 marks = 1 dollar
* chips: 1,000 chips = 1 dollar
* cores: 1,000 cores = 1 dollar

**Starting State**\
To establish a solid base for the algorithm, we will use an initial sample of 100 players, each playing an average of 2 hours per day. Each match lasts about 5 minutes, resulting in a total of 24 matches per player per day. The average spending in fees is estimated at twice the minimum bet, which is 200 tokens, equivalent to 20 cents. In total, the fees collected will be approximately 48 dollars per day.\
These initial values can be modified via a control panel, allowing adjustments based on real statistics collected during gameplay.


---

# 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://whitepaper-34.gitbook.io/rivalrumble/domestic-economy/initial-component-values.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.
