# Roadmap

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

**2025 — The Foundation**

* **Formation of the Game Concept** – Laying the foundation of the core vision, lore, and gameplay pillars.
* **Art Direction & Visual Development** – Establishing the unique artistic style of the galaxy, ships, and characters.
* **Start of Game Development** – Initial production and prototyping phase begins.

**2026 — Launch & First Steps**

* **Launch of Social Media Accounts** – Opening official channels for announcements and player interaction.
* [**PulsarRift.com**](https://pulsarrift.com/) **Website Launch** – The launch of our official project portal.
* **Whitepaper Published** – Release of the official project documentation detailing the game's economy, tokenomics, and long-term vision.
* **Closed Alpha Testing** – Initial, invite-only testing phase for core gameplay systems.
* TBA
* TBA
* TBA
* TBA
* TBA
* TBA
* TBA

**The Journey Ahead**

The details of each upcoming season—including specific features, narrative arcs, and associated digital collections—will be announced closer to their release. This allows us to remain agile, incorporate community feedback, and ensure each update meaningfully expands the universe you help shape.

Our ultimate destination is the **multi-platform release** of the complete Pulsar Rift experience, bringing this strategic space RPG to a wider audience on **Steam and consoles**.

**Join us in building this galaxy, season by season.**

🚧 **This feature is in active development.**\
⚠️*Its final design at launch may differ. This page will be updated as development progresses.*<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://pulsar-rift.gitbook.io/pulsar-rift/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.