Online rpg games bg img
Back to top

Online RPG games: what it takes to build and run one

Dmytro Lunov

Written by

Dmytro Lunov Verified author

Head of Delivery and Program Director at Game-Ace

Dmytro leads Game-Ace delivery teams on game development, art production, game design, MVP prototyping, and Unity and Unreal Engine projects.

Published August 14, 2024 Updated September 9, 2026

Online RPG games are role-playing titles where progression, story, or combat happens against a live backend that other players or persistent game state can influence. The category today covers MMORPGs, ARPGs, mobile gacha RPGs, and small-party co-op RPGs. Each subgenre has its own scope, team size, and backend footprint, and treating them as one product is the fastest way to overrun a budget.

What online RPG games mean today

The label "online RPG games" used to mean one thing: an MMO with thousands of players in a shared world. That is now a minority of the market. Today an online RPG is any RPG where meaningful state lives on a server, whether that is a gacha pull, a co-op raid, a PvP ladder, a live season, or a shared economy. Genshin Impact runs as a single-player feeling RPG with a live event calendar and cross-save backend. Honkai: Star Rail is turn-based and offline-playable, yet the entire progression loop depends on server-side pulls, events, and battle passes. Lost Ark is a session-based ARPG built on regional server clusters. The Elder Scrolls Online remains a classic sharded MMORPG.

The Elder Scrolls Online, a classic sharded MMORPG

When a studio says "online RPG", the first question a producer should ask is which of these models the game maps to. That decision drives tech stack, team size, and cost.

Scoping an online RPG at concept, prototype, or live-production stage?

MMORPG: persistent world, sharded backend

MMORPGs are the heaviest subgenre and the most expensive to operate. They rely on sharded world servers, character databases with high write volume, guild and economy systems, and a real-time combat protocol that has to reconcile many entities per frame. Albion Online proved that an indie MMORPG can ship on a single-shard cluster if the design accepts queue times. The Elder Scrolls Online uses a megaserver model with instancing. Both approaches shape the entire art, quest, and content pipeline.

A realistic mid-scope MMORPG needs a team of 40 to 80 people across engineering, art, backend, and QA, and 24 to 36 months to a soft launch. Game-Ace typically joins MMORPG projects as a co-development partner alongside a client team, covering client-side gameplay in Unity or Unreal, backend services, and content production. See the MMORPG game development service page for scope detail.

ARPG: session-based combat and loot loops

Action RPGs like Path of Exile 2, Lost Ark, and Last Epoch sit between single-player and MMO. Players do most content solo or in small parties, but character data, seasons, trade, and leaderboards run on shared servers. The backend load is bursty rather than persistent: players connect, run instanced content, and disconnect. That makes autoscaling and session brokers more important than long-lived world simulation.

The client-side challenge is loot: rolling, filtering, and rendering thousands of item variants without draining the frame budget. The backend challenge is anti-cheat and duplication protection on trade. Studios scoping an ARPG usually pick Unreal Engine or a custom C++ layer over Unity for combat feel, and delegate item generation and trade to dedicated services.

Mobile gacha RPGs: banners, meta, and pull economies

Mobile is the largest single platform for online RPG games by revenue, and gacha titles lead that category. Genshin Impact, Honkai: Star Rail, and AFK Journey all use timed banners, pity systems, and character-limited pulls. From a production perspective a gacha RPG is a live content factory: a new banner every 3 to 6 weeks, new characters modeled and animated, new voice-over, balance updates, and live server events. The client-side render budget has to accommodate multiple visually distinct character sets active in the same team.

Building for mobile also means designing around 90-second sessions, thermal limits on mid-range Android devices, cellular network drops, and store review policies for gacha and loot systems. Unity remains the most common engine choice for mobile online RPG games because of its Android hardware coverage and Addressables workflow for streaming content updates.

Co-op RPG: small parties, low backend cost

Co-op session RPGs run in short-to-medium sessions with a small group. Players match into a lobby, complete a run or a mission together, and return to a hub or a menu. Backend is lighter than MMORPG: matchmaking, lobby state, and player inventory. This is often the fastest online RPG subgenre to ship. A mid-scope co-op RPG can reach a playable vertical slice in 6 to 9 months and a full release in 18 to 24 months with a team of 15 to 25 specialists. Many studios use co-op as a stepping stone before scaling to a full MMO backend.

How the four subgenres compare

The table below summarises how MMORPG, ARPG, mobile gacha RPG, and co-op session RPG differ in team size, production scope, and backend footprint. Numbers reflect what live indie and mid-scope studios usually plan around.

DimensionMMORPGARPGMobile gacha RPGCo-op session RPG
Peak team size40 to 8025 to 6030 to 70 plus live team15 to 25
Time to soft launch24 to 36 months18 to 30 months18 to 24 months12 to 20 months
Backend footprintSharded world servers, high-write DBSession broker, stateless game servers, trade servicesWeb-service backend, banner and event system, gacha ledgerLobby matchmaking, inventory DB
LiveOps cadenceSeasons plus expansionsSeason every 3 to 4 monthsBanner every 3 to 6 weeksContent drop every 3 to 6 months
Live examplesThe Elder Scrolls Online, Albion OnlinePath of Exile 2, Lost Ark, Last EpochGenshin Impact, Honkai: Star Rail, AFK JourneyDeep Rock Galactic, Remnant II

Backend architecture for online RPG games

Backend architecture is where most online RPG projects fail commercially. The backend has to handle authentication, character storage, real-time state, session brokering, matchmaking, chat, and store transactions. For an MMORPG the world simulation runs on dedicated authoritative servers with a database tier for persistence. For an ARPG or co-op RPG a session broker plus stateless game servers usually suffices. For a mobile gacha RPG the backend is closer to a live-service web app with periodic content drops.

Common building blocks include WebSocket transport for chat and real-time updates, see the MDN reference on the WebSocket API, Redis for matchmaking and hot state, PostgreSQL or a NoSQL layer for account persistence, and container orchestration for scaling regional clusters. Studios often underestimate the observability layer: without proper metrics and player-facing telemetry, a live online RPG becomes unmaintainable within its first LiveOps season. Related reading: why your single-player game needs a backend.

For end-to-end backend and gameplay scoping across a production, see full-cycle game development.

Engine and pipeline: Unity or Unreal

Both engines ship online RPG games in production today. Unity fits mobile gacha RPGs, isometric ARPGs, and stylised co-op titles thanks to Addressables, DOTS for large enemy counts, and a lighter mobile footprint. Unreal Engine 5 fits larger 3D worlds and combat-focused ARPGs, with Nanite, Lumen, and the Gameplay Ability System reducing custom engineering on combat and rendering.

Studios that need help with either stack can bring in a specialist team from Unity game development or Unreal Engine game development. The engine decision should follow target platforms and the visual bar, not team preference.

LiveOps and monetization models for online RPG games

Online RPG games are LiveOps products. After launch, revenue and retention depend on content cadence, event design, balance patches, and player communication. The four working monetization models today are: box price plus expansions (The Elder Scrolls Online), free-to-play with battle pass and cosmetics (Lost Ark in the West), gacha (Genshin Impact, Honkai: Star Rail, AFK Journey), and subscription in narrow markets.

A live online RPG typically ships one major content patch every 4 to 8 weeks and a seasonal reset every 3 to 4 months. That cadence requires a small permanent team even after launch: producers, designers, backend engineers, community managers, and a data analyst. Studios that treat LiveOps as an afterthought lose retention within the first two seasons.

Regulatory review on gacha and loot boxes is now a mandatory step for App Store and Google Play submission. Apple publishes the current rules in the App Store Review Guidelines, and several countries (Belgium, the Netherlands) restrict gacha entirely.

A Game-Ace RPG case

One Game-Ace project that maps to online RPG production scope.

Welcome to Infowar: Shadows of the Grid, an educational MMORPG by Game-Ace

Infowar Shadows of the Grid educational MMORPG

Infowar: Shadows of the Grid uses Roblox-style visuals with Unity MMORPG mechanics to teach players aged 8 to 16 how to resist disinformation online. Game-Ace built the multiplayer gameplay, quest systems, and content pipeline, showing how MMORPG mechanics can serve a smaller-scale live game without a full sharded world.

When to talk to Game-Ace about online RPG games

The right time to talk to a partner about an online RPG is before the first vertical slice is locked. Subgenre, backend model, and monetization decisions made at that stage define the next three years of the project. Game-Ace has worked on games since 2005 with 120+ in-house specialists and 200+ shipped titles. If your online RPG is on the roadmap, the Game-Ace game development studio covers gameplay, backend, art, QA, and post-launch support from a single team. Related reading on staffing: hire game developers.

Frequently searched questions about online RPG games

The realistic budget depends on subgenre. A small co-op RPG can ship for €400,000 to €800,000. A mid-scope ARPG or mobile gacha RPG usually falls between €1.5M and €4M to soft launch. A full MMORPG rarely comes in under €5M for launch and needs a live-service budget on top. Game-Ace typically joins projects at concept or vertical slice stage and scopes cost by subgenre, backend model, and target platforms.

Timelines depend on scope. A co-op RPG can reach soft launch in 12 to 20 months. A mobile online RPG usually needs 18 to 24 months. An ARPG lands around 18 to 30 months. A full MMORPG rarely ships in under 24 to 36 months and often ships later than the plan.

The backend depends on the subgenre. Typical building blocks include authoritative game servers for MMORPGs, session brokers plus stateless servers for ARPG and co-op titles, a gacha and event ledger for mobile RPGs, and account and progression storage for every subgenre. Common infrastructure covers:

  • Authoritative world servers for MMORPGs
  • Session broker plus stateless game servers for ARPG and co-op
  • Gacha and event ledger for mobile RPGs
  • Account, character, and progression storage
  • Chat and real-time updates over WebSockets
  • Regional clusters with autoscaling
  • Observability, telemetry, and anti-cheat services

Matchmaking depends on the session model. For co-op RPGs a lobby service plus regional relay is usually enough. For ARPGs a broker that pools players by level, region, and content tier works. For MMORPGs matchmaking is limited to instanced content (dungeons, arenas) while world play uses shards. Latency budgets and cross-region rules should be decided before the first backend sprint.

Yes, if PvP scope is defined narrowly. Small-scale arena PvP (2v2, 3v3, 5v5) runs on dedicated session servers with server-authoritative combat and is manageable for a mid-size studio. Open-world PvP on MMORPG shards is a different scope and needs a full live team. Trying to add open-world PvP mid-development is one of the most common cost overruns in the category.

Unity is the default choice for mobile online RPG games and mid-scope 2D or 3D titles because of Android hardware coverage, Addressables, and iteration speed. Unreal Engine is stronger for combat-focused ARPGs and MMORPGs where visual fidelity and animation systems matter. Neither engine solves the backend problem: the server layer is a separate stack in both cases. Game-Ace has shipped online RPG projects in both engines.

LiveOps covers seasonal events, balance patches, cosmetic drops, community response, and content roadmaps. In practice a live online RPG ships one major content patch every 4 to 8 weeks and a seasonal reset every 3 to 4 months. This requires a permanent team of producers, designers, backend engineers, a data analyst, and community managers. Studios that plan for LiveOps at concept stage retain players longer than those that treat it as a post-launch add-on.

It depends on the target market and subgenre. Gacha works for mobile and character-driven online RPG games, especially in Asia. Battle pass plus cosmetics works for ARPGs and co-op RPGs in the West. Box price plus expansions remains viable for premium MMORPG audiences. Subscription still works in narrow markets. The model has to be decided at concept, because it shapes progression, content cadence, and backend cost.
Average rating 4.5 / 5. Votes: 133
Related posts
Metahuman game character standing near realistic cars in unreal engine scene How MetaHuman changes game character development Game development for startups rocket in space Game development for startups: budget and MVP guide Tower defense games image preview Engineering tower defense games from prototype to live service Idle game development preview img Idle game development: a full production guide Gamification in recruitment preview Gamification in recruitment: what actually works
Futuristic game robot running through a purple portal
Get in touch
menu
Get in touch
Game-Ace logo loader