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

# Roadmap

1. **Pre-Production (COMPLETED)**
   1. Finalize game concept, mechanics, and world building
   2. Initiate design of card assets, animations and other game assets
   3. Launch website to gather community interest
   4. Create whitepaper to outline the game’s vision and blockchain integration<br>

2. **Private Sale (COMPLETED)**
   1. Kickstart the private sale to secure funds for development.
   2. Activate community channels, through Discord and social media, to build a following and gather input<br>

3. **Vertical Slice Development (IN PROGRESS)**

   1. Commence prototype development focusing on core gameplay and card mechanics.
   2. Conduct closed feedback sessions to refine gameplay mechanics
   3. Balance card interactions and unique mechanics for an engaging play experience

4. **Marketing Preparations & Public Sale (IN PROGRESS)**

   1. Marketing & PR: Increase visibility of the game through various channels
   2. Public Sale Announcements: Terms, token, and staking details for early participants revealed.

5. **Alpha Development**
   1. Develop and iterate the alpha version of the game
   2. Involve early investors in alpha testing to refine gameplay and ensure quality<br>

6. **Beta Development**
   1. Roll out fully playable beta version for extensive user testing
   2. Focus on balancing, bug fixes, and community feedback to finalize the game
   3. Increase visibility of the game through various marketing channels<br>

7. **Game Launch & Post-Launch**
   1. Officially launch “Honor VS Madness” to the public
   2. Implement continuous improvements, expansions, and new features
   3. Engage with the community for ongoing feedback


---

# 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://honor-vs-madness.gitbook.io/whitepaper/honor-vs-madness/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.