WoW Files Emulation ops console
12 / 12
Stable branch Core · 3.3.5a Patch 3.3.0

Wrath of the Lich King

3.0.2 — 3.3.5

The reference branch. The 3.3.5a tree carries the largest module set we maintain, which makes it the usual starting point for a new realm.

Fan-favorite patch · Patch 3.3.0
Fall of the Lich King

Icecrown Citadel, cross-realm dungeon queueing, and the single most re-implemented raid script in emulation history.

Read build notes

Server core

Codebase
WF Core · Northrend branch

C++20 · protocol build 12340

Database schema
Complete + modular

Base DB plus 200+ community modules applied as SQL overlays.

Custom C++ scripting
Module API (hot-swappable)

Scripts live outside the core tree and link at build time.

Anti-cheat compatibility
Warden + anticheat module

Movement, teleport, and speed detection with per-realm thresholds.

Build stability
5 / 5

The most battle-tested build target available.

Test realm telemetry

Test realm · refreshes every 3s
21ms
Test-realm latency
48ms/tick
World update interval

Diff stays under the 100 ms warning threshold.

99.97%
30-day uptime

Measured on the public test realm.

3,410
Peak concurrent testers

Highest simultaneous session count this month.

Recommended Linux host
OS
Ubuntu 24.04 LTS
CPU
6 vCPU @ 3.8 GHz
Memory
16 GB
Storage
80 GB NVMe
Database
MySQL 8.0
Recommended Windows host
OS
Windows Server 2022
CPU
8 core @ 3.8 GHz
Memory
24 GB
Storage
120 GB SSD
Database
MariaDB 11.4

Environment showcase

One plate per notable tier

Deployment tiers

Pick one, then open the setup sheet
≈ 15 minutes

Quick-start repack

Prebuilt core with a seeded database. Fastest way to see a realm come up, hardest to keep current.

  • Binaries and world database ship together
  • One config file to edit before first launch
  • You still extract maps and DBC from your own client
  • Fixes arrive only when a fresh repack is issued
≈ 2 hours

Full source build

Compile the core yourself. Slower to start, and the only tier where you can patch and contribute back.

  • Unpack the source bundle and verify its checksum
  • CMake configure, then build with your own flags
  • Apply SQL updates in order on every pull
  • Custom C++ modules compile into your binary
≈ 40 minutes

Container stack

Core, database, and auth server as separate services. Best fit if you plan to run more than one realm.

  • Compose file brings up worldserver, authserver, and MySQL
  • Volumes keep DB and extracted data across rebuilds
  • Same stack runs on a laptop and on a host
  • Higher memory floor than a bare-metal build

How a realm fits together

Deployment topology
topology · authserver + worldserver + mysql Diagram
Deployment topology
Deployment topologyWhat talks to what once a realm is up: the client reaches authserver on 3724, receives a realm list, then connects to worldserver on 8085. All three schemas sit in one MySQL instance.