> For the complete documentation index, see [llms.txt](https://wiki.yami-ro.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.yami-ro.net/server-features/play-to-earn.md).

# Play To Earn

<figure><img src="https://917350178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FW66JuCfjIqobrujST6BX%2Fuploads%2FiX23Eg2tNMB6FtYbBiqE%2Fimg-075.png?alt=media" alt=""><figcaption><p>P2E Coin</p></figcaption></figure>

## How to get P2E Coins?

* Killing MvPs on their respective locations ( 30% on Rare MVPs and 20% of Normal MVPs )
* Endless Tower Instances ( 50% Chance )
* Administrator Hosted Events.
* Streamer's Reward.

## ***How do we convert our P2E Coins?***

* You may only convert your P2E to GCash TWICE a month, with 15 days cooldown.
* Minimum and Maximum of 1000 Cash Coins for conversion.
* Administrators will be deducting 20% Cash Coins on Conversion
* You can also cash in your P2E Coins into Donation Tickets, without any conversion Fee.

{% hint style="warning" %}
P2E Coin is currently unavailable for trading between players. Kindly wait for futher notice.
{% endhint %}

{% hint style="danger" %}
Having Play to Earn in our system doesn't mean we approve of RMT, under-the-table transactions are PROHIBITED.
{% endhint %}


---

# 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://wiki.yami-ro.net/server-features/play-to-earn.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.