A life aboard.
A galaxy ahead.

Build a place in the galaxy.

The intended Grevara loop connects construction, travel, command, exploration, and recovery. You build a ship that suits your purpose, take it into space, delegate to its crew, and respond when the world changes what that ship needs to do.

The aim is continuity between those activities. The ship you construct is the ship you fly. The interior is where its crew works. Damage should matter to its systems. Repair should leave you with a ship that can continue its journey rather than resetting the situation into an unrelated activity.

Block by block.
Purpose by purpose.

Modular shipbuilding is a central part of the vision. The goal is to construct ships block by block, including interiors, so creating a vessel involves more than selecting an exterior silhouette.

A ship’s space should support the experience aboard it. The wider design connects physical construction to utilities, access, damage, and repair. These interactions are the reason to care about where components and rooms belong.

The next integrated game slice aims to bring ship construction into one explorable system alongside basic AI ships. That integrated construction-and-flight loop is still ahead of the current Captain engineering prototype.

A 3D sandbox you can inhabit.

First-person and third-person ship flight are planned parts of Grevara. The world is fully 3D, with the ship acting as the link between personal-scale activity and the wider space sandbox.

Flight is meant to sit within the same world as construction and crew command. The larger ambition includes space warfare and fleets, so the ship’s condition and the decisions made aboard it should matter beyond the interior.

Detailed flight handling, control mappings, combat balance, and public hardware requirements have not been announced here. The current native verification work is a development gate, not a final compatibility promise.

Lead through delegation.

The crew vision gives people aboard the ship jobs, memory, learning, and relationships. Delegation is intended to let the player command through people whose relevant experience carries forward.

That makes command different from a set of anonymous buttons. A request belongs to a crew member, an outcome becomes part of the ongoing state, and the Captain prototype is used to investigate whether that continuity remains reliable when the simulation is saved and restored.

Current relationship learning is bounded to evidence-backed repair outcomes. The broader social simulation is not established as a complete game.

A destination beyond the hull.

The longer-term universe combines an enormous procedural galaxy with handcrafted content. Scale provides room to travel; authored discoveries, mysteries, and history provide reasons to look closely.

Living economies and factions are part of the vision for that world. Space warfare and fleet command widen the possible consequences of what the player builds and where they choose to go. These systems are longer-term ambitions, not currently available modes.

The near-term slice deliberately begins with one explorable system. It needs to prove navigation, discovery, construction, interaction with basic AI ships, and meaningful return before the project expands its scope.

The return trip matters.

An interruption should not erase the meaning of what happened. That principle appears at several scales: memory for a crew member, restoration of a prototype checkpoint, and ultimately persistence for a whole ship in its world.

The immediate integration target is a ship emergency that connects damage to utilities, uses finite parts for crew repairs, and retains the outcome. The broader acceptance goal is to leave and revisit the ship without losing its state or the authority of the systems that define it.

Prototype checkpoint restoration is already implemented and software-tested. Whole-ship continuity across the full interconnected game loop remains a separate development task.