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

# Game Summary

### Introduce briefly

Mechaverse is a subsidiary game-fi project of Mechaverse Labs, a Japanese Web3 entertainment platform with various forms of game like Auto Chess, Battle Royale, 3D Fighting, sandbox, conquest and UFO Catcher ,etc. Mechaverse is a Meta-Dimensional Strategy Game-Fi in The Era of Web3,with the NFT authorization of various well-known Japanese IPs.

### Story

A mysterious ascending-dimension catastrophe has invaded the earth. Silicon-based metal lifeforms from the local galaxy group have passed through the dimensional wall to invade and plunder the earth with digital and physical space successively. The mecha prototype weapons trained by artificial intelligence and neural networks for a long time have gradually developed human-like thinking and spirituality under the pressure of the crisis. Therefore, the mecha heroes assembled and a war to maintain the fate of the earth, humans and humanoid mechas was officially started. As the last alliance of human wills, we fight side by side for survival and civilization in the gap of time and space intertwined by dimensional chaos.


---

# 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.mechaverse.cc/mechaverse/game-summary.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.
