GOBIGnINTERRUPT

v1.1.5 (2026-04-30)

Full Changelog Previous Releases

• v1.1.5 - multi-row overlay + diagnostic split
  In-game testing on a Brewmaster Monk showed two leftover issues from the
  v1.1.4 round:
  • Overlay row hard-capped at 6 icons. Brewmaster has 9 non-interrupt
    CDs (Celestial Brew, Fortifying Brew, Dampen Harm, Niuzao, Detox,
    Touch of Death, Ring of Peace, Leg Sweep, Paralysis) — three never
    found a slot ("OnCDStart no free icon (max=6) unit=player" repeated
    in the log). Same problem for Druid, Paladin, anyone with a long
    class CD list. Bumping the constant alone would have widened the
    bar awkwardly; a wrapped grid is the right shape.
  • The "not in AuraMap (or name was secret-tagged and SafeString2
    rejected)" diagnostic conflated two distinct failure modes. We
    needed to know which one we're hitting to decide whether to chase
    a tagged-string regression or a missing data entry.
    Changes:
  • UnitOverlay.lua now supports configurable rows. New saved-var
    db.unitOverlay.rows (default 1, range 1..3 in the UI). Container
    size, icon placement (relayout), and test-mode visuals all
    generalized to (col, row) grid coordinates with col = (i-1)%perRow,
    row = floor((i-1)/perRow). MAX_ICONS becomes a function of
    perRow * rows; the old 6-slot ceiling becomes 12 at rows=2 / 18 at
    rows=3.
  • Anchor side -> grid corner mapping clarified: BOTTOM/RIGHT/TOP
    start near the host edge (TOPLEFT or BOTTOMLEFT) and grow outward;
    LEFT mirrors with TOPRIGHT.
  • Options panel adds an "Overlay rows" slider (1..3) under the
    existing iconSize / iconGap sliders. Default fix in mkOffsetSlider's
    per-key default table to seed rows=1 on first show.
  • Evidence.lua splits the conflated log line into three explicit
    outcomes by calling Taint.SafeString2 BEFORE LookupByName instead
    of relying on the lookup's internal reject:
    "name is secret-tagged (SafeString2 rejected; lookup not attempted)"
    "matched X but GetCooldown=nil (disabled in Spell DB?)"
    "not in AuraMap"
    Plus the existing success line. Now /gbi log tells us unambiguously
    whether non-addon-peer name detection is failing on the SafeString2
    gate (12.0.5 friendly-aura-name regression) or on the data
    registration.
    Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com