Every one of the 34 rows a play session reported was read back out of a
capture, and not one was ours: 16 are BetterCharacterPanel anchoring to
Blizzard_InspectUI frames that LoadOnDemand has not built yet, 7 are .toc
and <Script file> lines naming files their own package does not ship, 10
are TitanPanel/InfoBar/Outfitter integrations in addons whose optional
dependencies this player does not have, and 4 are CVars 1.12 never had,
which `cvars`'s own test says to leave unregistered.
The reference shows the player none of that. A missing parent, a missing
relativeTo and an unknown inherits are severity-2 lines in FrameXML.log,
and SetCVar on an unregistered name raises into the pcall every addon
that writes one already wraps it in. Our window was a deliberate superset,
which is right for a compatibility report and wrong for a line reading
"34 problems": a TitanPanel plugin with no TitanPanel is not a fault here.
So `error` (code raised) and `load` (an addon is not running) stay
problems and stay listed, and `warn` -- a call accepted that did not do
what it said -- becomes a note, counted beside them and listed behind a
new Show notes checkbox. Nothing is dropped; the log still carries every
one and the window is one click from all of them.
Also closes a hunt: the 283 `SetOwner: unknown anchor 'BOTTOMRIGHT'`
warnings that three static sweeps of every installed addon could not
place are the realm's own FrameXML, Shop_ProcessEntries forcing items
into the cache through a hidden scan tooltip.
The seven load failures and the two layout defects from the same session
are fixed in the player's own addon copies, mirrored to Addon_Ports; both
are written up in docs/ADDON_COMPAT.md.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SgstFWtn1RxEJ5kVrpgYwn
gromandClaude Opus 5
50a229c202