> For the complete documentation index, see [llms.txt](https://docs.playhighlands.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playhighlands.net/about-highlands/roadmap.md). # ROADMAP ## Q1 * [x] Website Launch * [x] Game Launch * [ ] Token Launch on Pump.fun * [ ] Dexscreener Payment * [ ] 500 Holders ## Q2 * [ ] Dexscreener Boost * [ ] NFT collection launch with rare, epic, and common tiers to increase Grow Power * [ ] Major game updates with many new features * [ ] Marketing and influencer partnerships * [ ] New seed bank and rare seed drops * [ ] 1000 holders ## Q3 * [ ] Dexscreener Ads * [ ] Decscreener Boost * [ ] New game updates including weapons and additional mechanics * [ ] CoinMarketCap listing * [ ] CoinGecko listing * [ ] 3000 holders ## Q4 * [ ] Mobile version available on App Store and Play Store * [ ] Listing on Epic Games or Steam * [ ] Listings on multiple exchanges * [ ] Token burning * [ ] 5000 holders ## Q5 * [ ] Highlands merchandise * [ ] Launch of our own blunt and rolling brand * [ ] Partnerships with major influencers and structured marketing programs * [ ] Giveaways for $HIGH holders and players * [ ] Token burning * [ ] 10,000+ holders --- # 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://docs.playhighlands.net/about-highlands/roadmap.md?ask=&goal= ``` `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.