Phaser-Eingabe und Skalierung

Phaser — input scale

Use when implementing Phaser touch, keyboard, gamepad or responsive canvas interaction.

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

Map device input to actions and define UI/gameplay capture. Choose scale and camera behavior for the game’s target orientation. Convert pointer positions through the relevant camera and world transform; reset held input on focus loss and scene transitions.

Deliver

An input/scale contract with working menu and play interactions on the intended aspect ratios. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.

Failure to prevent

CSS stretching alone can misalign hit areas and canvas coordinates.

Acceptance scenario

Tap screen edges, resize the host, hold a key during pause and interact with a HUD overlay above gameplay. 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