Crew, memory & command
A crew that carries
the journey forward.
The ambition is a ship populated by people whose relevant experience, work, and relationships have continuity. The Captain prototype is where those foundations are being tested.
People who are part
of the ship’s history.
Grevara’s NPC vision centers on non-LLM memory, learning, relationships, jobs, and delegation. The purpose is continuity: people aboard the ship should carry relevant experience into later situations.
A crew is intended to connect the player’s command decisions to the ship’s ongoing life. Instead of every job being an isolated interaction, an assignment and its outcome can become part of what the simulation remembers.
This is a wider design than the current prototype. The Captain Who Remembers engineering scenario provides a bounded place to test the mechanisms before expanding them across a full game.
An event can outlast
the moment.
Memory supports the idea that a crew member’s relevant experience matters later. In the prototype, memory and persisted continuation are part of the established foundation, alongside delegation and a crew of 30.
Continuity has to survive more than a normal running session. Save and restore must preserve the simulation and command state together, so the restored experience reflects the same history rather than a disconnected copy of the visible scene.
Current player checkpoint controls have been implemented and software-tested. Actual Windows key and device behavior still needs native acceptance for the current changes.
Learning grounded
in an outcome.
Recent Captain work connects accepted repair outcomes to trust and respect. Contributions are tied to evidence, with mechanisms to avoid duplicate learning and preserve the result across saved state.
That is a specific bounded capability. It does not establish the whole proposed career, institution, morale, or policy simulation, and it should not be read as a claim that every interaction can produce unrestricted social learning.
The design value is that command can connect to consequences the simulation can account for. The next integration work must make those consequences clear within an actual ship emergency and recovery loop.
Command through
the people aboard.
Jobs and delegation connect the Captain’s intent to work performed by the crew. They are part of both the broader game vision and the current command prototype.
The full ship-life loop requires more than issuing an order. The work must fit the ship’s damage and utility state, respect available parts, and leave behind a result that persists.
The immediate development target is to make a bounded engineering emergency coherent from end to end. Richer social behavior and broader command scenarios can then build on a loop whose ownership and outcomes are understood.
A voice for
the people aboard.
MDV is the supporting voice component associated with Grevara’s character systems. Its role is to connect the crew experience to voice presentation alongside Maple Engine.
Audio work currently includes software-tested scheduling, cancellation, bounded retry, and cleanup behavior. These checks improve reliability within the tested path; they do not certify real audible output on every device.
Windows speech and audio playback still need native verification. No public voice catalog, voice-cloning service, or finished MDV product is announced here.
Captain Who Remembers.
The current engineering prototype brings together 30 crew members, five existing host tiers, memory, delegation, persisted continuation, and bounded learned repair outcomes. It provides a focused environment for validating command and continuity.
Recent work has also advanced Full and Reduced presentation behavior, relevance transitions, CPU shadows, and audio reliability. These are pieces of making the prototype dependable; they are not evidence that the full galaxy or final performance target is complete.
The remaining gates include native input, real audible playback, Vulkan rendering, and cross-system gameplay integration. The public roadmap identifies those separately.
Read the current development snapshotStart a conversation
Ideas deserve a conversation.
Talk to Casilian Studios.
Questions about Grevara’s crew and command systems, collaboration, or the work behind it? Contact the studio directly.