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

# Roadmap

The tokenomics of our proprietary <mark style="color:red;">**$ROYALE token**</mark> position us to support two of the most important pillars in the roadmap of any cryptocurrency: <mark style="color:purple;">**development**</mark> (such as the addition of a battle bot within other Telegram groups) & <mark style="color:orange;">**marketing**</mark>. Our roadmap, taking into account both aspects, will initially be seperated in three blocks of two weeks. After this - our attention shifts to adding functionalities and updates to the bot (highlighted in the next chapter) maintaining a continuous stream of marketing, online and offline marketing initiatives and buybacks and burns of the <mark style="color:red;">**$ROYALE token**</mark>.\
\
💡 <mark style="color:purple;">**1-2 weeks after launch**</mark>\
🌀 Launch of Game\
🌀 Launch of $ROYALE token\
🌀 Launch of Social Media Platforms\
🌀 CMC & CG Listing\
🌀 Support ETH Waging\
🌀 Ongoing KOL Onboarding\
\
💡 <mark style="color:orange;">**3-4 weeks after launch**</mark>\
🌀 Launch of In-Group Battles\
🌀 Support Solana Waging\
🌀 Youtube Partnerships\
🌀 Ongoing KOL Onboarding\
\
💡 <mark style="color:red;">**5-6 weeks after launch**</mark>\
🌀 T2 CEX Listings\
🌀 Additional Battlefields\
🌀 Additional Token Waging Support\
🌀 Extended Fighter Profiles & Loot\
🌀 Ongoing KOL Onboarding


---

# 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://duelroyale.gitbook.io/duelroyale/roadmap.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.