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

# 🥾Movements

**Movement in a game**

When it's player turn, player roll the Mooncircle, NFT Moon Hero will move forward on the Board. The field player stand on determines what player need to do. Several players can be on the same Block at the same time. Depending on which block players have to:

* Buy this site or install aviaries on it.
* Pay the fee for a stop in the block belonging to another player
* Pay for the purchase of a scam coin or a high transaction fee
* Pull out a High Volatility card or Bear/Bull Market card
* Liquidate
* Lock in Fiat and sleep well

Passage of the field "AIRDROP"

Whenever player stop or walk through the AIRDROP field, the player receives 10% of the amount the he or she spent on the round.


---

# 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.moonpoly.io/gameplay-1/game-rules/movements.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.