# Game Design and Philosophy

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

Dear Players,

Our studio has been creating and successfully launching games for over four years. **Pulsar Rift** is our most ambitious and promising project to date. It represents the culmination of all our ideas and core design philosophies, amplified by the hard-earned experience from our previous endeavors.

**Pulsar Rift is a Space Strategy RPG where you will command your own starship, chart unknown planetary systems, harvest and trade rare resources, craft powerful devices, and engage in both real-time space combat and tactical turn-based battles.**

Our roadmap begins with the **Web3 version**, where we will steadily expand the universe with each new season, introducing major gameplay mechanics and narrative chapters. Upon the full implementation of the final core system—the **turn-based card battler**—**Pulsar Rift** will evolve into its complete, traditional form, launching on **Steam and major console platforms** as a dynamic, feature-rich experience.

We are thrilled to welcome you to our growing community. Our primary mission is to deliver the profound sense of adventure, discovery, and mastery that every gamer seeks. Join us on this incredible journey to the stars.

**Let's conquer the boundless cosmos together.**

<p align="center"><a href="https://discord.gg/U5X3fdB6TS" class="button secondary" data-icon="discord">Discord Community</a></p>


---

# 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/game-design-and-philosophy.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.
