story-starts

Story starts use a strict schema for narrative-driven game openings, defining required fields like name, description, locations, and locationAreas to ensure consistent configuration and reduce misconfigurations across worlds.

A compelling game opening scene uses a three-part storyStart format consisting of Scene, Situation, and Hook, ensuring structured validation and engaging narrative design for your game's initial player experience.

You can add optional starting quests and party NPCs to your narrative design configuration using the supported optional fields: startingQuests, firstQuest, startingPartyNPCs, and isDefault for flexible worldbuilding setup.

Yes, the story-start schema validates frontmatter-driven metadata across multiple locations and location areas, guiding structured configuration generation and providing documentation references for integration with Voyage-like engines.

The strict schema requires mandatory fields like storyStart, locations, and locationAreas, limiting freeform narrative design but ensuring frontmatter-driven metadata validation and reducing configuration churn for game openings.