> For the complete documentation index, see [llms.txt](https://docs.undisputednoobs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.undisputednoobs.com/what-are-we-working-on/current-affairs/issues-in-play-to-earn-space.md).

# Issues In Play-To-Earn Space

## Barriers To Entry

One of the largest issues facing the Play-To-Earn space, is the cost of entry into a given game.

Whilst some games cost very little to get started, quite often, the returns are very little as well.

In order to play in some of the games that offer larger returns, a player will need to buy an NFT or game character, which is more often than not, unaffordable to most players.

## Getting Started

After finding a game a player wants to take part in, they must then learn:

* How to set up a Crypto Wallet
* How to buy their character/s
* How to start playing the game
* How to earn a return in the game
* How to cash out their earnings

Whilst the above is relatively simple, it can be daunting to new players, especially new players who are also new to the Crypto space.

## Landscape Knowledge

Another large issue with the Play-To-Earn space, is the lack of knowledge regarding how tokenomics work, and how player decisions can influence the failure or success of a game's lifespan.

The majority of gamers want to play a game and cash out immediately, which can cause a drain on liquidity and token prices, without being aware that by holding or cashing out later, they actually increase the value of their particular token, allow the game's lifespan to increase, and yield a higher return overall.


---

# 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://docs.undisputednoobs.com/what-are-we-working-on/current-affairs/issues-in-play-to-earn-space.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.
