Minimap Button Collector

v2.2.0 (2026-08-18)

Full Changelog Previous Releases

• chore: prepare v2.2.0 — changelog entry for LibDBIcon-named button detection (#11)
  Co-authored-by: Claude Opus 5 (1M context) noreply@anthropic.com
• fix: detect minimap buttons named after LibDBIcon but not registered with it (#10)
  Method Raid Tools names its button LibDBIcon10_MethodRaidTools so that
  name-scanning collectors pick it up, but its LibDBIcon registration sits
  commented out. The button fell between our two passes: absent from
  lib.objects, and skipped by the ^LibDBIcon10_ name filter in the frame
  walk. The walk now asks the registry which frames it actually owns instead
  of trusting the name, so these buttons are collected as regular
  minimap-child entries and released back to the minimap by point.
  Two adjacent gaps fixed in the same pass, since both block the same family
  of hand-rolled buttons:
  • The walk only looked at direct children of Minimap, never
    MinimapBackdrop.
  • The clickability test used HasScript("OnClick"), which answers whether a
    widget type supports the script rather than whether a handler is set, so
    Frame-based buttons driven by OnMouseUp were rejected regardless of what
    they had wired up.
    Buttons their own addon is currently hiding are no longer collected:
    collecting one put back on screen exactly what the user had asked to
    remove, and adoption replaces Show() so the owning addon could not take it
    back.
    Adds /mbc scan-debug, which reports every frame the scan examined, under
    which parent, and either that it was collected or the specific reason it
    was not, so a "MBC does not detect X" report becomes a single paste.
    Adds tests/test_detection.lua, which stubs enough of the WoW API to load
    Core.lua and drive a scan against fake minimap children, locking in the
    Method Raid Tools case and the surrounding guards.
    Co-authored-by: Claude Opus 5 (1M context) noreply@anthropic.com
• docs: add before/after comparison GIF to README (#9)
  Replaces the demo GIF placeholder with a side-by-side
  "Without MBC / With MBC" visual that conveys the
  problem-solution at a glance, before the prose in ## Why.
  Co-authored-by: Claude Opus 4.7 (1M context) noreply@anthropic.com
• docs: drop version labels from README roadmap (#8)
  Planned items no longer pin themselves to specific version numbers (v2.2.0 / v2.3.0). Bullet order still implies priority, and the README stays accurate if release sequencing shifts.
  Co-authored-by: Claude Opus 4.7 (1M context) noreply@anthropic.com