Documentation

Description

DMK began as a set of quality-of-life improvements for the Anniversary client: replacement frames, bags, maps, and auction tools built to play with.

It then became a testbed for building with AI — a place to try ideas quickly against a real, running system, with the suite's shared libraries and data conventions keeping the experiments coherent.

It is now also a data pipeline. The suite captures gameplay data, ships it off the client into warehouses, and the analysis comes back as better decisions in game: gear, gold, and rotation min-maxing grounded in real numbers.

Feature timeline

When each feature landed. Full notes on Changelog.

Repositories

Every repo in the WoW group contributes to the suite: the addon itself, the game-data extraction that feeds its generators, the ingest pipelines that warehouse its output, and the sites that read the warehouses.

Steps

Releases are versioned zips built by package.ps1, hosted on Download; the suite version is stamped from DMK.toc, every release git-tagged, CHANGELOG.md at the repo root.

1. Get the release zip for the version you want from Download.
2. Extract into World of Warcraft\_anniversary_\Interface\AddOns — the zip carries all 21 addon folders.
3. Start the client. The TOC list is read at startup, so a running client needs a full restart, not /reload.
4. Enable the DMK addons on the character-select AddOns list.

Reload rules

Questie

Optional. Questie is the suite's one third-party runtime source: a read-only bridge in DMK_Map, toggle-gated, 150-marker cap. Without Questie the map falls back to the native quest API — nothing else in the suite notices.

AddOns folders

21 folders, one per addon, all publishing through the shared DMK namespace.

Interface\AddOns\
├─ DMK\                     core — config, profiles, UI / window-manager / form libs
├─ DMK_CharData\            data
├─ DMK_CharLogs\            data
├─ DMK_RealtimeData\        data
├─ DMK_AHSync\              data
├─ DMK_GearMGR\             data
├─ DMK_Telemetry\           data
├─ DMK_UnitFrames\          display
├─ DMK_Damage\              display
├─ DMK_DamageSimulation\    display
├─ DMK_Map\                 display
├─ DMK_MiniMap\             display
├─ DMK_Bags\                display
├─ DMK_Anchor\              display
├─ DMK_Status\              display
├─ DMK_Threat\              display
├─ DMK_AHSearch\            display
├─ DMK_Heal\                display
├─ DMK_Radar\               display
├─ DMK_Chat\                display
└─ DMK_Debug\               display

SavedVariables

Written on logout or /reload only. Data plugins own these files; display plugins read via accessors.

WTF\Account\<Account>\
├─ SavedVariables\                            account-wide
│     DMKCoreDB · DMKAHDB
└─ <Realm>\<Character>\SavedVariables\        per-character
      DMK_CharData.lua      DMKCharacterDB
      DMK_CharLogs.lua      DMKCharacterLogDB + DMKChatLogDB (chat history)
      DMK_RealtimeData.lua  DMKCombatEventsDB
      per-plugin DBs        DMKGearDB · DMKTelemetryDB · DMKDamageCharDB ·
                            DMKMapCharDB · DMKMiniMapCharDB · DMKBagsDB ·
                            DMKDamageSimCharDB · DMKAHViewDB · DMKDebugDB

Slash commands

In-game commands. Most windows toggle from the Anchor bar instead.

Pipeline

The addon never phones home — SavedVariables are picked up from disk, ingested, and only then read by AI.

Inputs

Warehouse reads: character snapshots (gear, stats, talents, professions), combat event history and fight breakdowns, gold/xp series, and current AH pricing per item and suffix.

Processing

Placeholder — describe what actually runs: models, prompts or jobs, how often, and what questions they answer against the warehouse.

Outputs

Placeholder — e.g. gear and loadout evaluation against real prices, spell-rank and rotation analysis from logged fights, upgrade paths per character.