data-manager

You can manage game state data in Phaser by using an event-driven key-value store. It provides per-object, scene, and global registry storage that emits events on data changes, enabling reactive and decoupled gameplay logic across systems.

The best way to share state across scenes is using a global registry. The game.registry provides isolated event emitters and cross-scene data storage, allowing you to set, get, and listen for global data changes without direct scene dependencies.

To trigger UI updates on data changes, listen for changedata, setdata, or removedata events. This event-driven approach emits notifications whenever reactive keys are updated, allowing decoupled systems to respond automatically.

Yes, you can increment and toggle state values directly. The data management primitives provide incData and toggleData functions alongside standard set and get methods, allowing you to easily modify numeric and boolean game state values.

Yes, Phaser provides a scene-level data plugin accessible via this.data. It allows you to store and retrieve scene-specific state using key-value pairs while emitting events to maintain reactive gameplay logic within that scene.

Use scene data for state isolated to a single scene, and the global registry for cross-scene state. This separation prevents tight coupling by scoping data storage and event emissions to the appropriate level of your game architecture.