Phaser gameplay and saves
Keeps score, inventory and progression independent of what is drawn. It validates stored progress and makes rewards repeat-safe when collisions or button presses arrive more than once.
phaser-gameplay-state-save
See how it helpsWhen is it useful?
Use when implementing inventory, scoring or local saves in Phaser.
What does it help you do?
- Defines stable item identifiers and explicit progression transitions.
- Makes rewards resistant to repeated overlap or input events.
- Preserves valid state when older or malformed saved data is loaded.
Try asking this
For our puzzle adventure, unlock a door after collecting three distinct keys. Reload the game, repeat a pickup event and load an older save missing the door field. Preserve earned keys, award each once and explain the migration of the door state.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
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.
Included files 1
SKILL.md