Dragon Island roadmap. Finishing the emulator, Android port, and a two-server model.
What is next for dragon-island.com. The server emulator gets finished, an Android build joins web, and we move to a permanent + seasonal server pair with cross-server migration.
Dragon Island is the project I have been pouring most of my time into. The website and CMS are live. The next phase is bigger and I want to put it on record before it ships.
Three threads in parallel
- Finish the server emulator (Season 6+, C++)
- Android port so people play during commutes, not only at desks
- Permanent + seasonal server pair with one-click migration through dragon-island.com
Each one is a real chunk of work. Done together they change what kind of community Dragon Island can host.
Why Android matters
Most MU Online private servers assume a desktop player on a desktop client. That market is shrinking. The Android port lifts the ceiling on who can join, which directly lifts the daily active count. A casual player who logs in from a phone is still a player. A player who has to boot a Windows machine to log in is often a player who logs in twice a year.
The technical path: Capacitor for the wrapper, native Android UI for menus and inventory, the C++ game logic served from the existing emulator over a thin protocol. Same backend, second client.
The two-server model
Most servers run one of two ways: a single permanent server (slow drift, no fresh start) or a season-only server (cool start, players leave with nothing). Both bleed players over time.
The plan is to run both, and connect them:
- Permanent server. Always on. The long-term home. Characters, items, history persist.
- Seasonal server. Restarts on a cycle. Fresh economy, new meta, race to the top.
When a season ends, players migrate their character (or selected items) from the seasonal server into the permanent one. The CMS at dragon-island.com handles the migration: pick the character, pick what to bring, confirm. The character lands on the permanent server with their progress intact and a migration tag in their history.
Why this works: seasonals attract the rush, permanent retains the survivors, and the bridge between them means time on a seasonal is never wasted.
What still has to happen
- Emulator: finish Dragon Tower polish, ship the auction system, harden the packet anti-hack
- Android client: protocol design, login flow, inventory UI, store integration
- Migration: schema for cross-server character transfer, UI in the CMS, edge cases for inventory overflow, rollback on failure
- Infra: a second server box for the seasonal instance, monitoring across both
It is a lot. Most of it is also already prototyped in some form. The pieces exist, the work is putting them together and hardening for real players.
Why I am writing this now
Public roadmaps keep me honest. If you play on Dragon Island and want to follow along, the next few months will be loud. If you are a recruiter reading this: yes, this is what production game infrastructure looks like at the scale of one developer with AI tooling. The plan is realistic. The shipping is the part I do.