Chapter 13 — Content Files
Part IV — Authoring Games
The schema system that defines your world.
A content pack is the simulation: zones, who is in them, gates, items given to an entity. Dimetric cells, floor plates, and which way a sprite faces are WorldProject.presentation in World Forge. They are not keys on this pack. The stage draws them. See Chapter 66.
Content Types
Section titled “Content Types”| Type | Purpose |
|---|---|
| GameManifest | Top-level game definition |
| EntityBlueprint | Actors, enemies, objects |
| RoomDefinition | Spatial containers |
| ZoneDefinition | Sub-areas within rooms |
| DialogueDefinition | Conversation trees |
| QuestDefinition | Objective tracking |
| AbilityDefinition | Skills and actions |
| StatusDefinition | Buffs, debuffs, conditions |
| ProgressionTreeDefinition | Advancement paths |
The Validation Pipeline
Section titled “The Validation Pipeline”Content goes through three stages before it reaches the engine:
schema validation → cross-reference validation → compiled content bundle- Schema validation — structure and types are correct
- Cross-reference validation — all refs point to real content (zones, entities, items)
- Compilation — content is bundled into a runtime-ready format
Errors are caught early, before the game runs. This prevents broken references, missing entities, and malformed data from causing runtime crashes.
Content Is Data, Not Code
Section titled “Content Is Data, Not Code”Games define their worlds through structured content files, not by writing engine code. This keeps gameplay logic separate from simulation mechanics and makes worlds portable across engine versions.