game-phaser-development

Phaser Game Development

Core Workflow

1. Identify the 2D game genre, target browsers/devices, orientation, resolution strategy, input methods, physics model, asset style, and publishing target.
2. Structure the game around Phaser scenes: boot/preload, main menu, gameplay, UI/HUD, pause, transitions, game over, and results where needed.
3. Use Phaser lifecycle methods deliberately: preload assets, create stable scene objects, update only active simulation, and clean up events/timers/listeners on scene shutdown.
4. Choose physics by gameplay need: Arcade for simple fast AABB/circle motion, Matter for richer bodies/constraints, or no physics for grid/turn/menu games.
5. Keep gameplay rules, data, and tuning values separate from raw sprite setup when the project will grow.
6. Verify in real browsers with responsive scaling, focus loss, audio unlock, mobile touch, fullscreen, and itch.io iframe behavior when publishing.

Phaser Priorities

• Scenes: use scene keys consistently, avoid conflicting scene registration, and choose start/stop/sleep/wake intentionally.
• Assets: preload with clear keys, use atlases/spritesheets where appropriate, handle load progress and failure states, and keep paths case-correct.
• Physics: tune gravity, body sizes, collision categories, overlap/collider callbacks, velocity, drag, bounce, and world bounds explicitly.
• Cameras: use follow, bounds, zoom, shake, fade, dead zones, and multiple cameras for HUD/game separation where useful.
• Input: support keyboard, pointer/touch, gamepad, focus loss, pause, remapping where needed, and mobile hit target sizing.
• Animation: define animation keys, frame rates, repeat rules, state transitions, and cancellation behavior.
• UI: separate HUD and menus from gameplay scenes when layering, persistence, or pause behavior matters.
• Performance: watch active sprites, particles, physics bodies, tilemap layers, texture sizes, object churn, and expensive per-frame callbacks.

Architecture Guidance