Voyage Schema V37 GameState: Complete Reference

Version: 2.52.0
Purpose: workflow guide and schema reference for creating and editing V37 scenarios - the raw JSON structure and the editor UI for each section, as a structured flow of information.

About this wiki

Community resource, not official documentation

This wiki is run by Guappa together with its community, and is not affiliated with Voyage. It is a best-effort project maintained by people, so expect the occasional mistake or error in the prose: treat it as a well-checked reference rather than ground truth, and when in doubt, test it yourself.

Where it comes from

Section and field information (names, types, required fields, allowed values, size limits, and the errors and warnings Voyage raises) is read straight out of Voyage's code and Studio on every update, not typed in by hand. If any of that is wrong here, it is either wrong in Voyage too, or we haven't caught up with the latest patch yet. For behaviour that can't be read that way, we fall back on the reference docs in World-Puppeteer, but only where nothing more authoritative covers the point. Where our own extraction disagrees with them, the extraction wins, and the wiki has corrected claims that came from there.

Every refresh replays 1,838 mutated worlds through Voyage's own validator to check this site agrees with it, on top of 1,681 automated tests. How this is verified describes the method, the figures, and what it does not cover.

How the explanations are written

Much of the text describing what a section or field does follows the descriptions Voyage Studio itself shows, taken or paraphrased from there. The rest is written for this wiki, mostly with AI working mechanically from the extracted data rather than from general knowledge: a field is only documented if it exists there. How something behaves is checked against Voyage's own engine wherever it can be probed. Some engine internals can't be, and those are tested by hand as a last resort. If none of these sources backs a statement up, it doesn't belong here, and we take it out as soon as we spot it.

Checked before it ships

Every release has to pass over 1,000 automated tests, and every schema update compares the builder's validator against Voyage's own checker on which worlds get rejected. Changes are proofread before they go live.

Built with its readers

Suggested edits and reports on Discord have corrected and added to this wiki before. Spotted a mistake? Use Edit / Suggest change at the top of any page, or tag Guappa on the AI Dungeon Discord for a direct line.

Current against the beta build. The schema, field notes, and validator here are extracted from and kept in sync with the beta Voyage build.

Build a world

Edit the JSON by hand with this reference open, or build visually in an editor with inline validation.

BuilderThe companion editor for this reference. Build V37 scenarios with a visual interface and live validation, no file editing required.Voyage ForgeAnother community-built visual world editor.Voyage Forge GuideCommunity-written walkthrough covering world creation step-by-step.

Start here

WorldStory, Lore, NPCs, LocationsBuild the people and places. Story overview, world lore, NPCs, items, factions, locations, regions, quests.MechanicsSkills, Traits, AbilitiesHow characters act and grow. Attributes, resources, skills, traits, abilities, triggers, combat settings.AINarrator InstructionsEvery narrator task. Story, Initial Start, NPC Details, NPC Intents, encounters, and more.OtherModes, Music, SettingsGame modes, narrator style, name filters, archetypes, and the remaining world settings.AppendixScripting and ValidationTrigger scripts, worked recipes, size limits, the voice catalog, and validator gotchas.Community GuidesTutorials and How-tosCommunity-written walkthroughs that complement the schema reference.ModsLayered Partial WorldsLayer partial world JSON over an existing world: same editor, same schema, no required sections.ToolsValidator, Workbench, Field indexValidate a world, audit triggers in plain language, browse every field, read the machine API.

For AI agents

Every section is exposed as a self-contained API endpoint with the schema fragment, prose explanation, field notes, and authoring tips. World JSON can also be validated via POST /validate. See /tools/api for the full list of endpoints, examples, and an agent prompt snippet.