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

# VISION & MISSION

## Our vision

Hit Zone aims to rethink the blockchain gaming:\
Bringing a simpler and faster user experience in order to make web 3.0 gaming accessible to anyone.

An easy-to-learn arcade game where everyone has the same chances to win.

## Our mission

**We want to make the crypto gaming experience simpler.** 

**Within 5 minutes, you can:**\
**- Use your tokens to enter an Arena or buy a Hit Zone NFT**\
**- Use your skills to win a game**\
**- Collect your opponent's tokens**\
**- Rank on 4 leaderboards**<br>

The quality of the game is guaranteed by the team of experts that have rallied around the idea. The HIT ZONE Team features a large number of experts from different domains – NFTs, Defi and the gaming industry. Bringing their experience and creative ideas together, the team has what it takes to launch the best PvP blockchain game.


---

# 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://hit-zone.gitbook.io/hit-zone-whitepaper/vision-and-mission.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.