Coordinate Phaser 4 event-driven communication across scenes and game systems.
npx skills add https://github.com/kehwar/pixi-square --skill events-system-kehwar
Please help me install this Agent Skill. Skill: events-system Source: https://github.com/kehwar/pixi-square/tree/main/.agents/skills/events-system Command: npx skills add https://github.com/kehwar/pixi-square --skill events-system-kehwar
Phaser relies on the EventEmitter pattern across its systems, which can lead to scattered listeners and hard-to-trace flows. This skill provides guidance for organizing event-driven communication across Game, Scene, and UI layers, ensuring reliable messaging and clean lifecycle management.
Listen for a scene event and emit a custom event to notify other parts of the game
High-intent search queries and answers about installing and using this skill.
To prevent memory leaks during Phaser scene restarts, use proper listener management by calling off or removeAllListeners to clean up active event emitters before the scene shuts down. This ensures destroyed scenes do not retain references to old callback functions.
Scene-level events are scoped to the current scene via this.events, while game-level events are globally scoped via this.game.events. Distinguishing them allows you to control inter-scene messaging and broadcast communication across the Game, Scene, and UI layers.
You send custom events between Phaser scenes by emitting messages on the shared game-level event emitter. Other scenes listen to this.game.events using the on or once methods to receive the inter-system communication and execute their corresponding logic.
Using named constants like Phaser.*.Events for event strings avoids typos and enables IDE autocomplete. This practice ensures reliable messaging by validating event names at compile time, making your event-driven flows predictable and easier to trace.
The Phaser EventEmitter pattern works for inter-system UI communication by coordinating event-driven messaging across the Game, Scene, and UI layers. It uses on, once, and off methods to handle input-driven events and custom notifications cleanly.
The best way to organize scattered listeners is grouping event-driven communication by scope using scene-level and game-level emitters. Applying predictable patterns and proper cleanup practices ensures reliable messaging and clean lifecycle management.
WanderTheWeebStandardize EventEmitter-based communication in Phaser 4 with lifecycle-safe listener cleanup.
GiantCroissant-LunarCoordinate in-game events across Phaser scenes using the EventEmitter pattern.
Raphe-devManage Phaser 4 EventEmitter communication across scenes and game systems.
MacPhobosExplain advanced event system patterns for Tauri applications.
