> For the complete documentation index, see [llms.txt](https://faq.rollercoin.com/rollercoin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.rollercoin.com/rollercoin/f.a.q./storage/2.-where-can-i-get-the-parts.md).

# 2. Where can I get the Parts?

There are several ways to obtain parts:

1. As a reward for playing mini-games. Please note that this is a random reward with a certain chance of dropping. Therefore, it is not guaranteed that you will receive a specific number of parts per a certain number of games won.
2. Open “Common parts” loot boxes at the [<mark style="color:green;">Season Store</mark>](https://rollercoin.com/game/market/season-store).
3. Simply buy them on [<mark style="color:green;">the Marketplace</mark>](https://rollercoin.com/marketplace/buy) from other users.
4. More rare parts can also be obtained via merge.
5. Buy them with Bundles, when they are active.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faq.rollercoin.com/rollercoin/f.a.q./storage/2.-where-can-i-get-the-parts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
