> For the complete documentation index, see [llms.txt](https://avania.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avania.gitbook.io/whitepaper/problem-and-solution/click-to-earn.md). # Click to Earn ### Problem There are many types of games. But lots of the blockchain games in the market in 2021 introduce gameplay with very low interaction. Many of them are called "Click to Earn". Click to Earn games can be good examples of the type of game that attracts players by its income intensive rather than entertainment service. ### Solution We introduce easy-to-understand gameplay, but yet have a high depth to master. In our game, players can interact with our game and have fun unlike 'click to earn' games that have less interaction. We also have integrated many mechanics to the game such as element attribute, Aether card, AOE (Area of Effect), ETC. It makes sure that players have things to discover. --- # 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://avania.gitbook.io/whitepaper/problem-and-solution/click-to-earn.md?ask=&goal= ``` `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.