> For the complete documentation index, see [llms.txt](https://whitepaper.plyr.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.plyr.network/detailed_roadmap_for_2024/platform_and_game_launches.md).

# Platform and Game Launches

## Official Mainnet Launch <a href="#official-mainnet-launch" id="official-mainnet-launch"></a>

**Objective:** Transition **PLYR CHAIN** from Testnet to mainnet, marking the platform's official public launch.

**Action Plan:** Select an auspicious launch date following successful testing, coordinating a synchronized rollout of platform services, and initiating community engagement activities to maximize visibility.

## Introduction of Six Games <a href="#introduction-of-six-games" id="introduction-of-six-games"></a>

**Objective:** Launch an initial suite of six diverse games to showcase the platform's capabilities and attract a broad player base.

**Action Plan:** Collaborate with game developers to ensure their titles are optimized for the **PLYR CHAIN**, planning a staggered release schedule to maintain player interest and platform momentum.


---

# 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://whitepaper.plyr.network/detailed_roadmap_for_2024/platform_and_game_launches.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.