# 8.2 Milestones and Timelines

*Please note: Dates are subject to change and may be delayed or delivered faster. This is based around a full funded project to give a realistic timeline of delivery*

### **Concept Phase (Q3 2024 - Q4 2024)**

* Q3 2024: Define the game concept and initial token economy design.
* Q3 2024: Conduct market research and feasibility studies.
* Q4 2024: Assemble the core development team.

### **Pre-Production Phase (Q1 2025 - Q2 2025)**

* Q1 2025: Create Game Design Document (GDD) and Technical Design Document (TDD).
* Q1 2025: Develop and test the initial game prototype.
* Q1 2025: Finalize the detailed token economy and smart contract development.
* Q2 2025: Launch the pre-sale of SugarCane.
* Q2 2025: Start community engagement and marketing campaigns.
* Q2 2025: Conduct the public sale of SugarCane.

### **Production Phase (Q3 2025 - Q2 2026)**

* Q3 2025: Begin full game development, focusing on asset creation and gameplay programming.
* Q4 2025: Integrate Solana blockchain for asset management and transactions.
* Q1 2026: Develop and test multiplayer features.

### **Key Milestones Starting from Q3 2026**

* **Q3 2026:**
  * Conduct internal testing and comprehensive security audits of smart contracts and blockchain integration.
  * Begin initial closed beta testing with a select group of players to gather feedback.
* **Q3 2026:**
  * Continue closed beta testing, focusing on refining gameplay based on player feedback.
  * Implement necessary adjustments and fixes identified during the beta phase.
* **Q4 2026:**
  * Finalize multiplayer features and ensure seamless integration with Solana blockchain for asset management and transactions.
  * Prepare for broader beta testing to include a larger player base.
* **Q4 2026:**
  * Launch an open beta to gather broader feedback from the community.
  * Begin final marketing preparations and campaigns to build anticipation for the launch.
* **Q4 2026:**
  * Implement feedback from the open beta.
  * Conduct further testing and optimizations.
  * Prepare for the final marketing push and optimize the game for launch.

### **Launch Phase (Q1 2027)**

* **Q1 2027:** Finalise polish and performance optimizations.
* **Q1 2027:** Execute the final marketing campaign.
* **Q1 2027:** Official release of Candyland Carnage to the public.
* **Q2 2027:** Provide immediate support for launch issues and monitor game performance.

### **Post-Launch Phase (Q2 2027 - Ongoing)**

* **Q2 2027:** Release the first major update with new content and bug fixes.
* **Q2 2027:** Implement the first seasonal event and special competitions.
* **Q3 2027:** Introduce player governance features, allowing players to vote on game updates and changes.
* **Q4 2027:** Expand the game with additional quests, items, and features.
* **Q4 2027:** Launch the second major update, including new storylines and gameplay mechanics.

### **Future Updates (2028 and Beyond)**

* **Q1 2028:** Continuously release regular updates and new content based on community feedback.
* **Q2 2028:** Enhance cross-platform interoperability, allowing SugarCane and in-game assets to be used in other games and platforms.
* **Q3 2028:** Organize large-scale community events and eSports tournaments.
* **Q4 2028:** Further evolve the token economy and governance models to adapt to the growing player base and ensure long-term sustainability.

This timeline outlines the major milestones from the initial concept phase to the ongoing post-launch updates for Candyland Carnage. By adhering to this timeline, we aim to deliver a well-developed, engaging, and dynamic Web3 MMORPG that continuously evolves with its community.

\ <br>


---

# Agent Instructions: 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:

```
GET https://whitepaper.candylandcarnage.com/8.-development-roadmap/8.2-milestones-and-timelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.