game-manager-skill

Game state persistence across agent skills is managed via a central SQLite database that handles saves, loads, and global synchronization. This ensures consistent world state across sessions and prevents data drift between different modules.

Resetting world state involves running a script-driven workflow that restores templates, clears archives, and reinitializes memory. This workflow manages the /game-restart cycle to return the game to its initial state.

Yes, game state management requires a central SQLite database and the sqlite3 dependency. You need this environment set up before executing save/load cycles or cross-skill state synchronization.

You save and load game state by executing script-driven commands that interact with the central SQLite database. Start by running the manager script with the reset flag, then perform a full save to confirm persistence.

Cross-skill state drift occurs when individual modules maintain isolated data instead of syncing with a central store. Global synchronization solves this by keeping all skill reference data aligned with the central SQLite database.

Yes, this handles game state archiving and global synchronization specifically for an immersive modular wuxia game. It manages save/load cycles and world resets to maintain state consistency across the game ecosystem.