Changelog

All notable changes to Boonkeeper are recorded here. The format follows Keep a Changelog, and the versions are semantic.

The version that counts is the one in Boonkeeper.toc; this file explains it.

[Unreleased]

[0.2.1] - 2026-09-08

Fixed

• The in-client self-test no longer fails itself after narrowing the amber/red thresholds in Options — it was judging the severity fixtures against the shipped defaults instead of your own settings.
• The in-client self-test no longer fails the target-badge check when nothing friendly is targeted, which is the common case before a pull.

[0.2.0] - 2026-09-05

Changed

• Eligible friendly players now always show their buff count. The configurable visibility threshold was removed after field feedback showed that hiding roomy counts obscured the addon's basic behaviour. Untrusted nameplates remain silent, while a targeted or hovered stranger still gets the honest ?.
• The addon window now sizes itself for each tab, keeps Options contained in its widescreen panel, orders tabs explicitly, and calls the former Test tab Simulation.
• Broker clicks now match the rest of the addon: left-click toggles the window and right-click opens a menu for Options, Simulation and About on clients that provide MenuUtil.

Fixed

• Surface controls in Options share a consistent left edge instead of drifting across the panel.

[0.1.0] - 2026-09-05

Initial release candidate. Classic Era only, deliberately — the 32-buff cap and the world-buff economy that make this addon worth having are Classic facts.

Added

• Boonkeeper's own shield icon. The AddOns list, broker displays and CurseForge project use the same dark-blue shield protecting a golden boon.
• The count on friendly nameplates. A small badge over the bodies in front of you, which is what healing without raid frames actually looks like. Friendly players only, never your own plate, and switchable on its own in the options tab.
• Every count follows the person. The target badge, nameplate badges and mouseover line keep up as buffs land and drop, at most four times a second.
• Quiet when it does not matter. The count appears from a configurable amount of room down, five slots by default. Your target and mouseover still answer ? when their auras cannot be read; nameplates stay silent so every stranger in a city does not wear a question mark.
• A slot count on the target frame. 28/32 beside the portrait of the unit you are about to heal, so "is there room" is a glance instead of a count.
• The same count on mouseover. A line on the unit tooltip, so a healer click-casting off raid frames or nameplates gets the number without changing target. Friendly players only, and it shows ? for anyone outside your group exactly as the target frame does.
• Colour that escalates. Quiet while there is room, amber at 5 slots of headroom or fewer, red at 2 or fewer. Both thresholds are settable.
• It knows what is at stake. A Classic world buff near the cap is a different warning from a full bar of flasks, and gets one severity step more. A raider carrying a Chronoboon has already stored their buffs and is treated as safe — the guild rule "no Renew while unbooned", expressed as code rather than as a raid-chat reminder.
• A cast warning. A line in chat when the cast you just sent is what knocks a world buff off. It fires at UNIT_SPELLCAST_SENT, which is the earliest the client will say anything: for a cast with a bar there is still time to stop, and for an instant there is not — knowing you just spent somebody's Rallying Cry is how the next pull goes differently. One warning per target per spell, because the second line is already noise.
• A broker entry. Publishes to any LibDataBroker display (Sigil, Titan) that is already running. No library is bundled; if nothing is listening, nothing happens.
• An options tab — /boon options. Each surface switches off independently, both thresholds step (and clamp against each other in front of you), and the list of buffs worth protecting takes your own additions and lets you switch shipped ones off. Preferences persist across /reload and survive a hand-edited or out-of-date saved file.
• /boon probe — dumps exactly what aura data this client hands an addon, per unit, including whether that unit is one Blizzard serves fully. It exists because the question is not settled by the documentation, and the answer has to come from a raid rather than from a test.
• /boon test — walks the badge through every state it can be in, so the display can be eye-verified without waiting for the right raid.
• /boon about — who made it, and an in-client self-test that answers the questions the offline tests structurally cannot. Its result is written to BoonkeeperDB, so it can be read off disk.

The rule this release is built on

Boonkeeper never shows a number it cannot stand behind. Blizzard serves a full aura list only for you, your party and your raid. For anyone else a list still arrives, still looks perfectly ordinary, and may be missing the world buff that was the entire reason to look — so Boonkeeper refuses to count it, does not claim "no world buffs seen", and shows ?. A truncated list reported as a count would be a confident lie at the exact moment somebody is deciding whether to cast, which is worse than having no addon at all.

Known limits

• The count is claimed only for yourself and your group. Strangers read ?. Whether that gate can be widened is an open question that a raid has to answer, not a test.
• Hostile debuff slots (16) are not counted yet.