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

# Cuboids

### Origin

Long ago, before the realization of the Metaverse, Cuboids lived secret and peaceful lives. The Cuboids species had many different looks that reflected their environments. Some even reflected a mix of those environments.

* <mark style="color:blue;">**BEASTS**</mark> could be found throughout nature, appreciating their surroundings.
* <mark style="color:blue;">**SOULS**</mark> could be anywhere and everywhere, especially if you could feel the cold chill of their nearby presence.
* <mark style="color:blue;">**MECHAS**</mark> were the impression of the future and what was to come.
* <mark style="color:blue;">**TROGOS**</mark> were the underground dwellers, tasked with guarding the treasures of the realm.
* <mark style="color:blue;">**DRAGOIDS**</mark> the keepers of the Realm, could rarely be seen as they soared high above everything.
* <mark style="color:blue;">**HEX**</mark> were the mystery, not much is known about them and their involvement.

### The Lore

Beasts were ancient to the realm, and they were respected for their might and wisdom. The other Cuboids trusted them to be their leaders and maintain order throughout the realm. However, Mechas considered themselves a superior species because of their intelligence and wanted to challenge the Beasts.

When humanity discovered the Metaverse, panic started to creep through all of the Cuboids.

Debates spread throughout the species, which caused a great divide. Beasts formed clans for protection from what may come. Souls seemed to become more scarce, when actually they preferred to watch without being seen by the naked eye, haunting those that tried to invade their space. Trogos became more cautious about their treasure, fearing that the chaos in the realm would draw attention to it, So they fortified themselves. However, Mechas saw the arrival of humanity as an opportunity for power. The Mechas assembled an army and began an attack upon their fellow Cuboid species, wanting their fellow Cuboids to fall in line to help conquer the vast Metaverse. War broke out and nearly drove the Cuboids to extinction.&#x20;

Not all Cuboids fought in the great war, small communities were formed and allowed the Cuboid species to live on. Today, each Cuboid carries one or more traits from another subspecies. It is even possible to find Cuboids with qualities from multiple subspecies.&#x20;

Now, with only so many Cuboids left, they are scattered and lost without guidance. Some Cuboids may just need a friend, others may be looking for a tribe, and the rest may be looking for the proper army to join.

{% hint style="info" %}
But little did the Cuboids know that the CubeVerse around them had continued to expand and their fighting and battles had been noticed by the rest of the cube creatures that had settled in the CubeVerse on neighboring cube planets.

\#wenfirstcontact
{% endhint %}


---

# 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://cubepaper.gitbook.io/cubepaper/gameplay/cuboids.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.