PeaversSplits
- By
Calls out how far ahead or behind the pace your Mythic+ run is, at every boss, while the key is still running.
PeaversSplits
A World of Warcraft addon that calls out how far ahead or behind the pace your Mythic+ run is, at every boss, while the key is still running.
Features
- A split called out at every boss, while the key is still running -- not a verdict at the end
- A live timeline of the whole key: every boss a node on one line, and you a dot travelling it, so you watch a gap open instead of being told about it once the boss is down
- Compared against your exact keystone level, never a neighbouring one
- Says "inside the usual range" when a delta lands inside the middle half of the pool -- a measurement, not a verdict
- Says plainly when your level has no published pool, and names the levels that do
- Party chat by default, "only me" available; SAY and YELL deliberately not offered
- One clock and one talker: group copies agree with each other instead of contradicting each other in chat
- Recovers from a reload mid-key, and says that it has done so
Usage
- Install it and start a key -- there is nothing to configure first
- At the start of the run it says what it is pacing you against, or that nothing is published for your level
- Watch the timeline: the dot is you, the nodes are the bosses, and the delta is written out in words as well as drawn
- Each boss death is called out in party chat with the split and the delta
/ps testshows a sample run you can drag into place;/ps configopens the settings
Pacing Murder Row +10 against the published 12.1 pool.
Kystia Manaheart down at 8:17, +0:31 vs pace, inside the usual range.
Zaen Bladesorrow down at 12:49, +0:36 vs pace, inside the usual range.
Xathuux the Annihilator down at 20:31, +1:54 vs pace.
Lithiel Cinderfury down at 28:08, +1:52 vs pace.
Key done. +1:52 at the last boss.
The live timeline
The chat line is the record; the timeline is the instrument. It runs continuously, and it holds the whole key rather than one boss at a time, so a gap is something you watch open rather than something you are told about once the boss is already down.
19:30 Next: Xathuux the Annihilator +0:53 vs pace
-----[==*===.==]-----[==.~~~~~!]------[===#==O==]------[===#==|]-----
---- the rail: the run, from the start to the last boss's pace
[==] the middle half of that boss's pool - its usual range
# a boss still ahead of you: its published pace
. the pace of a boss already down, stepped back
* it died there, ahead of that pace
! it died there, behind it
~ the gap between the two, drawn to scale - that IS the delta
O you, right now
| the last boss's pace: the end of the line
Point at any boss for its name, its pace, when it died, and how many runs the figure rests on.
The scale is fixed - it does not grow to fit an overrun, because a track that rescales keeps the dot in the same place while the numbers get worse, which is the opposite of what an instrument is for. Past the right edge it saturates and the text carries the number.
Ahead is the theme accent, behind is red, and the delta is written out in words - a display that only says "bad" in red says nothing at all to a reader who cannot see the difference. The geometry says it a third time: a kill drawn to the right of its pace node is late, whatever colour anybody's monitor makes of it.
Drag to move, lockable, and its length is a setting - the whole key shares one axis, so a short frame packs the bosses into a row of touching blocks. It hides itself whenever there is no pace to race: a rail with one dot sliding along it and no bosses on it is not an instrument.
No panel behind it by default. This is a line drawn over the world, not a window, and a box around forty pixels of instrument is mostly box. The line keeps its own slim ground and the text is shadowed, so the greys stay readable against whatever is behind them; the panel is there in the settings for anyone who wants the frame back.
Why the deadline is not drawn on it
The obvious finish line is the dungeon's own time limit, and it is deliberately absent. The keystone timer carries the death penalty; no published split carries any. Drawing the two on one axis would put the deadline five seconds per death away from the truth, always in the same direction, with nothing about it looking wrong. The last boss's pace is the end of the run that can honestly be compared - the same reason the end-of-run line sums up at the last boss rather than at the portal.
Why splits and not the timer
A split is the time from the start of a run to a boss dying. The dungeon timer is a single deadline at the very end: it is the truth, and it arrives too late to do anything about. A split is the same truth, available at the second boss, while the group can still choose a different route or stop chain-pulling.
What it compares against
The published pool from parses.gg, shipped in PeaversSplitsData: for every dungeon in the current season and every exact keystone level with enough runs behind it, the median time to each boss, plus the middle half of the pool.
Your exact keystone level, never a neighbouring one. Enemy health scales per level, so a +14 held against the +12 pool would be told it is behind a pace nobody at +14 ever set - plausible, wrong in one direction, and with nothing about it looking wrong. If your level has no published pool the addon says so and names the levels that do, rather than reaching sideways:
No pace published for Murder Row +14 yet. Levels with data: 7, 9, 10, 11, 12.
Splits are still called out on an uncovered level. They are a fact about your run and do not need anybody else to have done the dungeon.
"inside the usual range"
The pool carries its interquartile range as well as its median. A delta of forty seconds means very little on a boss where the middle half of the pool spans four minutes, so a split landing inside that range says so. It is the difference between a measurement and a verdict, and it is on by default.
Commands
| command | what it does |
|---|---|
/ps or /ps status |
what is loaded, what is running, and what it is being paced against |
/ps test |
show/hide the sample run, for dragging the timeline into place |
/ps config |
settings |
Notes on the clock
The split is measured from CHALLENGE_MODE_START with the addon's own
stopwatch, because that is exactly the quantity the published benchmark was
built from - real elapsed seconds, with no death penalty in it. Reading the
penalised figure instead would drift the delta by five seconds per death, always
in the same direction, and read as a group that got slower.
Reloading mid-key is recovered from: the addon adopts the run in progress and falls back to the game's own keystone timer, and says that it has done so.
Configuration
/ps config (or PeaversConfig) offers: announcements on/off and the channel,
the interquartile spread, sample size, the start-of-run and end-of-run lines,
group sync, and the live timeline (show, lock, position, length, panel).
Party chat is the default, because a split is a fact about the group's run. "Only me" is available. SAY and YELL are deliberately not offered - they reach everyone standing nearby, none of whom installed this.
Outside a group, and whenever the channel is unavailable, the line goes to your own chat frame instead of being dropped.
Installation
Recommended: PeaversUpdater
Download and install PeaversUpdater, the desktop updater for the whole Peavers collection. It installs PeaversSplits together with its required dependencies and delivers updates before they reach CurseForge.
Alternative: CurseForge
- Download from CurseForge
- Ensure PeaversSplitsData is also installed
- Ensure PeaversCommons is also installed
- Ensure PeaversConfig is also installed
- Enable the addon on the character selection screen
Part of the Peavers addon collection · Report an issue · Support development on Patreon
PeaversSplits Team
Owner
