Last reviewed
Why build this game
The project begins with a simple ambition: make building and operating a space empire feel consequential over time. Colonies, fleets, and local sectors should remain connected parts of one history rather than disposable levels.
Achieving that ambition is a systems problem as much as a content problem. The work therefore emphasizes persistent state, readable command interfaces, tunable rules, and clear boundaries between presentation and authoritative game logic.
How development is documented
Public updates are based on visible build changes and traceable project checkpoints. They explain what changed, why it matters to players, and what remains unresolved. Internal experiments are not promoted as finished features.
The journal also preserves the evolution of the art direction, from planet classes and full-hex colony structures to the visual language of fleets and tactical sectors.
A browser-first future with an authoritative core
The current prototype runs locally in Godot, while gameplay actions are progressively being separated behind service APIs. The long-term direction is a browser-accessible client that presents the universe while an authoritative service protects accounts, saves, timers, resources, and movement.
That architecture is still under development. The public roadmap and journal remain the best sources for the project's current state.