RO2_Server

Ragnarok Online 2 server emulator written in C# 15 / .NET 11.0.

Status

Working:

• ProudNet protocol (RSA key exchange, session encryption, heartbeat, P2P/transport RMIs)
• Login + authentication (account lookup, no auto-register) and character list / creation / selection
• World entry and UNENC game-RMI dispatch, verified against real retail captures
• Zone gameplay: movement, normal + skill combat, monster AI (proximity aggro, chase, leash/reset), drops and looting, party, chat, inventory, equipment refinement, derived stats
• Domain-driven architecture with pluggable persistence (MongoDB default; PostgreSQL and Redis providers) and a dedicated Identity bounded context

In Progress / known gaps:

• Player "in battle" stance polish (enter works; the leave/revert behaviour and weapon→stance map are unfinished)
• Broader content coverage and the ongoing hardening/verification passes

Requirements

• .NET 11.0 SDK (11.0.100-rc.3 or later until the November 2026 GA — the build gate blocks SDKs with known CVEs)
• MongoDB (running on localhost:27017 by default)
• PostgreSQL and Redis are optional (alternative persistence providers)

Building

# Kill any running server processes first (DLLs get locked), then:
dotnet build --no-restore

If the NuGet cache gets corrupted: dotnet restore --packages ".packages".

Game data

This repository does not ship the game's data tables (they are derived from the client and not ours to redistribute). Generate your own data/ from your RO2 client with the data-pipeline/ project; it writes the JSON tables the server loads into data/ (which is git-ignored). The server and the full test suite need data/ present to run; without it the data-dependent tests skip rather than fail, so a clone builds and its remaining tests pass out of the box.

Running

# Login server (port 7101)
dotnet run --project source/Hosts/RO2.Server.Login --no-build --packages ".packages"

# Zone server (port 7201)
dotnet run --project source/Hosts/RO2.Server.Zone --no-build --packages ".packages"

# Chat server (port 7401)
dotnet run --project source/Hosts/RO2.Server.Chat --no-build --packages ".packages"

Configuration

Edit config.json:

{
  "Login":    { "Host": "0.0.0.0", "Port": 7101 },
  "Zone":     { "Host": "0.0.0.0", "Port": 7201 },
  "Chat":     { "Host": "0.0.0.0", "Port": 7401 },
  "Database": { "ConnectionString": "mongodb://localhost:27017", "DatabaseName": "ro2_server" },
  "Game":     { "ExpRate": 1, "DropRate": 1, "GoldRate": 1 }
}

The client connects to the host the server advertises: the endpoint's Host, or AdvertisedHost when you set one (a 0.0.0.0 bind is advertised as 127.0.0.1). Set AdvertisedHost on Zone (and on Chat if it runs on another machine) for a LAN or public run. Login.AllowDuplicateLogin lets several clients share one account, and it is read at startup.

Architecture

A modular monolith organized by DDD bounded contexts over a shared kernel. See ARCHITECTURE.md for the layering, port, and dependency rules.

source/
  Shared/          RO2.BuildingBlocks, RO2.BuildingBlocks.Bus, RO2.GameData (game-data kernel)
  Identity/        Account / auth context       — Domain / Application / Infrastructure(+Mongo,+Postgres)
  Economy/         Mall, craft, auction, shop    — Domain / Application / Infrastructure.{Mongo,Postgres}
  Inventory/       Bags, items, sockets          — Domain / Application / Infrastructure.{Mongo,Postgres}
  Character/       Character, stats, progression — Domain / Application / Infrastructure.{Mongo,Postgres}
  Skill/           Learned skills, talents       — Domain / Application / Infrastructure.{Mongo,Postgres}
  Combat/          Cast path, formulas, gates    — Domain / Application (pure, no persistence)
  World/           Movement, warp, NPC runtime   — Domain (Application as flows are carved)
  Game/            RO2.Domain + RO2.Application — the remaining core still being carved into contexts
  Platform/        RO2.Network (wire), RO2.Persistence.{Mongo,Postgres,Redis}, RO2.Infrastructure (composition)
  Hosts/           RO2.Server.Login (7101), RO2.Server.Zone (7201), RO2.Server.Chat (7401)
tests/
  RO2.Tests/       unit + integration (Testcontainers) tests

Each carved context keeps its own Domain (entities, rules, its repository port) and Application (use-case flows + the ports they consume); persistence lives in Infrastructure.{Mongo,Postgres}; the wire layer, DI and live state stay in the hosts. Game data is not hardcoded — it is generated from the client's .tbl/XLSX tables into JSON under data/ (and data/strings/) by the data-pipeline/ project.

Documentation

The code is the reference: the handlers under src/RO2.Server.*/Handlers document the protocol messages they implement, and sample/ holds example message bodies for the login, zone and chat flows. The data-pipeline/ project regenerates the JSON under data/ from the client's data tables.

License

MIT License - see LICENSE