> For the complete documentation index, see [llms.txt](https://docs.civitia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.civitia.org/operations/bots-and-fair-play.md).

# Bots and fair play

Civitia's game mechanics are designed to let players create and explore their own strategies, and that’s what makes Civitia exciting. Different players, different approaches, all coexisting in one space.\
\
At the same time, the game should remain fair for everyone. It’s a delicate balance, and that’s why the Civitia team actively monitors for harmful behavior and takes action when needed, always making sure it doesn’t negatively affect the game dynamics.\
\
Automating strategies, like using bots, or playing with multiple wallets isn’t banned by default. But if these actions harm the game mechanics or other players’ experiences, Civitia reserves the right to take the necessary measures to protect the community.\
\
We encourage all players to get creative, build their own strategies and compete, always with fairness in mind and respect for the rest of the community.


---

# 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.civitia.org/operations/bots-and-fair-play.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.
