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

# Gameplay

![](/files/-MjphPwXkyZS5ZzXdUAn)

DCHESS gives a new dimension to an already established game. It is not about modifying Chess, it is about allowing the player to venture into duels with opponents from all over the world, with the premise of winning Tokens (called KING) per game won. DCHESS is an invitation to test your skills in a competitive environment, and without the need to invest any initial money, this means that playing for free you will be able to generate income. We are convinced that what determines a Champion is not only his diamond-encrusted board, but also his skill... But how nice and profitable it would be to have it! Of course, if you decide to invest in improving your board, your earnings will see an exponential and surprising growth.


---

# 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://teamdchess.gitbook.io/dchess/english-1/dchess-game/gameplay.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.
