Skip to content

RaidKit

Raid Ledger changelog

Paste a Warcraft Logs report and see who was flasked, fed, enchanted, gemmed and resist-capped, per player, per pull.

  1. Raid Ledger2026-09-22
    • Meta gems are checked for activation, not just presence. A TBC meta does nothing until the rest of the gear meets its color requirement and the game never says so, so the Enchants & gems table has a Meta column — active, INACTIVE, empty, ? or — — with the requirement and the gear's actual color counts in the tooltip. An inactive meta counts as missing gear, so it reaches the Status column, the night grid and the player's history. Requirements come from Wowhead's own tooltip text for all eighteen TBC metas, in both of its forms ("at least 2 Red Gems" and "more Red gems than Blue gems"); an orange gem counts as a red and a yellow, purple as red and blue, green as yellow and blue. A gem the offline data cannot color leaves the verdict at ? rather than accusing anyone.
    • Docs: a /docs section with a guide per tool and six for Raid Ledger — how to read every table and flag, the fight and link syntax, private reports, the shadow-resistance arithmetic, and what an unknown item means. Every audit header links to its section.
    • Live logs: a report whose last fight is within a day is re-fetched at most once every five minutes however many people are watching, and the report page and night grid show a Live pill, poll for the next pull for two hours after the last one, and refresh themselves when it lands.
  2. Raid Ledgervguilds2026-09-13
    • Buffs at the pull: a fourth audit with one column per raid buff family (Fortitude, Spirit, Intellect, Mark of the Wild, Shadow Protection, the six blessings, Shout, Blood Pact), a Missing count and Flags such as 'no Kings', 'no Might', 'Salvation on a tank' and low ranks. A buff is expected only when at least half the raid visibly carries it, because Warcraft Logs cannot see a buff cast before logging began.
    • Guilds: create yours with realm, region and faction; roles read Guild Master, Officer and Raider; Discord-pasteable join links with a role, an expiry and an optional use cap; email invites for the individual case.
    • Per-guild roster: talent ranks (a Mage's Magic Absorption) and manual SR bonuses live on /guilds/<slug>/roster and on the Talent cell of any SR audit; an audit reads the guild named on the report, or your own; one click adds a report's missing players to the roster; raiders unseen for sixty days are marked stale.
    • Automatic posts: turn it on beside the webhook and every new log's summary lands in the channel the morning after the raid — nobody pastes a link.
    • Player history: every name in a table links to that character's page — the latest audited pull of each public report, an enchants trend, consumables night by night, and the things that keep coming back (the same missing slot on three or more reports).
    • Gear sanity under the enchants table: PvP pieces named, empty slots, armor lighter than the class wears, and an item level far under the raid's — warnings, never a Status.
    • Hit & expertise: every dps against the boss caps — 9% melee and ranged, 16% spell, 26 expertise — from the ratings in the log plus the talent hit that spec usually carries, named so you can disagree; the Flags say how many rating points short.
    • Sign in with Warcraft Logs alone: no email or password needed to open your private reports; add an address later from Settings if you want notifications.
    • The night: /ledger/<code>/night is every player by every boss pull with one dot per audit — gear, buffs, shadow resistance on Mother Shahraz — a consumables dot for the whole night and a Red count per player; pulls not yet cached load one at a time while you watch.
    • Summary: /ledger/<code>/summary shows the last kill as three or four tiles — enchanted & gemmed, buffed at the pull, flasked & fed, shadow resistance on Mother Shahraz — with the names that did not make it, and the link unfurls into a card with the same numbers.
    • Post to Discord: an Officer saves the raid channel's webhook on the guild page, and every audit page gets a button that posts the same text Copy for Discord produces. A flag on every audit row files 'this looks wrong' with the row as shown.
    • Attendance: who was in the raid for which pulls, from the report header alone — boss pulls, kills, first and last pull, joined late / left early / sat out, and a bench-swaps table per pull.
    • Your guild's latest logs: with a guild set up here (realm and region), /ledger lists its newest Warcraft Logs reports with an 'audited' mark and a link straight to the night — no hunting for the URL in Discord.
    • Compare with last week: /ledger/<code>/compare lines this report up against the previous one from the same guild — or any report you paste — and says per player what was fixed, what is new and what is still there.
    • Pre-pots: the consumables audit now knows when each potion was used, so a Pre-pots column counts the boss pulls that opened with one and the Flags say which pulls did not.
    • Consumables: the wrong flask for the job is flagged — Mighty Restoration on a Rogue, Healing Power on a Warrior, Fortification on a Mage — judged as tank, healer, caster or physical from the spec, and only when the spec is known. Hybrids get the benefit of the doubt.
    • Account export is raidkit-export-*.json with your Warcraft Logs link (never its tokens), guilds, opened reports and the character facts you set; the only Guild Master of a guild cannot delete their account until someone else leads it.
  3. Raid Ledger2026-09-13
    • Character memory: the site now remembers each character's race and professions by name and realm, learned from every report (racial casts, Blizzard, class rules, profession-only gear and casts, ring enchants) and reused on the next one.
    • Click-to-set: signed in, a pencil on any uncertain Race or Engineer cell lets a raid leader set the race or the two professions; a manual entry wins over every automatic source from then on.
    • Professions rule things out: two known professions without Engineering means "not an Engineer"; without Enchanting, ring enchants are no longer expected of that player.
    • Races from Blizzard's character profile API where the log cannot name them, cached per character. On a typical Anniversary raid this resolves most of the remaining unknowns; the audit says which source each race came from.
    • A privacy page (/privacy) describing what the site stores, including the Blizzard character data.
  4. Raid Ledger2026-09-12
    • Races are now read from the log where possible: a racial ability cast anywhere in the report names the race, and the Warcraft Logs character API supplies each player's faction so Alliance shamans, Horde paladins and druids resolve by class. Unknown races stay unknown rather than guessed.
    • Engineer detection: Engineering-only gear worn at the pull and Engineer-only casts (sappers, bombs, rocket boots) anywhere in the report. Shown on the Enchants & gems and Consumables audits with the evidence.
    • Shadow Guard (+10 shadow resistance, head or legs) now counts toward gear SR.
    • Audit tables: flags, missing and warnings sit under each player's row and wrap to the screen; the player column stays pinned while the numbers scroll.
    • Pick any pull from the fight list or the Pull dropdown on an audit.
    • Recent reports are now per account: the list on /ledger and the homepage shows only the reports you opened, with a Forget button, and nothing is listed while signed out. The site-wide list is gone.
    • Product pages for every RaidKit tool at /tools, with a merged changelog.
    • Private reports open through the viewer's own Warcraft Logs connection: public and unlisted reports still use the site client, a not-found is retried with your token, and cached private data is served only after Warcraft Logs confirms your access on that request.
    • Report header now records visibility and owner; private reports are read through the viewer's own Warcraft Logs connection.
    • User tokens refresh through the refresh-token grant near expiry; a refused refresh asks you to reconnect.
    • Error notices show the next step beside the message: Sign in, Connect Warcraft Logs or Reconnect Warcraft Logs.
  5. Raid Ledger2026-09-11
    • Connect Warcraft Logs: an OAuth provider for warcraftlogs.com, Continue with Warcraft Logs on the sign-in page (for accounts that already connected it), and Settings > Connections with Connect, Reconnect and Disconnect.
    • Only Warcraft Logs tokens are stored (with your username there); disconnecting deletes them and is refused if it would remove the only way into the account.
    • RaidKit branding: site name, header wordmark and a homepage that leads straight into Raid Ledger with a plain form that works before JavaScript loads.
    • Report cache and the first pages: three database models cache the report header, per-fight snapshot and whole-report consumables lines; reports that ended in the last day are re-checked so a log loaded mid-raid does not stay frozen.
    • /ledger takes a report URL, /ledger/<code> lists boss fights, and /ledger/<code>/sr, /gear and /consumables run the engine on the server and hand a finished table to a sortable client table.
    • Race and talent settings come from the seed files until guild settings exist.
    • Warcraft Logs client in TypeScript, verified live: report header with trash flagged and ability names, fight snapshot from the Summary table and CombatantInfo events, and whole-report consumables lines with the boss-snapshot and trash-carry-forward rule.
    • One token source serves both the site's own client and a signed-in user's token; the live smoke test reproduces the Python numbers.
    • Engine ported from the wow-audit Python tool to TypeScript with parity tests: the Anniversary rules module, offline item, enchant and gem data (wowsims dump plus Anniversary extras), roster normalization and the three audits as pure modules.
    • Fixtures are the Python tool's own; the parity tests hold both implementations to the same numbers (174 gear SR and 244 buffed for one character's in-game sheet).