The Unfinished Kingdom has two very different surfaces.
The battlefield needs animated sprites, parallax layers, particles, timing, camera effects, and efficient continuous rendering. The Armory, settings, navigation, and account screens need accessible controls, responsive text, and ordinary interface behavior.
Using Phaser for the battlefield and standard browser UI for the cabinet gives each problem an appropriate tool. The engine renders the world at a controlled internal resolution with crisp nearest-neighbor scaling. The surrounding interface responds directly to phone safe areas, keyboard navigation, and changing viewport height.
We selected Phaser 4.2.1 for the prototype and pinned the exact version. Reading documentation for a different release can produce code that appears reasonable while relying on behavior the project does not have.
The choice remains subject to real-device evidence. A recent phone and an older phone need to survive extended play without repeatable rendering failures, excessive heat, or browser eviction. Performance mode targets 30 frames per second with fewer visual layers.
We are also avoiding a common trap in layered character systems: placing equipment with a pile of screen-specific coordinates. The Warden has one internal frame, one origin, named attachment points, and item-specific pivots. The completed character scales as a unit. Mobile CSS must never decide where the sword belongs.
That architecture takes more effort before the first large equipment catalog exists. It saves much more effort after it exists.
An engine is not the game. It is the agreement about how the game will draw, update, pause, recover, and scale. Phaser currently gives us the battlefield foundation we need while allowing the rest of OctarineOnline to remain a web platform.