Know exactly how much enemy forces you need before every boss — never overpull, never underpull.
What it does
MythicPlusPercentHelper watches your Mythic+ enemy-forces bar and tells you, live, whether you're ahead or behind the pace you need to clear the dungeon. It learns your checkpoints automatically from the runs you play — no config, no manual entry.
Features
- Auto-learned checkpoints — after each key, the addon records the enemy-forces % banked before each boss and keeps your leanest (most efficient) run as the target.
- Route-aware — dungeons with more than one viable boss order are tracked as separate routes, keyed by kill order, so pacing advice always matches the path you're actually on.
- Ambiguity handling — early in a run, when more than one learned route is still possible, you get one line per candidate route until the kill order rules the rest out.
- Live pace readout — a clean on-screen card shows current forces %, the next checkpoint's boss and minimum, and a status like
+3.7% aheadorSHORT 2.1%. - Pull breakdown —
/pt pathlists every recorded pull in order with the % it was worth, so you can see which packs were worth taking. - Editable checkpoints — the options panel lists every learned route per dungeon; edit a value directly to lock it and pause auto-learning for that route.
- Movable, lockable display and a self-contained minimap button — no external libraries required.
Slash commands
| Command | Effect |
|---|---|
| /pt | Open settings |
| /pt unlock · lock | Move the on-screen card |
| /pt show | List recorded routes for the current dungeon |
| /pt routes | Compare every learned path, leanest first |
| /pt path · path best | Per-pull breakdown of the current or leanest run |
| /pt last | Summary of your most recent run |
| /pt minimap | Toggle the minimap button |
| /pt reset · resetall | Clear learned data for one or all dungeons |
Notes
Checkpoints improve the more you play — your first clear of a dungeon has nothing to pace against yet, so the card shows live % only until a route is learned. Positions can't be pinned to the map (Blizzard doesn't expose player coordinates inside instances), so pacing is entirely %-based by design.

