AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 1, 2026, 22:00 JST

Three live mobile RPGs move to Unreal Engine 5.8 without a rewrite

Three live mobile RPGs move to Unreal Engine 5.8 without a rewrite

3 Key Points

  1. What happened

    The developer kept the old Cocos2d-x 3.17.2 C++ and Lua running untouched, and built a compatibility runtime on Unreal Engine 5.8 that mimics the Cocos2d-x API. AI agents (Claude, models Fable 5 and Opus 5) did most of the work.

  2. Why it matters

    Save data and paid in-app purchases carried over to existing users through store updates under the same bundle id, so the migration reached players without a restart.

  3. What to watch

    Only 2 crashes were logged on the Gifu Quest Unreal Engine version on Google Play (through September 28), and adoption depends on automatic store updates reaching players gradually.

WHO IT HITSDevelopers running live games on abandoned engines — especially small teams and solo operators with years of Lua and C++ code — may see keeping the old code and swapping the layer underneath as an alternative to a full rewrite. Studios weighing that path would still need automated tests and a compatibility runtime, not just AI agents.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The developer had previously worked on a game built with Cocos2d-x, chosen over Unity about 15 years ago, and later experienced the difficulty of running a game on an engine whose development had stopped. That experience shaped this migration: the goal was not to modernize the games but to replace the ground beneath them. The three titles share a self-built RPG engine on top of Cocos2d-x, and most of their content — Lua scripts, Tiled maps, Cocos Studio UIs, master data — stayed exactly as it was.

The approach changed two days in. The first plan was to rebuild the game logic inside Unreal Engine and reconnect the old Lua events one by one, but the scale of the project made that unworkable. On the third day the developer switched to running the old C++ wholesale on a compatibility runtime with the same API surface as Cocos2d-x. The prototype from the first two days was deleted the next day. Reusing the compatibility runtime across titles, copying the newest game's version and adding only per-title differences, is what made the second and third migrations fast.

The bet now rests on maintenance rather than technology. The developer says server costs are covered by ads, so keeping the games running takes only minimal revenue like the annual Apple Developer Program fee, and if the engine ages, the same layer-swap can be repeated. Whether that holds depends on continued AI-assisted upkeep and on whether the few remaining crashes are resolved.

FAQ
Which games were moved?
Gifu Quest, Mie Quest, and Aichi Quest — the three free-to-play titles in the "Regional Quest" series, which are live games with ads and in-app purchases.
How was the move done without rewriting the games?
The old Cocos2d-x C++ and Lua code was kept running as-is, with a compatibility runtime built on Unreal Engine 5.8 that mirrors the Cocos2d-x API. Only 28 files of the imported code were modified.
Did players lose their save data or purchases?
No. The old saves and user IDs were read directly, a backup of the old save was made on the first update, and the games were delivered as store updates under the same bundle id and package name.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOllaya runs decision models locally, up to 255 options