Phaser-Spielregeln und Speicherstände

Phaser — gameplay state save

Use when implementing Phaser score, progression, inventory, deterministic rules or local saves.

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

Separate game rules from rendering callbacks. Define state transitions and stable item identifiers, version the persisted data and validate parsed storage. Keep rewarded actions idempotent across duplicate overlap/input events. Expose reset/replay behavior without erasing an unrelated save.

Deliver

A small rules/state module with explicit save/load and replay contracts. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.

Failure to prevent

Client storage is user-editable and must not establish trusted online rewards or ownership.

Acceptance scenario

Duplicate a pickup event, reload after saving and load an older or malformed copied save without losing the previous valid state. 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