Phaser-Szenenlebenszyklus

Phaser — scene lifecycle

Use when implementing Phaser scenes, transitions, overlays, pause or restart behavior.

Version and project gate

Inspect Phaser major version, package lock, scene registry, renderer, scale configuration, Arcade/Matter plugins, loaders, animation keys and deployment base path. Phaser 2 States, Phaser 3 Scenes and newer APIs are not interchangeable. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.

Work

Draw the boot/preload/create/update/shutdown/destroy transitions actually used. Separate persistent game caches from scene-owned listeners, timers and objects. Connect inter-scene events through an explicit owner and unregister external listeners on shutdown. Ensure restart reinitializes transient state.

Deliver

A scene transition table and a repeatable menu/play/pause/restart implementation. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.

Failure to prevent

Scene shutdown and destruction differ; registering a global listener every create call can duplicate behavior.

Acceptance scenario

Restart the level repeatedly and confirm a single input event, timer and score transition per action. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.

Scope and sources

This skill belongs to Kip. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.

• https://docs.phaser.io/phaser/concepts/scenes
• https://docs.phaser.io/api-documentation/class/scene
• https://github.com/phaserjs/phaser/blob/master/skills/physics-arcade/SKILL.md