Technology & performance
Scale the world.
Keep the meaning.
Maple provides the foundation. Layered detail is the design direction. The challenge is to preserve coherent state while making a larger experience practical.
Built on Maple.
Grevara is being developed on Maple Engine, Casilian’s custom C++ and Willow foundation. Developing an engine alongside the game gives the technology a concrete setting in which its connected systems can be exercised.
Existing engine work includes scene and geometry foundations, utilities, physics and destruction primitives, rendering, audio, editor tools, and Willow integration. Their presence supports development, while cross-system integration and native acceptance remain separate responsibilities.
The creative suite also defines tools for modeling, animation, sprites, and supported conversion. Their intended workflow complements the runtime rather than making them interchangeable applications.
Explore Maple EngineSpend detail where
it matters.
The design aims to vary simulation and presentation detail with context. A large world should not require every region, object, and character to run at the same fidelity at all times.
Seven simulation/detail levels are the finished target. The Captain prototype currently has five existing host tiers and bounded Full/Reduced presentation work. The seven-level product design is not yet a finished whole-world system.
Current relevance work promotes and reduces presentation in a bounded way within the prototype. That does not establish whole-ship regional authority or prove final galaxy-scale performance.
Lower-end hardware
is a goal, not a guarantee.
A range of hardware, including lower-end machines, is part of Grevara’s design ambition. That goal informs layered detail and reduced-cost presentation, but it is not a published minimum specification.
Software tests can show correctness in a particular configuration. They do not establish real gameplay frame rate, GPU behavior, device compatibility, or the experience on every machine.
Windows and Steam are planned. No final hardware requirements, release date, or supported-device matrix is announced here.
Scalability still
needs continuity.
Changing the amount of detail should not change what is true about the world. The broader design needs clear authority over the ship, its crew, its work, and the systems that remain relevant while the player is elsewhere.
Current checkpoint controls preserve paired simulation and command state in the Captain prototype. Engine utility checkpoints and geometry save/load have their own narrower responsibilities.
Whole-ship leave-and-revisit continuity remains an integration task. It needs those responsibilities to agree, rather than assuming that one successful save path covers the entire game.
Room to shape
the experience.
Modding is part of Grevara’s longer-term vision. The intention is to leave room for players and creators to extend the experience once the necessary foundations and interfaces exist.
Specific modding APIs, file formats, distribution arrangements, compatibility promises, and release timing have not been announced. The Maple family’s intended asset pipeline should not be read as a completed public modding toolkit.
The current focus remains the single-player foundation and a coherent integrated slice. Multiplayer is a later goal.
Read the grounded development snapshotStart a conversation
Ideas deserve a conversation.
Talk to Casilian Studios.
Questions about Grevara’s technology, collaboration, or the work behind it? Contact the studio directly.