Orchestrate Phaser 4 scene lifecycle and state transitions.
npx skills add https://github.com/WanderTheWeeb/papas_trauma --skill scenes-wandertheweeb
Please help me install this Agent Skill. Skill: scenes Source: https://github.com/WanderTheWeeb/papas_trauma/tree/main/skills/scenes Command: npx skills add https://github.com/WanderTheWeeb/papas_trauma --skill scenes-wandertheweeb
Phaser 4 scene-heavy games often become difficult to manage because developers must correctly coordinate lifecycle phases, state changes, and inter-scene communication without causing bugs or broken transitions.
Use the scenes skill to design a minimal Phaser 4 Scene class that implements init, preload, create, and update, then uses this.scene.start('NextScene', { level: 2 }) to transition with data.
High-intent search queries and answers about installing and using this skill.
Transition between Phaser 4 scenes by calling this.scene.start('NextScene', { level: 2 }) to pass initialization data. You can also use switch, launch, or transition methods to orchestrate state changes and pass data reliably across scene boundaries.
The Phaser 4 scene lifecycle flows through init, preload, create, and update phases while moving between PENDING, RUNNING, PAUSED, SLEEPING, SHUTDOWN, and DESTROYED states. Understanding these states ensures safe scene orchestration and prevents broken transitions.
Broken Phaser scene transitions often occur due to ignoring SceneManager-driven queued operations or incorrect transition event timing. Coordinating lifecycle phases, using injected systems access patterns, and properly handling state changes prevents timing and control-flow bugs.
Yes, you can run parallel overlay scenes and control render ordering in Phaser 4. Using sleep, wake, and launch methods allows you to manage decoupled UI and game logic layers simultaneously without disrupting the main game flow.
The best way to communicate between Phaser scenes is by passing initialization data through start or launch methods, sharing global state via the registry, and using scene event emitters for decoupled UI and game logic communication.
Use sleep and wake to temporarily hide a scene while keeping its state intact for rapid reactivation, whereas pause stops update logic but keeps rendering, and stop completely shuts it down. Choosing the right method optimizes lifecycle management.
diegolinharesManage game object grouping, pooling, and nesting in Phaser 4 scenes.
jallard-007Manage game-state data across objects, scenes, and the global registry.
simon-tannaBuild 2D games with Phaser 3 scenes, physics, and tilemaps.
johnnystefanImplement the State pattern to manage object behavior across status transitions.
