Porting a 20-Year-Old Game to Mobile: Lessons from RuneScape

RuneScape, one of the longest-running MMORPGs, began in 2001 with over 15 years of content and a persistent world shared by players on both mobile and desktop platforms. Bringing this game to iOS and Android required porting a long-lived desktop game to touch devices and constrained hardware. At Jagex Games Studio, the mobile port team operated under the mandate of achieving full cross-platform parity, meaning a mobile player would have access to all the same features as a desktop player.

The challenge was immense due to the game's complexity. It had accumulated content over 20 years, built by hundreds of developers. RuneScape's unique scripting language, RuneScript, added to the complexity. The team faced a series of technical hurdles, from hard-coded screen dimensions to mouse-specific input assumptions baked into core gameplay mechanics. They also had to address memory usage patterns, which were acceptable on desktop (with 2GB+ RAM) but problematic on mobile (with limited, shared resources).

The team's first significant contribution was their thorough audit of the systems they would need to touch. This audit revealed critical issues like embedded hard-coded screen dimensions, assumptions about mouse input, and desktop-specific rendering paths. By identifying and documenting these issues upfront, they avoided many crises during production. This experience was crucial for their approach at Ocean View Games, where they implemented a similar audit-first methodology when remaking Nub for iOS and Android.

The second key takeaway was that touch UI is fundamentally different from a scaled-down desktop UI. The original desktop interface was designed for mouse and keyboard interactions, featuring right-click context menus, hover states, and dense UI panels. These elements were impractical on touchscreens, which lack the precision of a mouse cursor, do not have hover states, and cannot display the same amount of information as a desktop monitor.

The solution was to employ a context-sensitive adaptive UI, showing only the information relevant at any given moment and providing touch-native equivalents for desktop-only interactions.

In summary, porting a legacy game like RuneScape to mobile is not just about scaling down the desktop version. It requires a comprehensive understanding of the legacy codebase, a thorough audit before any architectural changes, and a focus on adapting the touch UI to fit the unique challenges of touchscreens. These lessons are now integral to the mobile development and porting work at Ocean View Games.