GOBIGnINTERRUPT

v1.1.4 (2026-04-30)

Full Changelog Previous Releases

• v1.1.4 - Evidence engine gate + diagnostic logging for non-addon peer
  matching
  Two complaints from latest in-game session:
  1. Engine-OFF dungeon log was full of "evidence: aura 'X' on partyN
  -> no DB match" lines for auras unrelated to tracked CDs (boss
  mechanics, talents, rotational procs).
  2. Known CDs that should match through Evidence's name-lookup path
  (Dancing Rune Weapon on a Blood DK, Bestial Wrath on a BM Hunter)
  are NOT matching - they get logged as "no DB match" too.
  Changes:
  • Bar.M.IsEngineEnabled() exposed. Evidence and future modules can ask
    the authoritative gate (set by SetEnabled via App.UpdateContext)
    whether the engine is currently on.
  • Evidence's UNIT_AURA handler and the 0.75s polling loop both bail
    early when the engine is off. Cuts log volume to ~zero out of M+
    and saves the per-aura table lookups.
  • Evidence's name-lookup branch now distinguishes three failure modes
    in the debug log:
    "evidence-by-name 'X' on partyN -> 49028" (success)
    "matched 49028 but GetCooldown=nil (disabled in Spell DB?)"
    "not in AuraMap (or name was secret-tagged and SafeString2 rejected)"
    Previously all three collapsed to "no DB match", hiding which one
    was actually firing. Re-running with this should tell us whether
    Dancing Rune Weapon / Bestial Wrath are missing from AuraMap, are
    having their names tagged in 12.0.5 (a regression from prior
    behavior where only hostile-aura names carried the secret marker),
    or are being silently disabled by the user's Spell DB.
    Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com