KeyPace

Live Mythic+ pace prediction for WoW Midnight (12.0): will this key time, +2 or +3 — answered while you still have time to do something about it.

Most timer addons tell you how much time is left. KeyPace tells you where you are going to land — and how much room you have to fix it.

Pace forecast (in-run frame)

A compact movable frame appears when the key starts and updates every half second:

• Big +3 / +2 / +1 / X forecast of the chest you are currently heading to — it flashes when the forecast changes tier.
• ETA and slack — the projected finish time and how many seconds you can still afford to lose while staying in time ("on time, spare 1:24" / "NOT in time, short 0:37").
• A time bar with the +3/+2 threshold ticks and a colored marker showing where your projected finish lands.
• Boss checkpoints: after each boss you see "boss 2: −0:41 vs +2" and the deadline for the next one ("boss 3 by 12:48"). You are always compared against runs that finished with the chest you are currently forecast for — being "on pace" for a +2 means on the pace of actual +2 runs, not an abstract average.
• Live trash % and boss count, plus the three raw pace estimates for the curious.
• Deaths and their time penalty, read live from the game (works with the tiered death penalties).
• Post-run chat summary: final time, % of timer, and per-boss checkpoint deltas — see exactly where the key was won or lost.

How the forecast works

Three independent estimates run in parallel and are combined by median, so one confused estimate can't wreck the forecast:

1. Whole-run pace — overall progress vs elapsed time.
2. Current tempo — a rolling 4-minute window, so a lull or a burst changes the forecast quickly.
3. Crowd curve — your boss-kill timings scaled against a pace curve built from thousands of recent timed runs on Logs (see PaceDB below).

The trash-vs-bosses weight of the progress model is adjustable in Settings.

Groupmate book

M+ is a game about people. KeyPace keeps your own private book of everyone you run with:

• After every completed or ruined key (depleted-and-reset, abandoned, or someone just left): rate your groupmates 0–10 and flag key-ruiners. The roster is snapshotted at key start — a ruiner who instantly leaves the group still gets remembered.
• Ratings, ruin flags and run counts appear in LFG applicant tooltips, LFG group-leader tooltips, unit tooltips and clicked player chat links — you know who you are inviting before you invite them.
• Optional announcement of the ratings you give to party chat.
• Run history (last 100 runs) with full party composition — class colors and specs — result and time.
• People tab: everyone you have run with, sorted online-first, with average rating, ruin count, runs together and last run; one-click Logs profile link, whisper and invite buttons. Online indicators cover friends, Battle.net friends and guildmates (the game does not expose online status of strangers).

All of it lives in a tabbed window (/kp or the minimap button): History / People / Settings.

Pace database

The addon ships with PaceDB.lua: per-dungeon, per-key-level percentile curves (p25/p50/p75 boss-kill timings and finish times, split by +1/+2/+3 outcome), aggregated from recent timed Logs runs. If your exact key level has no data, the nearest level with data is used. It refreshes with addon updates. Without it the live model still works — the curves are a calibration layer, not a requirement.

Built for Midnight's addon restrictions

Combat amounts (damage, healing, HP) are secret values in Mythic+ since 12.0 — no addon can do DPS math there, and KeyPace doesn't try. The model reads only what is public: scenario progress, the world timer, death count and C_ChallengeMode basics. Every read of potentially-restricted data is guarded, so the addon keeps working even if a patch moves the line.

Commands

• /kp (or /keypace) — menu: History / People / Settings
• /kp test — preview the forecast frame outside of a run
• /kp rate — rate the last recorded party
• /kp lock / /kp reset — lock or reset the frame position
• /kp wforces 0.5 — trash weight in the progress model (0–1)
• /kp db — PaceDB version and coverage
• /kp debug — diagnostic dump (run it inside a key when reporting issues)

Localization

English and Russian (ruRU).