Loothing

A second independent review with fresh eyes on top of 2.0.27 turned up three more distinct bugs — one that invalidates the entire schema-migration system, one that keeps pushing "TRADEABLE" comm noise despite 2.0.27's gate, and one that explains why Spark of Radiance kept showing up in the Loot Picker. All three shipped here.

Fixed

• Profile schema migrations have never actually run on any user's SavedVariables — fixed now. The migration runner was reading sv.profiles but Loolib's SavedVariables stores data at sv.data.profiles and doesn't proxy the bare field through the accessor. Every migrateV2 / V3 / V4 / V5 was a silent no-op. Compounding this: Loolib attaches a __index metatable to every profile that falls through to the defaults, so reading profile.schemaVersion on a profile that has never stored one returns the current default (5) via the fallback — making the migration code think "already up to date." The runner now walks sv.data.profiles and uses rawget(profile, "schemaVersion") to see what's actually persisted. On next login you'll see the full V2→V5 migration chain run for the first time, which among other things finally clears the stale settings.sessionTriggerAction="auto" / settings.sessionTriggerMode="afterRolls" entries from your DB that have been sitting alongside your real session.triggerAction="prompt" for several versions.
• Spark of Radiance (and other BoP crafting reagents) no longer leak into the Loot Picker. ENCOUNTER_LOOT_RECEIVED fires for every item distributed from a boss kill, including bound-on-pickup crafting reagents that can't be traded to anyone and have no business in a loot-council session. The inactive-session buffer path was accepting them because quality filtering is (correctly) disabled in prompt mode — the check "is this actually distributable loot?" was missing. Items that are bind-on-pickup AND in the consumable / trade-goods / miscellaneous / profession item classes are now skipped at the buffer gate. Raid gear (weapon / armor classes) passes through unchanged.
• TRADEABLE / NON_TRADABLE comm broadcasts now suppressed at the source in auto-roll raids. 2.0.27 gated the bag-scan TRADABLE path, but the same comm was still flowing through TradeQueue:UpdateAndSendRecentTradableItem — called every time the ML adds an item to an active session, and every time a non-ML raider receives a personal-loot item. In auto-roll mode (ML auto-NEEDs, non-ML auto-PASS) these broadcasts carry no signal: the ML is already aware of their own items, and non-ML raiders don't win anything to announce. The TradeQueue now reads the MLDB directly and skips both broadcasts when it detects auto-roll mode. Conservative fallback: if MLDB hasn't arrived or the raid is in passive group-loot mode, broadcasts continue as before so nothing is lost during ML handoffs.