A playable preview is useful, but ownership matters more. Oryn writes scenes, scripts, assets, and project settings into a normal Godot project so the result can outlive a single generation session.

The alternative we did not build

The easier product is a custom runtime: a bespoke scene format, an interpreter that only we ship, and a preview that only runs on our infrastructure. It is easier because you control every layer, and it demos beautifully.

It also means the game only exists as long as the company does. Every hour a creator puts into a project is an hour invested in a format they cannot open anywhere else. That tradeoff is invisible on day one and total on the day it matters.

What choosing a real engine costs

Godot has opinions, and generated code has to respect them. Node lifecycles, the scene tree, the input map, resource importing, and export presets are all real constraints that a bespoke runtime would let us define away.

• Generated code has to be idiomatic enough that a human can pick it up mid-project.
• Assets have to import cleanly rather than being loaded through a custom path.
• Project settings and input maps have to be written correctly, not simulated.
• The web preview is a genuine export, which makes it slower than rendering our own format would be.

What it buys

The structure that makes iteration safe is the same structure that makes the project portable. Every change can be built, inspected, versioned, and continued manually when a developer wants deeper control — and "continued manually" means in Godot, on their machine, with no part of Oryn involved.

That is the version of AI game development worth building: the AI is an accelerant on a project you own, not a dependency the project cannot survive.