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

# PLAY SYSTEM

In the early phase of this game we will create a 2D game that can be interacted. After that, we'll create 3D gameplay. The 3D gameplay we dreamed of was an MMORPG game that could be integrated with blockchain. You can play with friends and adventure in this boundless world. That's our main vision, we really want to make our world and we're going to be serious about making it.

{% hint style="info" %}
***For gameplay, each samurai can only use 1 tool, if you want to replace the tools it takes time until the tools are damaged or replace them by durability of these tools.***
{% 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://samuraiworld-whitepaper.gitbook.io/samuraiworld-whitepaper/information/play-system.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.