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

# Gameplay

## Current Market

When Play2Earn games started to become something in the web3 space, they did not require much thought. Most of them were basically clickers with really poor designs. Many of them demand that the user log in frequently to carry out many repetitive operations over time. Today, we are seeing more and more interesting games, even if a lot of them are still today copies of existing games which bring no added value to the existing market, and for which the players do not use their intellectual capacities.

## Our proposal

MetaMindGames wants to bring something unique and innovative in the web3, in which people could actually use their brains to solve games, and would be paid for doing it.

Games are created from scratch by the team and are various, puzzles, riddles, enigmas, treasure hunts, escape rooms, etc...

If players are clever, they can make money without any other random factor interfering!


---

# 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:

```
GET https://metamindgames.gitbook.io/metamindgames/market-analysis/gameplay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
