RPG Data and Starting State · Version 0.5
RPG Database Overview
Understand the current 15 RPG Database panels, their dependency order, persistent undo and redo, and the difference between definitions and runtime state.
The RPG Database is the central authoring workspace for reusable RPG definitions and managed catalogs. Filmstrip validates candidate changes across dependent registries and project documents before replacing the accepted snapshots.
Current panels
- Stats
- Actors
- Equipment Slots
- Items
- Currencies
- Shops
- Reward Bundles
- Quests
- Abilities
- Status Effects
- Enemy Parties
- Combat Rewards
- Encounters
- Variables
- RPG Tags
Recommended dependency order
- Create Variables, RPG Tags, Stats, and Equipment Slots first.
- Create Actors and Items after the definitions they reference exist.
- Create Currencies, Shops, Reward Bundles, and Quests.
- Create Status Effects and Abilities before Enemy Parties.
- Create Combat Rewards and Enemy Parties before Encounters.
- Author the starting Party, inventory, balances, equipment, and Quest state after the required definitions exist.
Definitions versus runtime state
A definition describes reusable content. Runtime state references the stable definition ID and stores mutable values such as current HP, experience, Item quantity, equipment assignment, Currency balance, Quest progress, or active Status duration.
Persistent history
Database changes use a persistent command history. Successful edits save atomically. Undo and redo write a complete restored snapshot and checkpoint it immediately, so the editor never claims an already-persisted registry snapshot is still waiting to be saved.
Cross-project safety
Opening another project launches a fresh editor process with a new Project Database and writable-state graph. One project’s registries cannot remain active while another project is opened.