What problem does it solve? Game state like flags, counters, and custom objects must survive save/load and history go-back in a Pixi'VN game, and using the wrong storage API or reserved keys can silently break persistence. ## Core Features & Use Cases - Simple Variables and Flags: Read and write persistent values with storage.set/storage.get, and use the dedicated storage.flags store for booleans to keep save files small. - Custom Persisted Classes: Extend StoredClassModel with a category ID and per-instance ID so rich objects like quest trackers survive save/load with per-property overrides. - Temporary Label-Scoped Variables: Use storage.temp for scratch state that automatically resets when the originating label closes. - Use Case: Track whether the player has met a character by setting a flag, then store a quest model whose completed property persists across saves and history rewind. ## Quick Start Ask the AI to add a persistent gold counter and a quest-tracking StoredClassModel to your Pixi'VN game using the storage API.