Official development showcase

ROYAL CITY RP

Your city. Your career. Your story.

A standalone mobile open-world multiplayer roleplay game for Android and iOS, designed Arabic-first for the Middle East and North Africa.

Development status: awaiting owner verification

  • Android · iOS
  • Arabic-first · RTL
  • Concept artwork, not an in-game screenshot
Scroll
  • 15Game systems
  • 8Factions
  • 4Deployment phases
  • 5Next priorities

Scope counts from the project brief, not progress.

Live game status

  • Server statusComing soon
  • Players online—
  • Registered players—
  • Servers available—

The live game connection is not set up yet. Nothing on this panel is estimated or placeholder data.

01 — The project

A city built for Arabic-speaking players

Royal City RP is a mobile roleplay world designed around the Arabic-speaking gaming community.

Project vision

Royal City RP is a standalone, mobile-first open-world roleplay game. Players live out careers, rivalries and stories inside one persistent shared city.
Named in project brief

Long-term objectives Proposed / recommendation

  1. Deliver a stable, secure and playable city on both Android and iOS.
  2. Roll the game out in four staged deployment phases, from a staff alpha to a commercial release.
  3. Run the community under a clear nine-tier administrative hierarchy with auditable staff actions.
  4. Keep an Arabic-first experience with proper right-to-left layout throughout.
  • Target audience

    Arabic-speaking gamers, particularly across the Middle East and North Africa.

    Named in project brief
  • Supported platforms

    Android and iOS mobile devices.

    Named in project brief
  • Localization strategy

    Arabic is the primary language with full right-to-left support. English is the secondary language.

    Named in project brief
  • Core gameplay concept

    An open-world multiplayer roleplay city where civilian, lawful and criminal careers share one persistent world.

    Named in project brief
  • Project category

    Standalone mobile open-world multiplayer roleplay game.

    Named in project brief

How to read this site

Every claim is tagged with where it comes from. Nothing is presented as verified unless the owner has confirmed it.

  • Named in project briefListed in the project brief as coming from the specification. The specification file itself has not yet been cross-checked.
  • Owner confirmedConfirmed by the project owner.
  • Proposed / recommendationA future plan or recommendation, not an established fact.

02 — Development status

Where the project honestly stands

Statuses are read from one data file. Anything not yet reported is shown as awaiting confirmation. No percentages, dates or counts are invented.

Overall project status

The scope of the project is defined, but no system has yet had its implementation status confirmed.

15 systems · Awaiting confirmation: 15

What is known

  • The project is a standalone mobile open-world multiplayer roleplay game for Android and iOS.
  • Fifteen game and platform systems are named in the project brief.
  • Eight factions are named.
  • Four deployment phases are proposed as a strategy, without calendar dates.
  • Five next technical priorities are listed and treated as outstanding.

Still requires confirmation

  • The current implementation status of every system. No status has been reported yet.
  • Whether any system has passed testing, and what evidence exists.
  • Whether the server infrastructure has been deployed.
  • Target dates, budget and player numbers.

Systems by status

Implemented

0

None reported

Tested and verified

0

None reported

Partially implemented

0

None reported

In development

0

None reported

Planned

0

None reported

Pending verification

0

None reported

Awaiting confirmation

15
  • Multiplayer client–server architecture
  • Character accounts and authentication
  • Character state persistence
  • Vehicles and ownership
  • Housing and real estate
  • Commercial businesses
  • Jobs and employment
  • Banking and financial transactions
  • Player inventory
  • Police and law enforcement
  • Military operations
  • Medical services
  • Federal investigations
  • Administrative tools
  • Anti-exploit and security systems

03 — Game systems

Fifteen systems, one persistent world

A system being described does not mean it is operational. Each card shows its status and what must still be validated.

15 systems shown

Multiplayer client–server architecture

What it does
Mobile clients connect to the Royal City core server, which keeps the shared world synchronized between connected players in real time.
Role in gameplay
Underpins every interaction: movement, vehicles, jobs, emergency response and faction operations all depend on it.
Validation still required
Multi-client stress testing under simulated high-latency mobile connectivity is outstanding (milestone 3).
Documented statusAwaiting confirmationNamed in project brief

Character accounts and authentication

What it does
Players sign in and manage their roleplay characters through authenticated sessions.
Role in gameplay
Ties every character, asset and faction role to a verified player identity.
Validation still required
Session-management behaviour and account-security checks await confirmed test evidence.
Documented statusAwaiting confirmationNamed in project brief

Character state persistence

What it does
Character data is stored in a persistent relational database so progress survives disconnects and server restarts.
Role in gameplay
Makes the world continuous: money, property and standing carry from one session to the next.
Validation still required
Data integrity, backup/recovery and concurrent-write behaviour need verification.
Documented statusAwaiting confirmationNamed in project brief

Vehicles and ownership

What it does
Players can purchase and own vehicles, with ownership recorded against their character.
Role in gameplay
Provides mobility and status, and supports jobs, customization and law-enforcement scenarios.
Validation still required
Purchase, ownership-transfer and persistence flows await verification.
Documented statusAwaiting confirmationNamed in project brief

Housing and real estate

What it does
Characters can acquire residential property inside the city.
Role in gameplay
Gives characters a home base and a long-term investment within the economy.
Validation still required
Property purchase, access rules and persistence await verification.
Documented statusAwaiting confirmationNamed in project brief

Commercial businesses

What it does
Player-run commercial businesses operate as part of the city economy.
Role in gameplay
Creates player-driven commerce and employment opportunities for other players.
Validation still required
Business creation, income handling and ownership persistence await verification.
Documented statusAwaiting confirmationNamed in project brief

Jobs and employment

What it does
Characters can take lawful or illicit work, from civilian trades to faction roles.
Role in gameplay
Drives income, daily activity and the interaction between different groups of players.
Validation still required
Individual job loops, payouts and balancing await verification.
Documented statusAwaiting confirmationNamed in project brief

Banking and financial transactions

What it does
Characters hold bank balances and can move money through transfers and purchases.
Role in gameplay
Connects every earning and spending activity, so it is the backbone of the economy.
Validation still required
Transaction integrity, duplication safeguards and audit trails await verification.
Documented statusAwaiting confirmationNamed in project brief

Player inventory

What it does
Characters carry and manage items.
Role in gameplay
Supports trade, work tasks and day-to-day roleplay.
Validation still required
Item handling, limits and anti-duplication checks await verification.
Documented statusAwaiting confirmationNamed in project brief

Police and law enforcement

What it does
The Los Santos Police Department (LSPD) faction enforces law and order in the city.
Role in gameplay
Provides the lawful counterpart to criminal organizations and drives pursuit and investigation roleplay.
Validation still required
Faction tools, application handbook and conduct documentation are outstanding (milestone 4).
Documented statusAwaiting confirmationNamed in project brief

Military operations

What it does
The Military Forces faction carries out organized operations within the world.
Role in gameplay
Adds structured, command-driven roleplay and large-scale scenarios.
Validation still required
Faction tools, application handbook and conduct documentation are outstanding (milestone 4).
Documented statusAwaiting confirmationNamed in project brief

Medical services

What it does
The Medical Coalition faction provides emergency medical response and treatment.
Role in gameplay
Gives players a cooperative, life-saving role and a reason for emergency response across the city.
Validation still required
Faction tools, application handbook and conduct documentation are outstanding (milestone 4).
Documented statusAwaiting confirmationNamed in project brief

Federal investigations

What it does
The Federal Investigation Bureau (FIB) faction handles serious and long-running investigations.
Role in gameplay
Supports in-depth investigative storylines above the level of everyday policing.
Validation still required
Faction tools, application handbook and conduct documentation are outstanding (milestone 4).
Documented statusAwaiting confirmationNamed in project brief

Administrative tools

What it does
A nine-tier staff hierarchy uses game-master (GM) commands to moderate and manage the live world.
Role in gameplay
Keeps the community fair and the economy healthy, with accountability for staff actions.
Validation still required
GM audit logging with Discord webhook integration and published permission matrices are outstanding (milestones 1–2).
Documented statusAwaiting confirmationNamed in project brief

Anti-exploit and security systems

What it does
Server-side validation and anti-exploit controls protect the game state from tampering.
Role in gameplay
Protects fair play and the integrity of the economy and character data.
Validation still required
Independent security testing and test evidence have not been reported.
Documented statusAwaiting confirmationNamed in project brief

04 — Factions

The factions of Royal City

Eight factions shape life in Royal City.

  • Police Department

  • Army

  • FBI

  • Government

  • Medical Services

  • Media

  • Mechanics

  • Restaurants

05 — Economy and jobs

A living economy that persists

From a roadside restaurant to a criminal organization, careers feed one shared economy.

Why persistence matters

Money, property and careers are linked through one persistent character record. What a character earns, owns and spends is stored, so the economy carries from one session to the next.

  1. 1Earn
  2. 2Bank
  3. 3Spend and own
  4. 4Persist

Conceptual flow written for this showcase, not a documented game formula.

Civilian businesses

Everyday commercial activity run by players.

Awaiting confirmation

Restaurants and retail

Food service and shops that serve other players.

Awaiting confirmation

Mechanics and vehicle customization

Repair and personalization services for vehicles.

Awaiting confirmation

Journalism and media

Reporting and media roleplay inside the city.

Awaiting confirmation

Legal employment

Lawful professions and employer-based work.

Awaiting confirmation

Private enterprises

Player-owned companies beyond the basic business.

Awaiting confirmation

Criminal organizations

Illicit groups that compete with lawful factions, overseen by dedicated staff supervisors.

Awaiting confirmation

Banking and transfers

Balances and money transfers between characters.

Awaiting confirmation

Vehicle purchases

Buying vehicles and recording ownership.

Awaiting confirmation

Real estate

Buying and holding property.

Awaiting confirmation

Implementation status of every component below needs confirmation.

06 — Technical architecture

From phone to database

The documented design links mobile clients to a core server and a persistent database through a network layer.

Royal City RP documented architectureMobile clients (Android, iOS) connect through a network layer to the Royal City core server, which stores state in a persistent relational database.Player input and world stateValidated requests and updatesPersistent reads and writes01Mobile clientsAndroidiOS02Network communication layerReal-time sync · HTTPS APIs · gRPC03Royal City core server infrastructureAuthentication · sessions · validation · anti-exploit04Persistent relational databaseCharacter and world stateReal-time synchronizationHTTPS APIsgRPC interfacesAuthentication and sessionsServer-side validationAnti-exploit controlsPersistent player dataDOCUMENTED DESIGN · DEPLOYMENT UNVERIFIEDDocumented in the project briefDeployment and testing: no evidence supplied
  1. 1. Mobile clients
    • Android
    • iOS
  2. 2. Network communication layerReal-time sync · HTTPS APIs · gRPC
    • Real-time synchronization
    • HTTPS APIs
    • gRPC interfaces
  3. 3. Royal City core server infrastructureAuthentication · sessions · validation · anti-exploit
    • Authentication and sessions
    • Server-side validation
    • Anti-exploit controls
  4. 4. Persistent relational databaseCharacter and world state
    • Persistent player data
Documented design only. No evidence has been supplied that this infrastructure is deployed or has been independently tested.Download diagram (SVG)

Documented components Named in project brief

Real-time network synchronization

Keeps all connected players looking at the same world state.

HTTPS APIs

Request/response interfaces carried over encrypted connections.

gRPC interfaces

Structured service-to-service and client-to-server calls.

Authentication and session management

Identifies each player and controls the lifetime of their session.

Persistent player data

Character, asset and financial records stored relationally.

Server-side validation

The server checks client actions instead of trusting them.

Anti-exploit controls

Safeguards against cheating and economy abuse.

Security overview

This page describes the security model at a high level only.

Documented controls

  • Server-side validation of client actions
  • Authenticated sessions for every player
  • Anti-exploit controls on the economy and world state
  • Audit logging of GM commands (outstanding)

Deliberately withheld

Credentials, API keys, server addresses, database details and detection logic are deliberately not published here, in the PDF, or in this repository.

07 — Development roadmap

Four phases to release

A proposed deployment strategy that widens access step by step.

The four phases are a proposed deployment strategy. No calendar dates have been confirmed and no phase is recorded as complete.

Phase 1

Staff Closed Alpha

ProposedDate to be confirmed

Objective
Let the internal staff exercise the core systems and administrative tooling before anyone outside the project sees the game. Proposed / recommendation
Target participants
Project staff and administrators
Main deliverables
Awaiting confirmation
Entry requirements
GM audit logging with Discord webhooks and published permission matrices (milestones 1–2). Recommendation
Exit criteria
Awaiting confirmation
Current status
Proposed

Phase 2

Creator Preview

ProposedDate to be confirmed

Objective
Give invited content creators early access to gather feedback and begin building awareness. Proposed / recommendation
Target participants
Invited content creators
Main deliverables
Awaiting confirmation
Entry requirements
Alpha findings addressed; faction handbooks and conduct documentation finalized (milestone 4). Recommendation
Exit criteria
Awaiting confirmation
Current status
Proposed

Phase 3

Public Beta

ProposedDate to be confirmed

Objective
Open the game to a wider public audience to test scale, stability and moderation. Proposed / recommendation
Target participants
Public players
Main deliverables
Awaiting confirmation
Entry requirements
Multi-client network stress test under simulated high-latency conditions completed (milestone 3). Recommendation
Exit criteria
Awaiting confirmation
Current status
Proposed

Phase 4

Commercial Release

ProposedDate to be confirmed

Objective
Launch the full release to the Arabic-speaking market on Android and iOS. Proposed / recommendation
Target participants
General public
Main deliverables
Awaiting confirmation
Entry requirements
Beta exit criteria met and target dates established (milestone 5). Recommendation
Exit criteria
Awaiting confirmation
Current status
Proposed

08 — Next milestones

The next five technical priorities

These remain outstanding until the owner supplies evidence of completion.

Outstanding 5

  • 1

    Complete GM command audit logging and Discord webhook integration

    Every GM command must leave a traceable record that is delivered to the staff Discord through webhooks.

    Area Administration

  • 2

    Publish detailed permission matrices for all nine administrative tiers

    Document exactly which command categories each tier may use.

    Area Governance

  • 3

    Execute multi-client network stress testing under simulated high-latency mobile connectivity

    Prove that many simultaneous mobile clients stay in sync when the connection is slow.

    Area Engineering

  • 4

    Finalize faction application handbooks and player conduct documentation

    Give players and faction leaders a written standard for applying and behaving.

    Area Community

  • 5

    Establish target dates for the four deployment phases

    Turn the proposed strategy into a dated plan.

    Area Project management

In progress 0

  • Nothing reported

Completed 0

  • Nothing reported

10 — Documentation

Everything in one place

Jump to any part of the project documentation, or download the executive report.

Executive project and development report

A formal overview for developers, staff, partners and investors, generated from the same data as this site.