wow-midnight-server

WoW Midnight Server

WoW Midnight Server — TrinityCore 12.0.7 (build 68275)

A documented, community-maintained World of Warcraft: Midnight private server built on TrinityCore master, at the current retail build 12.0.7.68275 — plus a set of original server-side fixes that make the newest content actually playable.

🌐 Language: English · Русский

⚠️ Read first: this repo contains documentation + our original fixes only. It does not include the game client, game data, or a world database — those are Blizzard’s property and cannot be redistributed. You build those yourself from your own retail client. See DISCLAIMER.md.


What makes this project different

Most public WoW private servers run old expansions (Wrath 3.3.5a, Cata, MoP…). This one targets current retail — patch 12.0.7 “Midnight” and is kept honest and playable:

  This project Typical private server
Client build 12.0.7.68275 (Midnight, current retail) 3.3.5a / 4.3.4 / 5.4.8
Races All 26 incl. allied races unlocked, Dracthyr Evoker intro working Classic races only
Content span Vanilla → Midnight in one DB, 517 maps populated Single-expansion
Companion bots Creature bots (.bot) + fake-player bots (.pbot) Usually none / 3rd-party only
Data policy Maximized to the public-data ceiling, gaps documented honestly Often silently broken
Fixes Curated, reversible, ID-band-safe community fixes (this repo) Ad-hoc

Highlights


Content at a glance (verified DB counts)

Metric Count
Quests 48,257
Quest objectives 61,101
Quest starters / enders (NPC) 27,694 / 34,524
Creature templates / spawns 227,684 / 733,928
GameObject templates / spawns 89,967 / 197,724
Maps with spawns 517
Loot table rows 3,084,867
Vendor rows 172,414
Retail build 12.0.7.68275

Content statistics

Architecture

Architecture

In-game screenshots

These are placeholders — drop your own real gameplay screenshots into assets/screenshots/ and they’ll show up here. (We ship no Blizzard game imagery; see DISCLAIMER.)

No screenshots yet — contributions welcome.

Two ways to install

  Path Guide
🛠 Manual Build & run on the host directly this branch — docs/en/SETUP.md
🐳 Docker Compose Everything in containers, fixes auto-applied docker branch

Both lead to the same server. Either way you supply your own client-extracted data and world DB (Blizzard’s property — see DISCLAIMER).

Quick start (manual)

  1. Build the core — TrinityCore master. → docs/en/SETUP.md
  2. Extract game data from your own retail client (maps/vmaps/mmaps/dbc).
  3. Import the world DB and run worldserver + bnetserver.
  4. Apply the community fixes in sql/. → sql/README.md
  5. Connect your client. → docs/en/CONNECT.md

Full walkthrough: docs/en/SETUP.md · Features & content: docs/en/FEATURES.md · Fix details: docs/en/FIXES.md


Repository layout

.
├── README.md / README.ru.md      Project overview (EN / RU)
├── DISCLAIMER.md                 Legal — what we can and cannot ship
├── LICENSE                       MIT (original materials only)
├── docs/
│   ├── en/  SETUP · CONNECT · FEATURES · FIXES
│   └── ru/  SETUP · CONNECT · FEATURES · FIXES
├── sql/                          Community fix SQL (reversible, ID-band-safe)
└── scripts/                      vmssh.py (env-var creds) · apply_fixes.sh

Contributing

Issues and PRs welcome — especially additional reversible, ID-band-safe data fixes for the newest content. Please never commit secrets or Blizzard game assets (the .gitignore guards against both). See DISCLAIMER.md.

Credits

Built on TrinityCore (GPL-2.0). World of Warcraft® © Blizzard Entertainment. Fan, non-commercial, educational project.