> For the complete documentation index, see [llms.txt](https://docs.openbisea.com/motodex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbisea.com/motodex/motodex-overview/gameplay.md).

# Gameplay

### <mark style="color:red;">Important Nuances for Victory</mark>

The gameplay divides users into two camps:

1. Track owners - NFT locations where competitions are held. Depending on the level, the tracks may differ in length, appearance of the location, and the minimum bet threshold.
2. Owners of NFT characters who fight bots in the game and compete with each other.

Both in motoDEX will have to develop their facilities and earn on their subsequent operation. Players interact with each other through the following mechanics:

* The owner of the track gives other users of the game access to his obstacle course. To participate in competitions on someone else's NFT object, players need to place a bet. The start bet threshold is set by the owner of the track.
* The minimum bet size directly depends on the level of the track.
* The game on the track starts after the user decides on the game location and makes a bet.
* The presence of an NFT character is a prerequisite to start playing on the track.
* The task of the gameplay is to keep your character safe and sound, to get ahead of other real players on the track and break old records.
* Game achievements are recorded in the corresponding smart contract and allow track owners and players to receive bonuses and rewards.
* Along with real players in each game session, there are pest bots on the track.


---

# 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.openbisea.com/motodex/motodex-overview/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.