Engine workflow
Organise game design data in the browser, then export selected quests, characters, items, skills, locations and lore as clean JSON for Unity. The same engine-independent output can feed Unreal Engine, Godot or custom studio tooling.
Export selected entry types instead of an entire monolithic document
Use predictable structured fields for import and validation
Keep design content separate from engine implementation details
Commit exported JSON to Git or transform it in a build pipeline
Designers can work in a purpose-built game workspace while developers consume ordinary JSON. Build a small Unity importer with JsonUtility, Newtonsoft JSON or your existing serialization layer and map exported fields into the runtime structures your project already uses.
Export a focused set of quests for a narrative prototype, item data for balancing, or the complete world library for an internal tool. Selective exports make review and source-control diffs easier than moving one giant game design document.
The export is not locked to a proprietary plugin. Transform the same JSON for Unity ScriptableObjects, Unreal data tables, Godot resources, web tools, localization systems or automated validation in CI.
You can export selected characters, items, skills, quests, locations, lore and other structured entries as JSON.
No. Gamifying produces ordinary JSON, so you can import it with Unity's built-in JSON tools or your own data pipeline.
Yes. The output is engine-independent JSON and can be transformed for Unity, Unreal Engine, Godot or custom tooling.
Design connected game quests with AI-assisted objectives, rewards, characters and lore. Edit every field and export structured quest JSON.
Build a searchable game lore bible for factions, history, locations, characters and magic systems with contextual AI assistance.