Ka0s Loot History

A passive loot-tracking addon for World of Warcraft: Midnight. Ka0s Loot History keeps a permanent, account-wide record of every item you loot (above a quality threshold you choose), works out where each drop came from, and gives you a standalone window to browse the full history and an Insights view to analyze it — so you always know what you picked up, when, and from what.

Every item you receive is captured passively from the loot stream and attributed to a source — a mob kill, a container, mail, a trade, the auction house, a quest, a vendor, a deconstruct action, or a Mythic+ chest — with a confidence marker for anything that had to be inferred. History is stored in the account-wide saved variables, so it's shared across every character and survives reloads and relogs.

Roll and Craft are part of the source model (and the forward-compatible export contract) but have no live capture path yet, so they aren't offered as recording toggles.

Screenshots

The History browser

Insights

Settings panel

Usage

Install the addon with the Addon Manager of your choice (or drop the folder into Interface/AddOns) and log in — recording starts immediately, with no setup required. All libraries are bundled in libs/, so there are no separate dependencies. Open the History window with the minimap button (left-click) or a slash command; inside it, click a column header to sort, use the filter bar to narrow results, pick a Group by to collapse rows, and switch to the Insights tab for analytics.

Slash commands

/lh is the short form; /loothistory is a long-form alias that accepts the same subcommands.

Settings panel

Settings live at Escape → Options → AddOns → Ka0s Loot History (or /lh config). Everything is account-wide, and every control mirrors to the slash CLI (/lh get / /lh set). Two groups:

Master Controls

• Enable collection — master toggle for recording. When off, no loot is captured; existing history is untouched and the window still works. Persists in saved variables.
• Hide minimap button — show or hide the LibDBIcon minimap button. Left-click opens the window, right-click opens settings.
• Window scale — scale the standalone browser window from 0.6× to 1.6×. Window position and size persist across sessions independently of this setting.

Data Collection

• Minimum quality — only record items at or above this quality (Poor → Legendary; default Common). Applies at capture time — it never hides records already stored.
• Keep history for — retention window. Records older than the chosen age are pruned once per session; choose Always to keep everything forever (default 30 days). Retention is shared account-wide.
• Record data from — per-source recording toggles. Unchecking a source stops recording it. Only sources with a live capture path appear here — Roll and Craft are enum'd for the export contract but not yet stamped, so they're hidden.

How attribution works

Every record is built by a short pipeline:

1. Detect self-loot — CHAT_MSG_LOOT is the authoritative signal that you personally received an item. The collector self-filters to the player and applies the minimum-quality gate, so other players' loot and sub-threshold junk are ignored.
2. Resolve the source — peripheral game events stamp a short-lived loot context just before the loot line fires: the creature you looted, the container you opened, the mail / trade / vendor / auction-house interaction, the quest turn-in, or the Mythic+ keystone chest. The collector consumes whatever context is live at the moment of loot.
3. Fall back gracefully — if no context is live, the drop is tagged Other with Inferred confidence rather than dropped. Everything attributed from a live signal is recorded as Certain.
4. Store one dense row — the item link plus denormalized fields (id, name, quality, item level, bound, sell price, type), the resolved source, the zone, the character, and a timestamp go into the account-wide history, ready to filter, group, sort, and analyze.

The loot context is single-slot and short-lived by design — it deliberately survives multiple loot lines from one loot window, so a full container of drops all attribute to the same source.

FAQ

Troubleshooting

Issues and feature requests

All bugs, feature requests, and outstanding work are tracked at https://github.com/tusharsaxena/loothistory/issues. Please file new reports there rather than as comments — the issue tracker is the single source of truth for the project's backlog.

Testing

Unlike most addons, Ka0s Loot History ships a headless unit-test harness that targets WoW's Lua 5.1 runtime. From the repo root:

• Unit tests: lua tests/run.lua — loads all source via tests/loader.lua against the WoW-API mocks in tests/wow_mock.lua.
• Lint: luacheck . — must report 0 errors before every commit (config in .luacheckrc).
• Syntax-check one file: luac -p path/to/file.lua.

Run these before tagging a release or after refreshing libs / bumping ## Interface:.

Version History