# Product Roadmap

#### 🛠️ **Phase 1: Fuddles 2D Running Track – Building Phase**

* Core development of Fuddles' 2D competitive runner game.
* Includes level design, obstacle mechanics, UI/UX setup, and $SOL / $USDC ticketing integration.
* Foundation for future competitions and leaderboard-driven gameplay experiences.

***

#### 🎮 **Phase 2: Fixelz Adventures – Game Development Phase**

* During this phase, the team will design and develop core gameplay systems such as skill-based creature capturing mechanics, logical mini-games, and the adventure-RPG style progression.
* Three major biomes (Normal Region, Underworld, and Skyhaven) will be built, each with distinct visuals, Fixelz species, and gameplay challenges.
* Farming systems, trading mechanics, and strategic resource management will be implemented to deepen the game loop.
* World-building, character lore, and story-driven quests will be crafted to deliver a rich narrative experience.
* Technical preparation for cross-platform deployment (PC, mobile, consoles)

<figure><img src="/files/Tla9QDNqW0FsnUqlfyeQ" alt=""><figcaption></figcaption></figure>

***

#### 🎯 **Phase 3: Fuddles Running Track (2D) – Building Phase**

* A fast-paced side-scrolling game focused on dodging, jumping, and hitting milestones.
* Designed for quick competitive runs and tournament-style play-2-earn.
* Core experience for casual and speed-focused gamers.
* Includes integration of $SOL / $USDC ticketing system for entry.

***

#### 🎲 **Phase 4: Fuddles Jump Track (2D) – Building Phase**

* Reflex-driven vertical platformer that challenges players to reach new heights.
* Great for leaderboard competitions and short-session gaming.
* Includes integration of $SOL / $USDC ticketing system for entry.

***

#### 🕊️ **Phase 5: Fuddles Flappy Track (2D) – Building Phase**

* Fuddles-themed flappy-style game with unique visuals and scoring mechanics.
* Designed as a community-friendly play-2-earn competive game with leaderboard.
* Includes integration of $SOL / $USDC ticketing system for entry.

***

#### 🏁 **Phase 6: Fuddles Play-2-Earn Competitions**

* Launch of official game competitions across Fuddles games (Running, Jump, Flappy).
* Players will purchase tickets with **$SOL or $USDC** to enter matches.

***

#### 🧍‍♂️ **Phase 7: Fuddles 3D Characters Integration**

* High-quality 3D avatars of 1/1 Fuddles characters introduced into the Fuddles Studio metasystem.

***

#### 🚀 **Phase 8: Fixelz Adventures – Game Release**

* Official release of Fixelz Adventures across **PC (Steam, Epic Games), Android, iOS, and consoles**.
* Players explore diverse regions, complete quests, farm resources, and collect rare Fixelz through skill-based challenges.
* Offers a story-rich experience with long-term progression, trading systems, and high replayability.

<figure><img src="/files/ThkDflrfXf9QHpp8Up4x" alt=""><figcaption></figcaption></figure>

***

#### 🛍️ **Phase 9: Fuddles Merchandise Shop**

* Online storefront where users can buy Fuddles-themed clothing, collectibles, and gaming gear.
* $SOL & $USDC accepted as a payment method, adding real-world utility.
* Supports community branding and long-term ecosystem funding.

***

#### 🎙️ **Phase 10: Fuddles Vtuber Studio Services**

* Studio services to create custom Vtuber avatars for streamers and creators.
* Fuddles-style assets, motion capture support, and onboarding guidance included.

***

#### 🧠 **Phase 11: Fuddles Studio P2E & Spaces Services**

* P2E or Spaces game creation services for external projects, powered by Fuddles Studio’s expertise.


---

# 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://fuddles.gitbook.io/fuddlesstudiowhitepaper/about/product-roadmap.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.
