Manage Phaser multi-scene lifecycles, transitions, and cross-scene communication.
npx skills add https://github.com/jallard-007/jallard-ca-server --skill scenes-jallard-007
Please help me install this Agent Skill. Skill: scenes Source: https://github.com/jallard-007/jallard-ca-server/tree/main/.github/skills/scenes Command: npx skills add https://github.com/jallard-007/jallard-ca-server --skill scenes-jallard-007
Scenes are the organizational backbone of a Phaser game. Each Scene has its own lifecycle (init, preload, create, update), its own set of injected systems such as add, input, cameras, etc., and can be started, stopped, paused, slept, or run in parallel with other Scenes. The ScenePlugin, exposed as this.scene, controls all multi-scene orchestration.
Create a minimal Phaser.Scene class and register it in your game's scene array to observe the lifecycle from init through update.
High-intent search queries and answers about installing and using this skill.
Multi-scene management in Phaser is handled by using the SceneManager and ScenePlugin to control scene lifecycle, startup order, and parallel execution. You can coordinate scenes like loading screens, gameplay, and UI to run together for smooth game initialization.
Cross-scene communication in Phaser uses event-based systems and data passing through the ScenePlugin. Scenes can share data during initialization and emit events to each other, enabling coordinated behavior between parallel scenes like a gameplay scene and an overlay UI scene.
The Phaser scene lifecycle consists of init, preload, create, and update phases. You structure your game logic by registering a Phaser.Scene class and organizing asset loading, object creation, and frame updates across these distinct lifecycle events.
Yes, Phaser allows multiple scenes to run in parallel with controlled rendering order. The SceneManager handles launching scenes simultaneously, enabling you to layer a UI scene over a gameplay scene while both maintain their own lifecycle and injected systems.
Scene management is required to organize complex Phaser games with multiple scenes needing orderly startup, data passing, and cross-scene communication. It prevents initialization conflicts by structuring the lifecycle and controlling the rendering order of overlapping scenes.
Yes, Phaser scene management supports the injection of global and scene-specific properties to streamline development. This allows you to share configurations and systems across multiple scenes while maintaining the isolated lifecycle of each individual scene.
diegolinharesManage Phaser 4 scene lifecycle, transitions, and communication.
dzyamikManage Phaser 4 scene lifecycles, transitions, and inter-scene communication.
Dominik-SteinwegManage Phaser 4 camera viewports, scrolling, and post-processing effects.
Dominik-SteinwegManage Phaser 4 scene lifecycles, transitions, and parallel orchestration.
