> For the complete documentation index, see [llms.txt](https://wiki.metados.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.metados.com/intro/overview.md).

# MetaDOS Overview

The world's first Time-as-Currency battle royale game.

Welcome TimeKeeper! Here you'll find some useful information about MetaDOS, the free-to-play Battle Royale game that combines fast-paced gameplay and the Time-as-Currency concept.

Whether you're a seasoned esports competitor or a novice player, our wiki is the ultimate resource for diving into the game's economy and gaining valuable insights from our vibrant community.

<div data-full-width="false"><figure><img src="https://3774778010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5xTCYuHdg4f7T6ZNSjS6%2Fuploads%2FdfvjHxxocDvoiRE79Dmw%2Fkeyart_illustration_FHD.jpg?alt=media&#x26;token=9f80de34-0ca5-4ff7-af9c-201b57666d13" alt=""><figcaption></figcaption></figure></div>

## Our Story

We developed the first mobile shooting game, [Captain Strike](https://www.youtube.com/watch?v=EO2sD9PYmZE), 12 years ago and had the first 1M users within 2 months. The game was inspired by Counter Strike, and we wanted to bring the amazing team-deathmatch experience to mobile devices. It was a huge success for us with a lot of experience and lessons. The players were so loyal that they are still requesting us to bring the game back until now.

Five years later, in 2017, we develop [Bullet Strike](https://www.youtube.com/watch?v=weYKGSl5fPg), one of the world's first mobile battle royale games (before Free Fire or PUBG Mobile). We received a lot of attractions in the alpha version with almost 10,000+ CCU and the game was featured on many news sites. Unfortunately, we were an indie developer and were not backed by Garena or Tencent. During that period, our approach to financial and technological aspects was inadequate, prompting us to transition our gaming model to a more casual style.

In both of our shooting games, the players lost everything they had earned when the games closed. With MetaDOS, we are building our most ambitious Battle Royale yet - a game where Time itself is the currency, built around fair, skill-based competition and a healthy game economy that will last for years to come.

## A Better Gaming Experience

<figure><img src="https://3774778010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5xTCYuHdg4f7T6ZNSjS6%2Fuploads%2FSlY2Aqng5NK1cCBy1voU%2FWeb3%20Gaming%20Experience.png?alt=media&#x26;token=76fb223e-6ca7-486a-bd60-f0ac9a92dd1f" alt=""><figcaption></figcaption></figure>

We're here to create an amazing set of MetaDOS gaming experiences with the community as one of the foundational pillars. But we don't do that by sacrificing player gaming experience. Using the battle-tested economy and gameplay design of MetaDOS, we aim to solve the main issues in modern free-to-play gaming:

* The inflation of game economies and unbalanced progression
* The poor onboarding process that negatively impacts new players
* Low quality and fun. Players only play out of habit, not for enjoyment.

Our approaches and solutions will be detailed in the next sections of this wiki.


---

# 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://wiki.metados.com/intro/overview.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.