Guides
Build with a smaller loop.
Short, practical workflows for moving from an idea to a playable Godot project without losing control of the details. Read them in order, or jump to the one you need.
Build your first playable
What to ask for in the first message, what Oryn does with it, and how to tell whether the result is a good foundation to keep building on.
ReadWrite a brief that produces a coherent game
Six things worth being specific about, why constraints beat feature lists, and how to describe a look without naming a game you cannot copy.
ReadAnswer the planning questions, then approve the plan
The two checkpoints before any file is written, why the second one is the cheapest place to change your mind, and what to look for in a plan.
ReadDecide mobile or desktop before you build
Every Oryn game runs on both, but only one of them is what the game is designed around — and that choice shapes orientation, controls, and the mechanics themselves.
ReadIterate without breaking what already works
One change at a time, test in the preview, and use version history as a safety net rather than a last resort.
ReadBring your own assets, or generate them
Three sources of art and audio, how to get them wired into the game rather than parked in a folder, and what to check before you publish commercially.
ReadExport the Godot project and share the build
What is inside the export, how to continue the project in Godot yourself, and the difference between sharing a playable link and shipping to a store.
Read