Skip to content
All case studies
Metin2 · Server Core
2024 · 9 months

Dragon Coast

Rebuilt a crash-prone Metin2 private server into a sharded, authoritative core holding 18,000 concurrent players per world.

6x
concurrency ceiling
45ms
median tick time
0
unplanned outages since

Overview

Dragon Coast ran on heavily-modified leaked Metin2 server files. It had a passionate community, but the core buckled under load — nightly crashes capped the world at roughly 3,000 players.

The challenge

The original core was a single-threaded process with global locks and no horizontal scaling path. Every content update risked a cascade of instability, and the team had lost confidence in touching the netcode.

Our approach

  • Profiled the live core to isolate lock contention and tick-time hotspots.
  • Re-architected map simulation into shard workers with a stateless gateway tier.
  • Added authoritative movement & combat validation to close common Metin2 hacks.
  • Rolled out map-by-map behind a feature flag with instant rollback.

The results

Within one quarter, Dragon Coast held a stable 18,000 concurrent players per world with median tick time under 45ms. Content updates now ship weekly with zero-downtime deploys.

Have a server worth engineering?

Tell us where you are — a new server, a struggling live game, or a legacy core that needs rescuing. We'll tell you exactly how we'd approach it.