What problem does it solve?
Phaser 3 to Phaser 4 upgrades often break existing rendering, shaders, masks/FX, tinting, and camera math, leaving developers stuck debugging API differences without a systematic migration plan.
Core Features & Use Cases
- Rendering and pipeline migration: Converts v3 WebGL Pipeline concepts into v4 RenderNode architecture, including guidance for custom WebGL changes.
- Visual effects, masks, and tint updates: Replaces FX/masks with the unified Filter system and updates tint APIs and modes to match v4 behavior.
- Engine-breaking API adjustments: Covers major breaking changes including camera matrix differences, shader/uniform API changes, GLSL loading changes, texture coordinate orientation, DynamicTexture/RenderTexture render() requirements, and multiple removed objects/plugins/utilities.
Use case example: You have a Phaser 3 project that uses custom pipelines, BitmapMask-based masking, shader-based effects, and camera matrix access; you need a checklist-driven set of code changes to reach a working Phaser 4 build.
Quick Start
Ask an AI to generate a Phaser 4 migration patch for your specific Phaser 3 codebase by following the v3-to-v4-migration guide and applying its breaking-change checklist.