Maple Engine
The foundation
under Grevara.
A custom C++ and Willow runtime developed alongside a demanding game vision. The next challenge is to connect substantial foundations into one coherent experience.
Where the world runs.
Maple Engine is Casilian’s custom C++ and Willow engine, developed alongside Grevara. Its responsibility is the running experience: the foundation in which a world is presented, simulated, interacted with, and continued.
A runtime has a different job from a modeling or animation application. Foundry, Soar, Design, and Morph define creative and preparation roles; Engine is the destination in which the game uses its assets and systems.
Grevara gives that work a concrete purpose. Ships, crew, utilities, damage, memory, and persistence create a demanding integration problem that cannot be solved by treating every subsystem as a separate demonstration.
A substantial base
to connect.
Existing engine work includes geometry and scenes, rendering, audio, gas and power systems, utility checkpoint ownership, dependency and item primitives, physics and destruction, and Willow integration. These foundations are part of the current development base.
Native editor work also includes detached windows and an in-process debugger. Those capabilities should not be confused with the separate Foundry modeling application.
An implemented subsystem is a foundation, not a claim that all interactions around it are complete. The immediate game task is to connect existing systems into an engineering emergency with finite-resource repair and coherent persistence.
The custom
technology stack.
C++ and Willow are part of Maple Engine’s own technology stack. Willow integration sits alongside the engine foundations and is part of the work used to develop Grevara’s connected experience.
This site does not publish a scripting API, language compatibility reference, or public SDK. It introduces the technology and its responsibilities without implying that an external developer platform is already available.
As the project progresses, authoring interfaces and compatibility will need their own documentation and acceptance. The current focus remains the engine and game foundations rather than a public tooling release.
Saving the right things
for the right reason.
Persistence is not one undifferentiated feature. The Captain prototype restores simulation and command state together; utility checkpoints own a narrower subsystem scope; geometry archives retain authored or generated scene geometry.
Those paths have different boundaries. A geometry archive does not by itself retain all live physical state, pending work, crew orders, resources, or regional authority. A utility checkpoint does not automatically cover the whole game.
The larger goal is whole-ship continuity at a coherent authoritative boundary. A ship should be able to survive a cold restart or a leave-and-return cycle without duplicated resources, lost repairs, or a disconnected crew history.
Scale with
clear authority.
Grevara’s seven simulation/detail levels are the finished design target. The current Captain prototype provides five existing host tiers and bounded Full/Reduced presentation behavior. The final regional and whole-world system is still in development.
Lower-end hardware is an ambition that informs reduced-cost work. Correctness tests and scene benchmarks support particular paths; they do not establish final whole-frame gameplay performance or compatibility for every machine.
Native platform acceptance, real device behavior, rendering, sustained operation, and representative performance remain distinct from passing a software test suite.
Read the technology and performance boundariesProgress with
specific evidence.
Recent software-tested work has advanced player checkpoints, bounded relationship learning, CPU shadows, audio handling, fracture safety, and geometry persistence. Native physics-backend tests have also progressed.
Current Windows input, real audible playback, native GUI, and Vulkan/GPU rendering still need direct acceptance. Locally validated work is not presented here as a public downloadable release.
No public Engine download, SDK, price, licensing program, or release date is announced on this site. For the dated game integration plan, see Grevara’s development snapshot.
Read Where We AreStart a conversation
Ideas deserve a conversation.
Talk to Casilian Studios.
Questions about Maple Engine, collaboration, or the work behind it? Contact the studio directly.