Skip to content

Data Extraction

Jacob Bowen edited this page Mar 8, 2026 · 1 revision

Data Extraction

The Data Extraction page manages the client data files (DBC, Maps, VMaps, MMaps) that AzerothCore needs to run.


What is client data?

AzerothCore requires extracted data from a World of Warcraft 3.3.5a (build 12340) client:

Data type Contents Approx. size
DBC Client database files (spells, items, zones, …) ~300 MB
Maps World geometry/height maps ~400 MB
VMaps Visual mesh maps (line-of-sight) ~500 MB
MMaps Movement/pathfinding maps ~6 GB

Option A: Download Pre-Extracted Data (Recommended)

Click Download Data to fetch a pre-built archive directly from AzerothCore's GitHub releases. This is the easiest option and does not require a WoW client.

  • Size: approximately 1.5 GB (DBC + Maps + VMaps; MMaps may be separate)
  • Time: 2–10 minutes depending on your connection
  • Progress is shown via a live SSE stream

The data is saved to the Data Dir configured in Settings.


Option B: Extract from Local WoW Client

If you have a WoW 3.3.5a (build 12340) client installed:

  1. Set CLIENT_PATH in your root .env to the WoW client directory.
  2. Restart the panel containers: make docker-restart
  3. On the Data Extraction page, select which data types to extract.
  4. Click Extract.

MMaps: Generating movement maps can take 30–60 minutes and is off by default. Only enable it if you need pathfinding (required for dynamic NPC pathing).

Extraction options

Option Notes
Extract DBC Always required
Extract Maps Always required
Extract VMaps Required for line-of-sight calculations
Generate MMaps Optional; very long processing time

Extraction Status

The status panel shows:

Field Description
in_progress Whether an extraction is currently running
current_step The active extraction step
progress_percent Estimated progress
has_dbc Whether DBC files are present
has_maps Whether map files are present
has_vmaps Whether vmap files are present
has_mmaps Whether mmap files are present
data_present True if DBC + Maps are present (minimum requirement)

Cancelling an Extraction

Click Cancel to abort a running extraction. Partially extracted files are left in place — re-running the extraction will overwrite them.


API Endpoints

Method Path Description
GET /api/v1/data-extraction/status Get extraction status and data presence
POST /api/v1/data-extraction/download Download pre-extracted data (SSE stream)
POST /api/v1/data-extraction/extract Extract from local WoW client (SSE stream)
POST /api/v1/data-extraction/cancel Cancel running extraction

Example: Extract from local client

POST /api/v1/data-extraction/extract
Authorization: Bearer <token>
Content-Type: application/json

{
  "client_path": "/root/wow-client",
  "extract_dbc": true,
  "extract_maps": true,
  "extract_vmaps": true,
  "generate_mmaps": false
}

Troubleshooting

"Client path not found"

  • Ensure CLIENT_PATH in .env is correct and the directory is bind-mounted before the containers are started.
  • The path must contain the WoW 3.3.5a executable (Wow.exe or similar).

Download stalls or fails

  • Check the panel server has internet access.
  • Try re-running — the download uses a direct HTTP fetch from GitHub releases.

Server won't start after extraction

  • Make sure DBC and Maps are both present.
  • Ensure the Data Dir in Settings matches where the data was extracted to.
  • Check the worldserver log on the Log-Viewer page for ERROR: Could not find DBC file messages.

Clone this wiki locally