> For the complete documentation index, see [llms.txt](https://contact-63.gitbook.io/cebg-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://contact-63.gitbook.io/cebg-whitepaper/gameplay/free-to-play.md).

# Free To Play

Players are allowed to try the game. Once they finish the registration process. They'll get a free hero (not NFT) . With that, they'll be able to play the game but cannot trade their gears only if they pay to convert to NFT. 

{% hint style="info" %}
Offering free-to-play options is a crucial component for driving sustained growth among Couner Fire players and increasing the overall value of assets within the ecosystem.
{% endhint %}

All free-to-play game players can be matched with paying players. 

Free players can earn Crystals through valid in-game actions, such as defeating opponents, and then convert them into CEC through the hashing power system.


---

# 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://contact-63.gitbook.io/cebg-whitepaper/gameplay/free-to-play.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.