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

# 🟢 Equory

\- Main resource: Equorium.

The surface of Equory resembles a garden full of blooming fantasy plants and trees. There are also tall towers and "buildings" made of plants that are inherently alive and intelligent, glowing with bright lights and colored in different colors. Often their appearance is deceptive, some of these creatures are quite cunning and aggressive, they lure their victims with their beauty and then mercilessly devour them. There are many gravitational anomalies on Equori, which allow towers and islets with plants to float in the air forming "air castles" and incredible architecture.

&#x20;A notable fact: there is absolutely no water on this planet, and the sap and vapors released by the plants are toxic and deadly to almost any race living off the planet.

<figure><img src="/files/TU8NJNVUJeRBqkW9IdzK" alt=""><figcaption><p>Equory</p></figcaption></figure>

<br>

<figure><img src="/files/1XXkm8XbNf1KT3A4rirR" alt=""><figcaption></figcaption></figure>


---

# 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://mbground.gitbook.io/game/planets/equory.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.
