Dibs — Master Loot for Classic Era Raids

Dibs is a master-loot tool for Classic Era raids. Everyone calls dibs on the gear they want before the raid, so when an item drops the masterlooter instantly sees who's competing — for fast, fair, drama-free distribution. Because dibs are shared with the group, it works whether you're in an organized guild run or a freshly-formed pug.

In development. This page describes the design; features ship over time.

Call your dibs before the raid

• Every raider builds a wishlist of the gear they want, organized by the dungeon or raid it drops in — so nobody forgets the item they were farming or where it drops.
• Wishlists sync to the group, turning a private note into the shared answer to "when this drops, who actually wants it?"
• Walk into an instance and your list auto-filters to it. Holds non-gear items too (recipes, mats, mounts).
• Win an item and it gets crossed off (strikethrough), not deleted — so you can see your progress, and future drops say "You already won this."

A masterlooter interface that does the work

• See each dropped item and who is competing for it; click Roll to prompt the group (or just the competitors).
• Hover a drop and Dibs tells you which classes it is best-in-slot for — in the raid you are actually in. You can see your own BiS in the planner; this is the other nine classes, so caster gear on a warrior masterlooter is no longer a shrug. Class-coloured, and it says Priest (Shadow) when only one spec wants it and just Warrior when the whole class does.
• Auto-distribute to the winner — as soon as everyone has answered, or when the countdown expires — with automatic tie-breaker rolls.
• You decide what happens to greys, whites and mats (absorbs BijouRR). One officer setting, pushed to the raid: Leave alone, Roll for them so a stack of Mageweave gets a row on the loot table like any boss drop, or Hand out at random. A protected-items list is the exception to all three, so a valuable BOP mat is never scattered — it gets a row and you decide where it goes.
• Distribute Later (Gargul-style): auto-loot, whisper the winner to trade, and a buff-bar timer for the 2-hour trade window that fades green → yellow → red.

The whole boss in one window

Loot the boss and the corpse’s entire drop goes up as one list — on everybody’s screen, on its own, with no one having to press anything to send it. Everyone picks Main / Off-spec / Pass on every item at the same time and privately, under a clock you control — so nobody gains an advantage by clicking last, and nobody sits watching a countdown for an item they already answered.

• Pause the clock for a pull, add time, or close selection early. A raid pulls mid-list and nobody loses their window.
• A roster column shows how many picks are in, and who has and has not finished — so you chase the two stragglers instead of waiting the clock out on their behalf.
• The roll countdown is a thin bar under the item being rolled, draining to empty, so it is obvious which row the clock belongs to.
• An Unstick button, because WoW silently drops addon messages when the air is busy and a stuck answer used to mean a /reload. Anyone can press it, it re-sends only what was genuinely stuck, and it is safe to press when nothing is wrong.
• Then you call each item in turn. Everyone who picked it rolls for real — your own /roll scrolls past in chat exactly as it always has — and you announce the winner and hand it over. Nothing advances on its own: the pause between items is where a dispute gets settled.
• Soft reserves show on the row, with the buttons gated to the people who reserved it. No second tab to check.
• Hovering a row says who the item is best-in-slot for, so a raider deciding whether to spend a pick on it can see whether they are the obvious candidate or the fifth in line.
• Misclicks narrow in stages: change freely before the clock stops, Unlock one player on one item after it, and Void an entry after that item has rolled — a void is always announced to the raid, because chat is the record.
• If somebody picked an item and then disconnected, the window says so rather than quietly resolving it short.

Know who wants the drop before you roll

• The roll window looks like the Need/Greed prompt you already know — with the item's competitors shown, so you're never guessing whether a drop is relevant.
• Optional Mainspec/Offspec wording and attendance counts (how many times someone lost their wishlisted item).
• The roll ends when everyone has answered, not when the timer runs out — the way Need/Greed does it. No more standing around watching a countdown after the whole group has already clicked. It never ends early while someone might still be choosing, so if a raider isn't running Dibs the timer stays as the backstop.
• Hover for the tooltip, Shift-click to link, Alt-click to compare against what you're wearing — and drag the window wherever you want it.

Soft-reserve a raid — no website needed

• An officer builds the raid's reservable list in-game: it auto-builds from the item database (every drop, in boss order), so there's no 74-row spreadsheet to fill out.
• Restrictions suggest themselves. Every item is scored for each class and spec, and Dibs pre-restricts it to who actually wants it — a 2H sword to melee, a defense cloak to tanks, a caster staff to casters and healers — so the officer only tweaks the exceptions. Recipes restrict to the profession that learns them. Or flag an item Loot Council or Guild Bank (goes to the bank, not reservable).
• Members click an item they're eligible for to reserve it, and see who else reserved what — class-coloured, with an EP-change column vs their own gear and a green ✓ when a restricted drop is for them.
• Keep using softres.it if you want. Paste an existing softres.it “Gargul” export straight in, or export one back out — and save, restore, and share the whole setup as a string so a hand-tuned config is never lost.
• Lock it for raid time. An officer can freeze all reserves during the raid and unlock afterward — and it holds across a relog, because the setup syncs to every client with leadership as the authority.

Run DKP or GDKP — without a spreadsheet or a website

• Three independent choices, not a list of named systems. How points are earned (flat per boss, a pot split across the raid, a completion bonus, per-30-minutes, an on-time bonus, an absence penalty), what an item costs (live auction, a fixed price, or nothing at all), and where spent points go (destroyed, or split back to everyone who was there). Configure the system your guild already runs instead of picking the nearest preset. GDKP is just gold + split-back — not a separate mode to learn.
• Your raids don't have to agree. Molten Core can run soft reserve while Blackwing Lair runs DKP — on the same night, with different people in each. Set each raid from one dropdown; anything left on Default follows your guild-wide setting. Dibs then only shows the tabs for the systems you actually use.
• Auctions with free-text bidding. Type any number — no +10 / +100 buttons, which are noise on a 2000-point item and overshoot a 50-point one. Every bid pushes the clock back, so there's no last-second sniping, and the countdown re-announces when it moves.
• The maths is exact, always. Splitting 1000 among 30 raiders is 33.333…, which no amount of decimal places fixes — so Dibs gives 20 people 33 and 10 people 34. Exactly 1000, every time. Your balance is a whole number, and it's the number that gets used.
• Nothing is ever quietly edited. Every change is its own line: a correction is a new entry, not a rewrite. When a raider asks why they have the points they have, the DKP tab shows them every entry that produced it — how much, what for, and who recorded it.
• Everyone agrees on the numbers. During a raid only the master looter records anything, and it syncs out from there — so the points you see are the points deciding the loot.
• Officers can award and adjust by hand. A character, an amount (plus or minus) and a note. It is recorded the same way as everything else — its own ledger line with your name on it — so a hand-made correction is as auditable as an automatic award, and the raider can see exactly what you did and why.
• People who leave keep their points. Someone who gquits drops out of the standings, but nothing is deleted — come back and you come back to exactly what you had. Tick Show ex-members to settle up with someone who's gone. Pugs are tracked separately and never swept up in it.
• Officer-triggered decay (rounded down, so a 20% decay never takes 21%) and alts folded under your declared main, so it doesn't matter which character you raid on.

Plan your gear like SixtyUpgrades — in-game

• Open the planner and click a gear slot to see every item that fits it, ranked by EP for your class and spec (community-standard HawsJon weights, or your own custom weights) — filtered to what your character can actually use (armor, weapon, class and faction restrictions all respected), with the best item from each raid flagged BiS.
• Left-click to try an item on. The centre panel updates live with your build's total EP, item level, top stats, and active set bonuses as you swap pieces in and out.
• Enchant your pieces too. Pick an enchant per slot and its stats fold into your totals — and your currently-worn enchants are read straight off your gear, so the numbers match your character sheet.
• Save loadouts as templates (Prebis, AQ40, Naxx…) and switch between them — then add anything you want to your dibs with one click.
• Find the item you're after fast. Filter to upgrades only or one raid/dungeon/zone (grouped into tidy submenus), sort the list by any stat instead of EP, search any field (name, source), or hide two-handers. Hover any item for its full tooltip plus an EP breakdown showing exactly why it scores what it does.
• Compare side by side, and equip the right ammo. Alt-click any item — a list row or a paperdoll slot — to compare it directly with what you're wearing. And hunters can't pick the wrong ammo: the Ammo slot only offers what your ranged weapon fires (arrows for bows/crossbows, bullets for guns).
• Tune the weights to your build. Edit the EP stat weights in the Weights tab and save named templates — the whole planner re-scores to the one you pick, and switching to a spec template (say Beast Mastery) scores you as that spec. Defaults stay untouched.
• See what's driving your EP. A Breakdown sub-tab lays out an EP datasheet — the EP each stat contributes, and the EP each piece (with its enchant) contributes by slot — so nothing about your score is a mystery.
• Plan buffed, not naked. A Buffs tab toggles the buffs and consumables you'll raid with — the full flask / elixir / potion / food spread and every raid / world / totem buff, straight from the item database (all six Sayge's Dark Fortunes, the Dire Maul tributes, all the totems…), each showing the EP it adds and folding into your Total EP. Consumables are grouped by which ones share a slot and are single-select per slot (one agility elixir, one flask, one food…), so you see at a glance what coexists. Hover any one for its real in-game tooltip plus a Dibs EP breakdown.
• Play with your talents too. A Talents sub-tab seeds from your actual current build and lets you spend and remove points across the three trees — tier gates and prerequisites enforced, just like the in-game trees — and the build you land on drives the spec the planner scores you as. Respec and it re-seeds itself.

Browse every drop — loot tables in-game

• A Loots tab browses the whole item database like AtlasLoot — pick a source (raids & dungeons, PvP, reputations, world bosses — whatever the data ships) and a subcategory to see its loot, grouped by boss or tier.
• Every row shows your EP for the item — something AtlasLoot can't — alongside its type (Sword / Staff / Plate / Ring…), slot, and item level, all sortable.
• Narrow it fast. Filter by faction (Alliance / Horde / both), by type, or to “My class” — only what your character can actually equip — and search any field. One click adds anything to your wishlist.

Works for pugs

Dibs is built for pugs, not just guild runs — and nobody in a mixed raid is left out:

• Pug raiders who have the addon (from any guild, or none) get the full experience: the raid leader or master looter — not a guild rank — sets up the soft reserves, locks them, and starts rolls, and every Dibs user in the raid receives the setup and a popped roll window. Reserves and Main/Alt declarations sync straight to the group. No guild, no website, no spreadsheet.
• Raiders with no addon at all still take part: the master looter announces each roll in chat, they /roll as normal, and Dibs tallies those rolls right alongside the addon users' — MS>OS, ties and soft reserves all still apply — and whispers the winner. A raid that's half-on-Dibs, half-not, across several guilds, runs as a single loot flow.
• Raiders from a different realm land on the right character. A /roll in chat gives you a bare name with no realm on it, and on a connected-realm cluster that is not enough to tell two characters apart — so a raider from another home realm could be mistaken for somebody else, or matched to nobody at all. Dibs now builds a table of everyone in the raid as they join and keeps it for the whole night, learning each character's real realm from the group itself, the guild roster, or the identifier that arrives free on any chat message. Because it accumulates, a roll that arrives after somebody has dropped group still counts for them. It is kept per raid, so a guild running two at once never has one answering for the other — and it never sends a /who.

Only the parts you actually use

A fresh install of Dibs is a planner. You get Planner and Loots and nothing else — no soft reserve, no DKP, no roll handling, and the game’s own Need/Greed is left completely alone.

• Every loot feature is opt-in. Tick Use Soft Reserve, Use DKP or Let Dibs handle loot and that feature’s tab appears; untick it and the tab goes away. The tabs change the moment you tick the box.
• Let Dibs handle loot is the master switch over all of it. With it off you have a wishlist, a planner and a loot browser, and Dibs touches nothing about how your group hands out loot.
• Switching something off never throws away how you had it set up. Tick it again and your reserves, restrictions, DKP config and history are all where you left them.
• Per raid, not just per guild. Molten Core can run soft reserve while Blackwing Lair runs DKP, and a raid you have set up by name keeps its tab even when that system isn’t your guild default — because that raid really does run it.

Requirements

• World of Warcraft Classic Era and Burning Crusade Classic (2.5.x) — both supported. TBC support landed in v0.2.0: EP scoring, best-in-slot, drop sources, the nine Outland raids, talents and buffs all work on a TBC client, the same as Classic Era. (Verified on a live TBC client; the one known gap is TBC ammo scoring.)
• Dependencies install automatically on CurseForge (Ace3, LibItemDB, ProfessionDB, DeltaSync, AceCommQueue, VersionCheck, GuildRoster, LibLocaleOverride, LibAceGUIWidgets); manual installers must add them too.
• Optional: ClassicCalendar — enables tagging your dibs to scheduled raid events.
• Optional: TOGBankClassic — puts a [Bank] button on gear rows for items your guild bankers are holding, so you can ask for an upgrade without leaving the window.

Recent Updates

v0.4.5 — Advantage counts for everyone, Dibs learns your raid, and the standings say more

• Fixed: an Advantage player’s second roll was thrown away if they raided from another realm. Reported live with the chat log — “you can see one player who had Advantage rolled twice, their second roll was 98 but the item was awarded to the 65 roll.” Dibs was asking two different questions about who that player is, and only one of them had the right answer. When it flags somebody for Advantage it identifies them from the raid, which knows each character’s real realm — so the flag was stored under their true name, exactly as the announce printed it. But a /roll scrolling past in chat arrives with no realm attached, and Dibs asked the guild roster to fill one in. That never looked anybody up: it simply stapled on the masterlooter’s own realm. For anyone raiding from a different realm the two names then disagreed, the flag was not found, and the second roll was rejected as a duplicate — so the lower die stood and a smaller roll beat it. It only ever hit raiders from another realm, which is why it looked random: on the masterlooter’s own realm both routes produce the same name and Advantage worked perfectly. This is the worst shape a loot bug has — the advantage was announced to the whole raid, the player took both rolls in public, and the higher one was discarded in silence with nothing erroring. There is now only one question: a roll is matched against the raid roster, the same list the flags were keyed from, so the two cannot disagree about who somebody is. Guild membership never enters into it, and a pug resolves exactly as a guildmate does. And a refused roll now says so — Dibs always had a line naming the reason, switched off unless you were running a debug command, so the one fact that would have settled this in seconds had never once been printed. It is on by default now for the two refusals that change who can win, in the masterlooter’s own chat and not the raid’s.
• Added: Dibs now remembers who is in your raid, and which realm they are really on. A /roll line gives you a bare name with no realm on it, and on a connected-realm cluster that is not enough to tell two characters apart. Every version until now filled the gap by guessing — right for people on your own realm, wrong for everybody else. That is the Advantage bug above, and it was never going to be the last one: the same guess sits under the loot log, soft reserves and attendance. Dibs now builds a table of everyone in the raid as they join and keeps it for the whole night, so a roll that arrives after somebody has dropped still lands on the right character. It is per raid, because a guild can run two at once and they must not answer for each other. Three sources, none of which invents anything: the group itself (which knows each character’s real realm, and covers a pug exactly as well as a guildmate), the guild roster for a guildmate who has already left, and a player’s GUID, which arrives free on any chat message they send. It sends no /who queries — once those three are in play there is nobody left for a query to find.
• Fixed: a pug’s roll could be credited to the wrong character. If somebody in your raid was not in your guild and left the group before their roll was counted, Dibs asked the guild roster who they were. The guild roster has never heard of them — but it answers anyway, stamping your realm onto their name. Dibs now only takes the guild roster’s answer for somebody it actually has on file. A pug still in your raid was never affected.
• Fixed: a re-roll under a second spelling of your name could take an item off somebody. When Dibs checked whether you had already used your roll it compared names exactly, while every check around it compared them realm-tolerantly. If one raider’s two rolls arrived under two spellings the second looked like a different person, so “your first roll is binding” quietly stopped applying — both rolls competed, and the higher one could take the item off somebody who rolled once. A pass could be followed by a roll the same way.
• Fixed: the loot table could take itself away from the masterlooter, again. The previous release stopped this when the game could not say who holds master loot. That check had two halves and only one was covered: the same collapse survived on the question “and am I that person?”. If your client momentarily could not work out its own name — the churn around a reload, somebody zoning, a member joining — the answer came back no, which reads as “somebody else is the masterlooter”, and the action bars, roster and title vanished mid-boss with the table still live. That question now has a third answer: yes, no, or I cannot tell. Only yes and no move the table between players.
• Fixed: the roll window no longer pops up with nothing in it. Reported with a screenshot on Augment Blizzard’s frame — “dibs roll window still appears just without the buttons.” In Augment mode Dibs deliberately draws no roll buttons, because Blizzard’s own window does the rolling; the Dibs companion beside it exists to tell you one of three things — that you called dibs, who else did, or that it is an upgrade. On a stack of cloth it knows none of those, so it drew an item name and a timer that Blizzard’s frame was already showing a few pixels away, and a window with no controls reads as a window whose controls have broken. It now stays shut unless it has something to say, which on trade goods and greys is most of the time. Replace mode is untouched — there the window carries the buttons, so it always has a job.
• Added: two new standings columns, WL lost and SR lost. Requested — “we SHOULD have a column for lost rolls on wishlisted items” and the same for soft-reserved ones. Plain Lost on its own is a weak argument: a raider with forty lost rolls may simply have rolled on everything, while a raider with twelve losses on items they had actually wishlisted has a case. Both sit immediately right of Lost and each is a subset of it. They overlap on purpose — reserving something you want is the whole point — so a loss on an item that is both is counted by both columns, and adding them together over-counts. They only count from this version onwards, and the header tooltips say so: whether a loss was wishlisted or reserved is a fact about that moment, and nothing already in the history can be worked out after the fact. Lost keeps its full history.
• Changed: the ? column is gone, and the standings show how many raids you actually attended. Requested — “this ? column is useless information”. It was the bucket for a night whose raid Dibs could not identify, and as a column it could not be read: it has no name, so there is no way to tell which nights are in it. In its place, an Attended column, sitting immediately left of the percentage it produces — that number had been carried on every row and displayed nowhere, so an officer got 60% with no way to see whether it was 3 of 5 or 12 of 20, and those are not the same raider. The unidentified nights are not deleted and still count as attendance, because they were really raided; the visible consequence, which the tooltip states rather than leaving you to discover, is that Attended can be higher than the per-raid columns added together.
• Fixed: a raid you had not run yet could not be configured, and a per-raid loot system was not being applied. Reported — “the loot system per raid is missing RFC, ony, aq20 and aq40”. Every source behind that list was a record of something already done, so a raid could not be set up until after you had run it — backwards for a screen whose whole job is deciding how a raid will run. It now starts from the raids your client actually ships, so Onyxia, both Ahn’Qiraj raids and Ragefire Chasm are there the first time you open it. Separately, a per-raid loot system was doing nothing at all: the settings screen saved under a raid’s internal key while the lookup made from inside the instance used its display name, so setting Molten Core to DKP, walking into Molten Core and getting the guild-wide default was the actual behaviour — with the setting still showing as set on screen. An override saved before this keeps working.
• Fixed: a record could be filed under a character with no name. Found by review, not in play. In the moment between logging in and your character existing, Dibs could build its identity key as a realm with nobody attached to it. Every guard in the addon checks the key is not empty, and that string is not empty, so it went through — DKP entries, soft reserves and Main/Alt declarations could all be filed under it, saved, and then synced to everyone else. Nothing errors, and no later fix undoes it, because by then the record has travelled.
• Changed: the priority picker and the roll it opens now agree on which method is running. Three places read the Priority method setting and one assumed a different default, so an unconfigured guild could get a picker explaining Advantage rules over a roll that ran as Standard. That trail led somewhere worse: the “rolls twice” announcement was sent whenever names were flagged, without checking that the roll it described actually grants a second one — so the raid could be told one set of rules while another was running. The announcement is now tied to the roll it describes.
• Fixed: two descriptions that described the wrong thing. The Lost column’s tooltip claimed it counted losses on wishlisted items — “i think the description for lost is wrong, in game it’s just ‘how many rolls you lost’” — which makes a large number read as bad luck on the things a raider actually wanted. The same wrong claim was on the Show lost rolls setting, where nobody had reported it. And the Below-threshold loot setting still told you to use the Distribute mats button, which was removed a release ago, sending people to a control that is not on any window.

v0.4.4 — loot moves only while you are watching, and the greys are yours to hand out

• Fixed: the masterlooter lost their own controls in the middle of a boss. Reported live with a screenshot — “whatever you just did, makes the ML buttons across the bottom disappear for the ML”. The loot table still had its rows and a running clock, but both button bars were gone, the roster column was gone, and the title had gone back to plain Loot. Those three things are all drawn from one fact — whether this client is the masterlooter — so all three vanishing at once meant the addon had quietly decided it was not. The table stayed; the authority over it did not. The cause was a question with no way to answer “I don’t know”. Dibs asks the game who holds master loot, and that answer is genuinely unavailable for a moment now and then — while group information is still arriving after a reload, or when a raid member’s details cannot be resolved at the instant an event fires. All of those came back as a flat no, which is indistinguishable from “somebody else has it”, and the addon acted on it. Worse, the event that asks fires exactly when the answer is least available — the loot method changing, somebody joining, a player zoning — which is why it looked random. Loot authority now moves only on a definite answer naming somebody. If the game cannot say, nothing changes and Dibs waits — what it already knows is the last thing the game actually told it. A real handover is unaffected, because that comes with a name. Fixed alongside it: the status line at the bottom of the loot table kept announcing “Selection open” long after it had stopped being your window, which is what made this look like missing buttons rather than a change of role.
• Added: an Unstick button, so a stuck answer is not a reload. Reported live — “i did rolls a few times, it just ‘stopped working’”, and then “/reloading on both characters fixed it, but i shouldn’t have to do that”. WoW quietly discards addon messages when there is too much traffic, and a message whose delivery is never confirmed can leave that channel blocked for the rest of the session — everything queued behind it waiting on something that will never arrive. On a raider’s screen that is an answer stuck on Sending your answer… that no amount of pressing Resend will shift. Both loot windows now carry an Unstick button, bottom right. It releases the blocked queue and re-sends whatever was waiting. Safe to press at any time — a message that is merely waiting its turn is left alone, so nothing is ever sent twice, and it tells you which of the two happened. It is a button rather than only a command because the person it happens to is a raider who has no reason to know a command exists; /dibscomms status is there as well if you want the detail.
• Fixed: a pick that never arrived, and nobody was told. Reported live — “i tried to pick MS on a recipe drop, and it’s not being sent across”. The raider’s row sat on Sending your answer… while the masterlooter’s window still listed them as not having answered. Two checks on the masterlooter’s side could discard an incoming pick and reply nothing at all, both for temporary reasons like a handover in progress or the loot table not being open at that instant. The raider was left with a receipt that never resolved, and Resend could not help because every retry met the same check and vanished the same way. Both now answer with a reason the raider’s window shows, and the masterlooter gets a line in chat naming whoever was turned away — a refusal takes somebody out of the running for an item, and the person running the loot is the one who can do something about it.
• Fixed: the bottom of the Loot & Rolls settings could not be reached. Reported live — “the bottom of the rolls settings where the push to raid sync button is, isn’t showing”. The tab’s scrollable height was a number kept by hand beside the code that draws it, and a setting had been added without the number being grown to match. A short scroll height does not clip visibly and does not give you a scrollbar — the panel simply ends, which is why this reads as a missing button rather than a mis-sized panel. It is the second time this has happened, so the hand-kept number is gone: each settings tab now reports the height it actually drew, and the panel is sized from that.
• Changed: “N picked” moved into the roster column. The count of how many people have picked an item now sits with Raid, Waiting and Done instead of on the item row beside the buttons. It is the same kind of number as those two — how much of the raid has answered — and reading it off a single item’s row is what made it look out of place wherever it was put. One thing is lost and it is worth saying: the count is now for the whole table rather than per item, so you no longer see at a glance how many picked one specific drop.
• Fixed: a roll finished itself, and gave the item away, while the loot window was closed. Reported live — “when the ML looted an item and the popup happened and i pushed roll, and for some reason the ML closes the window, the addon randomly hands out the loot. it shouln’t.” An earlier fix made a roll survive the loot window closing, which was right: that window shuts for half a dozen ordinary reasons — Escape, stepping out of range, a knockback, closing it to read a whisper, the corpse despawning — and none of them is a decision to end the raid’s roll. What it did not do was stop the roll finishing with nobody watching. The countdown ran out, or the last raider answered, and Dibs announced a winner, wrote the loot log, spent the points and pushed the item at whoever was a candidate on whatever loot window happened to be open by then. A closed loot window now holds the roll. The clock stops. Nobody wins, nothing is handed out, and every raider keeps their prompt. Open a corpse again and the countdown restarts from full so you can see it through. Closing the Master Loot window with its X still ends the roll and still tells the raid — that one is a decision. The trade, said plainly: if you shut the loot window mid-roll and never open another, the roll stays held and the Roll button will not start a new one until you do. Loot that waits can be sorted out; loot handed to the wrong person cannot.
• Added: you decide what happens to greys, whites and mats. Dibs has had the BijouRR machinery since the beginning — the protected-item list, the below-threshold test, the random pick — and the only way to reach it was the Distribute mats button. There was no way to say “we roll for cloth in this guild”. Below-threshold loot is now an officer setting on the Rolls tab, pushed to the raid with the rest: Leave alone (the default, and exactly what Dibs did before), Roll for them (greys and whites get rows on the loot table, so a stack of Mageweave is rolled out like a boss drop), or Hand out at random (opening the corpse gives each one to a random eligible raider straight away). The protected-mats list is the exception to all three — under Hand out at random a protected item is given a row instead of being scattered, so you decide where it goes. The boundary is the master-loot threshold you set in the game’s own loot menu, not a second one hidden in the addon.
• Fixed: a /roll typed in chat could disappear without a trace. Two reports — “if a person with dibs is an idiot and does a /roll 100/1000 we need to be able to use that” and “if a person OUTSIDE of dibs does a /roll that is in the raid/party, we need to include them on that item”. If the range somebody rolled did not match the item's range exactly, Dibs threw the roll away: not counted, not shown on any window, and nobody told — not the raider, not the masterlooter. That hits hardest on the people least able to notice. A raider without the addon gets one line in chat and no window at all, so a plain /roll against an item called for /roll 1000 put them silently out of the running for loot they were invited to roll on. A roll on an unexpected range is now counted, at the bottom of the order, and the masterlooter is told who rolled what. Bottom of the order is the important half: main-spec beats off-spec, and a roll nobody can place has no claim on the top — so it wins only if nobody rolled above it, and a mistyped 99 can never take an item off somebody's correct main-spec 2. Everything else still applies exactly as before: a soft-reserved item still admits only its reservers, a tie-break only the tied players, and a pass is still final.
• Removed: the Distribute mats button. “it was always confusing and it’s better to have it as a setting” — and it was confusing for a real reason: it was a button that encoded a policy. Pressing it meant “greys are handed out at random in this guild”, which is a standing rule about how your raid runs, being re-decided on every corpse by whoever happened to be looting, with nothing recording the answer. The setting above says it once and applies it everywhere. Nothing is lost: the same hand-out still happens, on Hand out at random, and it tells you in chat how many items went out.
• Note: Hand out at random is the only thing in Dibs that moves loot with nobody pressing a button, and it is off unless an officer turns it on.
• Fixed: the loot window opened on every trash mob. Reported from a live raid — “ML window appears every time looting a corpse, even if corpse is blank”. v0.4.3 fixed half of this and it was the rarer half. That release stopped a window opening on a corpse with nothing lootable at all — money-only, or already looted — but deliberately kept the “No tradeable loot on the corpse” notice on a corpse of greys and cloth, because that is the corpse Distribute mats exists for and that button lives on the notice. True, and beside the point: a raid pulls dozens of trash mobs an hour and nearly every one of them drops something below the loot threshold, so in practice that was a window on nearly every corpse in the instance. Looting a corpse with nothing above the threshold now opens nothing at all — no loot table, no notice, no Master Loot window. The notice has not gone anywhere; it is on demand. Press Loot table, or type /dibs loot while standing on an open corpse, and you get it. (This originally said the notice also carried Distribute mats, which was true when it was written and stopped being true in this same release — that button is now the Below-threshold loot setting above.) The rule, stated once: a button you pressed deserves an answer, an event you did not ask for does not deserve a window.
• Changed: /dibs loot now works on a corpse, not just on a live table. It used to re-open the loot table only when one was already running. If there is no table and you are the master looter standing on an open corpse, it now builds one for that corpse — the same thing the Loot table button does. It refuses for anyone who is not the master looter, so typing it out of habit mid-raid cannot put a second loot table on the wire.

v0.4.3 — rolls wait for the raid, empty corpses stay quiet, the masterlooter window opens, and loot stops getting stranded

• Added: the roll window tells you whether it is an upgrade, without a hover. The roll prompt now carries the same vs. yours column the loot browser, the Planner, the Master Loot window and the loot table already had: a green +40 or a red -15 against what you are wearing in that slot, drawn beside the item name. You can see whether a drop is worth rolling on by looking at the prompt, rather than hovering it while a countdown runs. Both prompts have it — the masterlooter’s roll call and Blizzard’s own Need/Greed roll. It stays blank rather than guessing on a random-suffix drop (“of the Owl” — those stats are not on the base item, so a number there would describe a different item) and on anything your class cannot use (otherwise a wand’s damage lands on a hunter’s ranged weighting and reads as a huge upgrade). A green number you can trust is worth more than a number on every row.
• Fixed: “script ran too long” on a low-level character. Reported from Classic Hardcore on a level 2 character, thrown out of the Planner. Dibs works out which talent tree you have spent the most points in and remembers the answer — but it only remembered it once it found points spent, on the assumption that finding none meant your talents had not loaded yet. Nobody below level 10 has a point to spend, so the answer was never remembered and was worked out again from scratch on every single call — and it is asked once per item, while the Planner scores hundreds of items in one frame. Dibs now tells “your talents have not loaded” apart from “you have not spent anything”, remembers the second, and re-checks the moment you spend your first point. Fixed silently alongside it: Dibs was calling a deprecated talent function that only exists when a particular client setting is switched on — with it off, spec detection failed quietly and scored you as unspecced for ever. It now calls the current one.
• Fixed: a winner was declared before the raid had finished rolling. From a live raid log — one player rolled 70, the winner was announced as that player, and the next line in chat was somebody else rolling 12. “and now it chose a winner before all the rolls were in”. A loot-table row ends its roll as soon as everyone it is waiting on has rolled, and that list was built from who had ticked the row on the table — but the roll announce in chat invites the whole raid, including people who left the row blank and people not running Dibs at all. So a row one person had ticked resolved the instant that person’s dice landed, while everyone else was still reading the line telling them to roll. A row now only ends early when every player who may act on it has actually answered it, counting a Pass as an answer. The trade, said plainly: a row somebody left blank runs its full countdown again. Waiting costs a few seconds; resolving early costs somebody the item.
• Fixed: an empty corpse popped a window telling you there was nothing on it. “and now i’m getting this on an empty corpse”, with a screenshot of a loot table holding nothing but “No tradeable loot on the corpse”. Two very different corpses looked identical to Dibs: one that dropped only greys and mats — which is exactly what that notice and its Distribute mats button exist for — and one with nothing lootable on it at all, money-only or already looted. Both got the notice. Dibs now tells them apart, so the mats corpse keeps its window and the empty one gets none. Pressing Loot table yourself still answers on both, deliberately: a button you pressed deserves an answer, an event you did not ask for does not deserve a window. Walking over an already-looted corpse also no longer disturbs a loot table you left open on the last boss.
• Fixed: the masterlooter could be left waiting on their own answer, for ever. The loot table’s roster and its record of who has answered were written by two different pieces of code using two different spellings of a player’s name, and only one of them had been tidied up. Where those spellings differed for the masterlooter, their own click was filed under a name their own roster did not contain — so the table counted them as still waiting, the “everyone has answered” check could never come true, and the clock went back to being the only thing that could end selection. The tell was Waiting (1) naming the masterlooter with their choices visibly made on the rows in front of them. Both writers now use one spelling — and so do the five places that read it back, one of which was the handover: when a masterlooter drops and someone else takes over, every raider re-sends their own answers, and that lookup was finding nothing and re-sending nothing, silently. Five new tests pin it, including one that puts the bug back and watches the handover send zero answers instead of two.
• Changed: one window on the corpse, not two. Reported from a live raid with a screenshot of both windows up at once — “i’m still getting the other window”. Looting a boss opened the loot table and the old Master Loot window side by side, listing the same drop twice. The loot table is the window now. Open a boss with real loot and you get one window. The two cases where a table cannot open — an auction raid, and a corpse with nothing above the loot threshold — land on the loot table as a notice instead, which is what carries Distribute mats onto a corpse of greys. The Master Loot window is the fallback only when even the notice cannot be shown, because a refusal nobody can read is worse than an extra window.
• Changed: the roll timer is a bar again, under the item it belongs to. The countdown used to sit in the Master Loot window’s title corner, where it told you how long was left and never what it was left on — and on a boss with twelve drops that is the more useful half of the question. It is now a thin orange bar across the row being rolled, draining smoothly until it is gone, the same bar the old single-item roll prompt used. It appears on the row the masterlooter called and on no other, so the clock names its own item.
• Fixed: forgetting to press Finish no longer costs you the next corpse. Reported live — “if i forget to finish, and start looting again, it should go ahead and finish and pull up the new loot window. it doesn’t right now. i have to close and reloot.” Opening a corpse while an old loot table was still up did nothing at all, because the only check was “is a table already live”. That check exists for a real reason — re-opening the loot window on a boss you are part-way through fires the same event, and starting over there would throw away every selection the raid had already made — but it could not tell that case from the next boss, and answered both by leaving the stale table up. Dibs now compares the drop against the table’s rows. Everything already on the table means the same corpse and your selections are kept; anything new means a new corpse, so the old table is finished for you and this one opens. Items are matched including their random suffix, so two different “of the …” versions of one item count as two different drops. A table you did not start — one you are receiving as the raid’s master loot changes hands — is never closed out from under the raid.
• Changed: Fix tiers and Distribute mats moved onto the loot table. Both now sit on a second row of buttons at the bottom of the loot table rather than on a separate window. The two rows split by what they act on: the top row is the table — start, pause, lock, begin, finish — and the bottom row is the corpse. The window is slightly taller to hold it.
• Fixed: “Decide main/alt for me” now tells you when it could not decide. Reported as a regression — “i have it set to auto and it’s giving me the choice”. It was not one: the setting had declined to answer for that particular drop, which is deliberate, and most often because the item has a random suffix — a suffixed drop’s stats are not on the base item, so scoring it would be scoring a different item, and Dibs would rather ask than guess wrong. The defect was that it never said so. Two buttons with the setting on looked exactly like two buttons with the setting off, so a correct refusal and a broken setting were the same picture and there was no way to tell which you had. Such a row now carries a quiet “Auto tier could not decide — pick one”, and hovering either button names the actual cause: a random suffix, a Main/Alt declaration that is not finished, no declaration at all, or two setups that score the item too closely to separate.
• Fixed: your main and off-spec choices never reached anybody after the first time. Reported from a live two-account test: “the sync problem is with syncing the main spec and alt spec choices”. Saving a declaration never wrote a version number — it recorded when the declaration was locked, and left unset the one field the sync sorts on. So every declaration Dibs has ever saved travelled as version zero, and the receiving client refuses anything not strictly newer than what it already holds. Zero is never newer than zero, so a raider accepted the first declaration they ever saw from you and silently discarded every change after it: re-spec, re-declare, relog, and their copy of you stayed frozen at whatever you were the first time your two clients met. It failed in the direction that hides it — the change detection did notice, the two clients did negotiate, and the record really was sent; it was thrown away on arrival with no error and nothing in chat, which from outside is indistinguishable from it never being sent. Declarations you have already saved are fixed without you doing anything, which matters because saving locks a declaration — “just save it again” would have meant every raider asking an officer to unlock them first. The lock stamp has always been recorded, so it stands in as the version where the newer field is missing.
• Fixed: the roll popup asked you again for a choice you had already made on the loot table. You tick Main, Off-spec or Pass on the loot table, the masterlooter presses Roll, and a roll picker opens asking the same question — for a row the table beside it is already showing as answered. Two windows asking one question is worse than a missing window, because the two answers can disagree and only one of them is the one the row acts on. The first fix for this only fixed one person: the check went into the code that starts a roll, which runs on the masterlooter’s client and nowhere else, so the masterlooter stopped being asked twice and everybody else carried on being asked twice. Both sides now ask the same question, and they ask it per item — a second drop off the same corpse still gets its own prompt, and a drop the table has no answer for still prompts, because otherwise there is no way to ask you at all. It suppresses the question and never the roll.
• Fixed: an Advantage announced the lower of the two rolls. From a raid chat log: the raid was told “roll ONE range twice … your higher roll counts”, the player rolled 41 and then 59, and the winner was announced as 41. The cause is a name spelling. Every part of a roll session tolerates the realm suffix except the one deciding how many rolls you are allowed: the eligible list comes from the group roster and carries the realm (Thorium-Azuresong), while a /roll arrives from the game as a bare name (Thorium). They did not match, your allowance fell back to one, and the second roll was silently discarded — so the player was publicly promised two rolls, took them, and had one thrown away. An unflagged player still gets exactly one roll; that is pinned by its own test, so a too-eager match cannot hand the whole raid an advantage.
• Fixed: the loot table kept counting down after everybody had answered. Reported with a screenshot showing “Waiting (0) — Everyone has answered”, “Done (2)” and “2 of 2 have finished” — with the clock still running from 114 seconds. Nothing ever looked at the waiting list emptying; only the clock could end a selection. It now closes the moment nobody is outstanding, whether the last answer came from a raider or from the masterlooter’s own click, and it closes through exactly the same path the clock uses so nothing downstream can tell the two apart. Only the masterlooter can end it, and an empty roster counts as “not everyone” rather than “everyone”, so a table built before the roster has resolved cannot lock itself the instant it opens.
• Fixed: a roll could open for the whole raid and be answerable by only part of it. Whether a roll is restricted to the people who reserved the item was worked out twice — once when the roll was set up and once when it went out to the raid — and the Advantage picker opens in the gap between them. That setting is pushed by officers, so it can change in that gap. Set up unrestricted but sent restricted means the roll waits on all forty people while only the reserve holders are ever asked, so “everyone has answered” can never come true and the roll burns its full countdown. That is the same stuck-timer symptom as the masterlooter’s missing prompt arriving by a completely separate route, which is why fixing the prompt did not fix the timer outright.
• Fixed: the My Main / Alt window drew its status message straight through its own buttons. Reported with a screenshot. The message was inset far enough to clear the Save button and nothing else — and Request unlock is wider, and exists only in the locked state, which is the one state with the longest message to show. The status line has a row of its own now and the window is wider to fit it. This is the third window in this addon to have had the same defect, so it is now pinned by a test that measures where things actually land on screen rather than what they are anchored to — an anchor test passes on all three.
• Fixed: Dibs now speaks up again when the group changes, not only when you log in. A guildmate who loads in ten minutes after you would never receive your declarations. The exchange is one-directional — the client that speaks learns what the other one holds, and the one that listens does not — and Dibs only ever spoke at login plus a handful of button presses, so whoever was online first broadcast into an empty room and was finished for the session. It now re-broadcasts when the group roster changes, debounced so an invite storm costs one pass rather than forty.
• Fixed: “Fix tiers” did nothing, and it was the moment it is most wanted that broke it. The button was drawn, its tooltip worked, and clicking it opened nothing at all. Two correct decisions had cancelled each other out. The button deliberately stays on screen after the roll resolves — that is the whole point of it, because a wrong tier is noticed when the winner is announced. Separately, and just as deliberately, resolving a roll clears the roll’s state, because a finished roll left lying around reads as a live one. So from the instant the winner was announced the button was live, visible, and pointed at nothing: no error, no message, which in game is indistinguishable from a dead button. The last finished roll is now kept for exactly as long as the button offers to correct it — until the next item is rolled, or the loot window closes. It deliberately does not re-award the item: a correction made after the winner was announced changes the record and is announced to the raid, but does not move loot that has already moved.
• Fixed: the masterlooter got no roll prompt — and that is also why the countdown never ended early. The masterlooter had the loot table and the Master Loot window and no way to want the item themselves. They now get the same roll prompt every other raider gets, on every roll they start. The second symptom is the one worth reading, because nothing about it looks related: a Dibs roll ends early once everyone has answered, and “everyone” is the group roster — which includes the masterlooter. With no window to answer in they were permanently outstanding, so the check could never come out true and every roll burned its full countdown however fast the raid answered. One missing window, two bugs. The prompt is drawn locally rather than waiting for the broadcast to come back round, so it appears even when the roll could not be sent; and the loot table is untouched, because its rows deliberately do not send that message.
• Fixed: changing the loot table’s countdown did nothing until the next boss. Reported as a setting that would not save — the length was changed from 120s to 20s and “it didn’t take”. It had saved: nothing on an open table ever read it again. The length is sampled once, when the table is built, so Restart replayed the length the table was born with and the new number would not appear until the next corpse. From outside, that is indistinguishable from a setting that failed to write. Restart now re-reads the setting and tells the raid the new number so nobody’s clock disagrees with the masterlooter’s. A running clock still never changes length underneath a raid that is already answering against it.
• Fixed: the masterlooter was the one person who could not answer their own loot table. Reported with a screenshot: the roster read “Waiting (1) Galdof” against a status line saying “Selection open — 1 of 2 have finished”, and there was no control on screen that could make it 2 of 2. Galdof was the masterlooter. Their view drew their own controls — call this row, correct that one — and hid the Main / Off-spec / Pass buttons outright, so the person standing on the corpse, who has a main and an alt like everybody else, was structurally unable to want anything. They get the same three buttons as the raid now, on the same rows, beside the controls they already had.
• Changed: with “Decide main/alt for me” on, the loot table asks Roll or Pass rather than MS or OS. The roll popup has collapsed its two tier buttons into one since that setting shipped; the loot table never did. So a player who had switched on the one option whose entire purpose is to stop asking which tier they are rolling was still being asked — on every row of every boss, which is many more times than the popup asks it. A row your setup can decide now shows one Roll and a Pass. Pass is never collapsed away, because the setting removes the main-versus-alt choice and never the choice of whether you want the item at all, and a row it cannot decide keeps both buttons — random-suffix drops especially, which cannot be scored from the base item and must never be guessed. The label changed and the choice did not: the button still sends the tier your setup picked, with that tier’s roll range, and the tooltip names which one and how to switch the setting off.
• Added: the loot table now tells you who won each item, and on what roll. You picked your items, the window said “Selection is closed. Wait for the master looter to call each item”, and then nothing on it ever changed again — it showed your own receipt and never the outcome, so the only record of who actually got the drop was raid chat scrolling past. The reason was structural: the table’s messages describe it being built, clocked, called and closed, and not one of them carried a result. The masterlooter’s own copy had the winner and the winning roll the whole time; nothing sent it. Each row now shows the winner and their roll the moment the masterlooter resolves it, in the same words their window uses. A row nobody won says so — that is the difference between being beaten and the item going nowhere.
• Fixed: the loot table is the raid’s window, and it only ever arrived if the masterlooter fetched it. Reported from a live run: a raider only saw the loot table when the masterlooter opened it by hand. It is the raid’s window, not the masterlooter’s — the whole point is that everyone sees the boss’s drops as one list and marks what they want before anything is rolled, so a table that arrives only when one person remembers to send it is a table the raid mostly never sees. Every piece of it already worked, which is why it lasted: the snapshot was right, the broadcast was right, and a raider receiving one already popped their window open on its own. The only thing missing was the trigger. It now opens on the same moment the masterlooter’s own window does — looting the boss — so both arrive together, for everyone, with nobody having to remember anything. It will not restart a table that is already running, which would otherwise throw away every selection the raid had already made; and it still refuses in an auction raid or on a corpse with nothing above the loot threshold.
• Fixed: whoever logged in first stopped talking to everyone else, and never started again. Reported with a screenshot from each of two clients: two guildmates, same guild, same party, both with a saved Main/Alt — and each one’s Accounts tab listed only itself. Part of that was the tab reading the wrong list (below), but the tab stayed wrong afterwards because there was nothing to read. Dibs announces what it holds when you log in, and after that only when you actually change something. Everything else was meant to be covered by the sync library’s catch-up: a broadcast that finds nobody home retries a few times over the next few minutes — which is exactly what happens when your guildmate loads in three minutes after you do. Dibs had that switched off. Asked “do you still need anything from anyone?” it answered a flat no, which the library reads as “I am complete, stop retrying” and abandons catch-up for the rest of the session. So the first person online broadcast into an empty room and was finished broadcasting forever. It answers yes now, because Dibs genuinely cannot know whether somebody out there holds a declaration it has never seen — and the library caps that at a handful of retries a minute or so apart before it stops on its own.
• Fixed: an automatic roll’s button then claimed the drop was not for that tier. When Dibs rolls for you, the button it pressed stays on screen with its tooltip — and that tooltip reported the opposite of the decision that had just been acted on, telling you the drop was not for the tier it had this second rolled you into. Nothing was rolled wrongly; the roll was right and the explanation beside it was wrong, which is arguably worse on an option whose whole job is to be trusted without being watched.
• Fixed: automatic main/alt could put a random-suffix drop in the wrong tier. Reported live — a holy priest was rolled as alt on Aboriginal Footwraps of the Owl. On a random-suffix item (“of the Owl”, “of the Bear”, and the rest) every stat the suffix grants lives in the suffix, not in the base item — and the base item is what Dibs was scoring your two declared specs against. With almost no stats to compare, the difference between them was noise, and noise is all that check needs to pick a side. Dibs now spots a random suffix and asks you instead of guessing, which is what it did before the setting existed. Weapons are unaffected: a sword is still a sword whatever suffix it rolled, so weapon-based main/alt splits still answer automatically. Expect it to ask more often than it used to — suffix armour drops constantly in Vanilla, and every one of those was previously being answered from an item that does not exist.
• New: Dibs can send the roll for you, not just pick which button to press. “i was hoping the addon would just do the roll automatically for each plyaer” — and that was the original ask; only the choosing half had shipped. Roll for me automatically is a new per-player option on Loot & Rolls, directly beneath Decide main/alt for me. With both on, the roll goes out the moment the window opens and you never touch it. It only fires when your Main / Alt setup picked a tier outright — if Dibs has to ask, both buttons are still there and it waits for you, so the automatic roll can never be more confident than the decision behind it. Off by default, and deliberately a separate switch from the tier option: wanting the tier chosen for you is not the same as wanting the roll sent for you, and only one of those cannot be taken back. With it on you roll on every drop your setup can classify, including ones you did not want, and you can win them.
• Fixed: a hunter was being told to roll main spec on cloth. Reported as “on a hunter i should not have MS roll for a cloth item”. Every check Dibs had asked which of your two setups a drop was for; none of them asked whether it was gear for your class at all. Cloth bracers on a hunter passed all three — no weapon type to read, no spell school, and two gear scores that were identical because that player’s two setups named the same spec — so the main-spec default answered. There is now a check ahead of the others: body armour lighter than the armour your class actually gears in is never a main-spec roll, and it overrides the rest, because “this is not your armour type” outranks anything your two setups have to say. It is not the same as “can you equip it” — a hunter can put on cloth, and Dibs already knew that; being allowed to wear something is not the same as gearing in it. It knows about levelling: hunters and shamans do not train Mail until 40, and warriors and paladins do not train Plate until 40, so a level 13 hunter’s leather is still main-spec gear and only cloth is demoted. Cloaks, rings, necks and trinkets are untouched — every class wears those whatever their armour type.
• New: the Master Loot window shows what a drop is worth against what you are wearing. A column beside each item — green for an upgrade, red for a downgrade — using the same number and the same colours as the Loot browser’s vs. yours column, so you can see whether a drop is an upgrade without hovering anything. It is blank rather than zero when the item is one you cannot use or one Dibs has no scores for, because a confident 0 on a drop that was never scored is worse than saying nothing.
• Fixed: every cloth drop was being read as a two-handed weapon, and every plate drop as a one-hander. This is the real cause of automatic main/alt putting armour in the wrong tier. WoW numbers item subtypes separately for each kind of item, and the low numbers collide: as a weapon, 1 means two-handed axe — as armour, 1 means Cloth. 4 is a one-handed mace, or Plate. 0 is a one-handed axe, or the “miscellaneous” bucket holding rings, necks and trinkets. Dibs was feeding that number to its weapon check for every item, so the check was not occasionally wrong on armour, it was systematically wrong: a pair of wrist bracers came back as a two-handed weapon, matched the player’s two-hand off-spec setup, and settled the tier before anything else was even looked at. If your Main/Alt setup splits on weapon type, whole categories of armour were being sorted by nothing but a number collision. The weapon check now ignores the subtype unless the item is genuinely a weapon.
• Changed: /dibs tier now names the check that actually decided. The report listed all three checks and then the answer, leaving you to work out which one spoke — and the gear-score numbers print last, right above the verdict, so they look like the cause even when something further up already settled it. Each check now marks itself when it is the deciding one, says when an earlier check got there first, and points out when both your setups name the same spec (which makes their scores identical no matter what the item is).
• Changed: automatic main/alt now asks whether you are rolling for your main, not which of your two specs likes the item more. Reported live — “i’m getting OS on a clothie and this item is MS for a clothie”, on Crystalline Cuffs (+1 Intellect, +2 Spirit) for a holy priest with a shadow off-spec. No random suffix this time, the setup was read correctly and the gear scores were right: the question being asked was the wrong question. The old check weighed your two specs against each other and refused when they came out close — but main spec versus off spec does not mean “which spec likes this more”, it means “am I rolling for my main?”, and a holy priest rolling on intellect and spirit cloth is rolling for their main whether or not shadow wants it too. So the check is deliberately no longer even-handed: your main setup keeps the drop on ties, near-ties and anything it leads, and your off-spec only takes one when it decisively out-scores your main — by exactly the margin the old check used, so genuinely off-spec drops are unchanged. An item neither of your setups can use is still refused and still asks you, and that test runs first so it can never fall into the main tier by default. Expect it to ask far less often: two specs that want the same gear — marksmanship and beast mastery, holy and discipline — used to be unanswerable and now answer main, which is what you would have clicked. Weapons and spell schools are untouched, and random-suffix drops are still asked rather than guessed.
• Fixed: the bottom of the General settings tab could not be reached. The tab scrolls, but it was telling the scrollbar it was far shorter than it really is, so the last button or two simply had nowhere to scroll to. It measures itself properly now — including the fact that an officer sees one more button there than everyone else.
• Fixed: the reserve-limit buttons could edit a raid you never picked. Opening the Soft Reserve tab published a raid as though you had chosen it — the tab needs something to show, so with no saved selection it displays whichever raid sorts first, and it was writing that guess into the same place the rest of the addon asks “which raid did the officer pick?”. The new settings +/- was meant to refuse when nothing is selected, and instead the refusal only held before you had opened the Soft Reserve tab, which is to say only while you could not reach the buttons anyway. It also appeared after visiting that tab, vanished after a /reload, and came back on the next visit. The guess is gone: the raid picker is the only thing that answers now, and it saves your choice.
• Fixed: the reserve-limit tooltip always read “Soft-res limit: 1” whatever the raid was actually set to. It takes the live value now, and re-reads it after each click.
• Changed: the reserve limit is set in Soft Reserve settings now, not on the Soft Reserve tab. The “Soft-res limit: N” badge used to have a - and a + beside it, sitting on the page every raider spends the whole pre-raid on — and one stray click there changes what all forty people are allowed to reserve. The badge has not moved, because reading your allowance is what it is for; only the two buttons went, into Settings → Soft Reserve → Reserves per player, behind the same officer check they always had. The limit is stored per raid, so the settings row names the raid it will change — the one selected on the Soft Reserve tab — and says so plainly rather than quietly editing whichever raid happened to be first.
• Fixed: guildmates who were not even in the raid got roll popups. Reported as “people with dibs not in the party/raid are getting roll popups”. When an officer started a roll, Dibs sent it to the whole guild as well as the group — so anyone who had wishlisted that item got a prompt to roll on a boss they were not at, from another zone, another instance, or while standing in a city. Rolls, loot tables and bid popups now go to the group only. Officer settings pushes still reach the whole guild, which is what that was for: a guildmate who is not raiding tonight should still get the guild’s soft-reserve setup.
• Changed: the loot tooltip now scores the drop for everyone in your group, not just the people it is best-in-slot for. Reported with a screenshot of a green world drop whose tooltip carried every other addon’s section and nothing from Dibs: “the loot popup window is supposed to show the EP of the item for everyone in the raid/part, so the ML can see who it is ‘best’ for”. The old block only named the classes an item was best in slot for — and most drops are best for nobody, which is exactly when a masterlooter still has to give it to someone. It now lists what the drop is worth to each class standing in your group, ranked, with the best-in-slot ones tagged. Hold Ctrl to expand it — collapsed it is a single line with a count, so it never takes up space you did not ask for. (Ctrl and not Shift, because Shift already toggles the game’s item comparison on the same tooltip.)
• Fixed: an advantaged player could not actually take their second roll. “so it said my highest roll counts, but it should show both of them. or is there a bug to where it’s only rolling once?” It was rolling once: the popup fired one roll and put its buttons away. The button you used now becomes Roll again and spends the second roll — locked to the range you rolled first, because best-of-two keeps your higher roll and the spec category it was in, so a main-spec 21 followed by an off-spec 900 would be kept as an off-spec 900 and rank below every main-spec roll. Rolling twice could have lost you the item.
• Fixed: an Advantage roll never told anyone it was an Advantage roll. Reported as “i gave galdof the advantage, and he only rolled once” — and he would have. The rules were applied correctly and announced to nobody: the raid saw an ordinary “roll on this, /roll 100”, so a player given a second roll had no way to know they had one. The only person who ever saw it was the masterlooter. Dibs now names the flagged players in chat, right under the roll announcement. Manual gets its own wording, because there the same tick decides who may roll at all — until now everybody else’s roll was quietly ignored and they simply were not in the result. It goes to chat rather than the popup on purpose, so raiders without the addon read it too.
• Fixed: an auction could charge the winner and leave the item on the corpse. If the loot window closed while an auction was running — Escape, stepping back from the corpse, closing it to read a whisper — Dibs forgot which item was being sold. Nothing looked wrong: the auction window stayed up with the bid on it. Clicking Award then took the bidder’s points while the item stayed in the corpse. Auctions now survive the loot window closing, exactly like rolls do, and an award that cannot identify its item refuses instead of charging for it.
• New: every button in the roll popup explains itself. Hovering Need, Greed, Pass — or MS and OS on a masterlooter roll — now says what pressing it does and how that decides the item: that any Need beats every Greed, that off-spec only wins if nobody rolled main spec, and that passing is reported straight away so the roll can end as soon as everyone has answered. A greyed-out button still tells you why you cannot use it, as it always did.
• Fixed: the priority picker drew its instructions on top of its own first tickbox when the item name was long. The list now starts below however many lines the text actually took, at any width and in any language.
• Fixed: the masterlooter window would not open at all for some people. Reported as “i’m still not getting any masterloot windows” from a guild running plain rolls against wishlists. Dibs was asking the game a question through an old, retired function, and on some clients that function simply is not there — so Dibs believed nobody was master looter and correctly refused to open a window for a raid that plainly had one. This is why it happened to one person and not to someone else on the same build, and why it looked like a phantom for weeks. Dibs now asks the current function, and understands both answers, so every supported game version keeps working.
• Fixed: roll prompts that you could not get rid of. Two prompts stacked on a raider’s screen, both stuck on “Sending your answer…”, for items the masterlooter had already rolled out and announced. A masterlooter-driven prompt had no ending of its own — the countdown that really ends the roll runs on the masterlooter’s client, so every way that window could close was a message that might never arrive. Now the masterlooter tells the group when a roll is finished and the prompts close themselves, and every prompt carries a close button so you are never stuck with one regardless. Closing sends nothing — a roll you already made is public and still counts.
• Fixed: a winner who was out of the instance left the item stuck on the corpse. Somebody outside the raid won a roll, and the window said “couldn’t auto-assign — hand it out manually” — but there was no way to do that, because handing loot out by hand uses the same list the automatic path does. The only option left was to let the corpse despawn with the item inside it. The item now goes to the masterlooter to pass out, the raid is told in chat so somebody remembers to trade it over, and the winner keeps the win — they are still charged, and the loot log still records them, not the masterlooter.
• New: /dibs debug, for when nothing happens and nobody can say why. It prints what your client actually sees — the version, whether loot handling is on, the loot method, who the masterlooter is, whether that is you, and which required libraries failed to load. That last one is the important one: a missing library is completely invisible in-game, because the windows that needed it just never open. Paste the output into a bug report and the first four rounds of questions are already answered.
• Changed: the “Best in slot for” tooltip now shows each class’s score, best first. It listed class names alphabetically, and in a thin slot that reads as though half the raid wants the drop equally. Each class now gets its own line with its score beside it, ordered by that score — so the top line is the answer, and a long tail tells you the slot simply had nothing better in it.
• Fixed: the masterlooter window’s status line was drawn straight across its own buttons. It has a row of its own now.
• New: the roll countdown is now visible, ticking down, in the Master Loot window. Reported as “we need to see the roll timer somewhere in the loot window counting down”. The clock that actually ends a roll runs on the masterlooter’s own client, and nothing ever showed it — so you set a countdown in Settings, pressed Roll, and then could not tell “this is nearly over” from “this has hung”. It sits on the window’s title row and turns red for the last five seconds, which is when you decide whether to let it run out or call it early. And the raider’s own popup now has a countdown too: the bar it always had rendered nothing on a Dibs roll, sitting at empty — which is worse than no bar, because it reads as a clock that has already run out. The roll’s length now travels with the roll, because it is the masterlooter’s setting and not yours. Your bar running out does not close the prompt: the masterlooter’s clock is the real one, and closing on a local guess would take the window away while your answer was still in flight.
• New: “Decide main/alt for me” — stop being asked which tier you are rolling. Asked for as “when the roller window pops up, i have to chose if i’m main/alt rolling ... I don’t want to do that. I want to set it once somewhere in the UI, and have the roller just know.” You already declare a Main and an Alt setup — a spec, a weapon layout and an optional caster school. Tick this on the Loot & Rolls settings tab and the roll prompt reads it instead of asking: a rogue with swords-main and daggers-alt gets the answer on every weapon that drops, and a fire mage with a frost alt gets it on anything carrying a school. It is off by default and the buttons are unchanged if you leave it off, and it is yours, not your officers’ — it cannot arrive on an officer’s settings push, and a raid can run with a mix. When a drop genuinely cannot be told apart by your two setups — a hunter whose main and alt want the same bow — it asks, exactly as before, rather than guessing. The tier it did not pick is greyed, never hidden, so a mis-click can never leave Pass as the only thing you can press.
• Changed: “best in slot” now says which raid it is best in slot for — when that is not obvious. The per-class values on a loot tooltip are judged against a raid, because an item can be Molten Core best-in-slot and not worth an enchant once Naxxramas opens. That raid comes from one of two places, and they are not equally trustworthy: the instance you are standing in, or the raid picked on the Soft Reserve tab when you are not in one — and the second is a stored choice of unbounded age, possibly last week's raid, possibly picked by someone who has since logged out. The words on screen were identical either way. The expanded block now names the raid when the answer came from that stored selection, and stays quiet when you are standing in the raid, where you can already see where you are. The one-line collapsed form is unchanged.
• New: the masterlooter can fix a roll that went into the wrong tier. Asked for in the same breath as the option above: “also, we need a way to fix that on the ML side if someone gets the wrong one”. A Fix tiers button appears on the masterlooter window as soon as somebody rolls; it lists everyone who has rolled with their number and the tier it counts as, and clicking a tier changes what that roll competes in. This is not a repair kit for the automatic option — the commonest wrong tier is a raider without the addon reading the announced ranges out of chat and typing the wrong one, which no setting can prevent. Nothing is re-rolled and nobody is asked to roll again: the roll stands exactly as thrown, only which tier it competes in changes. Nothing happens until you press Apply, so opening it to look cannot change the result — and a correction is announced to the raid, because a tier change can move the item and a second announcement with no reason given reads as the addon being wrong. It stays available after the winner is announced, which is when a wrong tier actually gets noticed.
• New: an Accounts sub-tab on Attendance — who plays what, on one screen. Asked for as “we need to track alt/main also in a subtab on one of the main tabs. so officers/people can see the main/alts tied to one account”. Every character grouped under the main it is declared against, alts indented beneath it, each row showing the role, the declared Main / Alt specs, and whether that declaration is currently locked. It is read-only — editing stays in the declaration window, which owns the lock — and it reads the main/alt linkage through the same resolver the standings’ “Group alts” tick already uses, so the two can never disagree about who belongs to whom.
• Changed: locking and unlocking a Main / Alt are both recorded decisions now, not flipped switches. A declaration locks the first time it is saved, so nobody can quietly change their main between raids, and only an officer — or the raid leader / master looter in a pug — can release it. Both sides used to be a value set on one person’s client: nothing recorded who decided or when, no other client could see it, and the next copy of the declaration to arrive could undo either. Now the player mints the lock when they save and an officer mints the unlock, each a record naming who and when. The key covers your whole account’s main/alt table — every character, what each declared, and which one is your main — because the usual reason to ask for an unlock is to move your main to another of your toons, which changes more than one character at once. So an unlock releases the account, and any character on it can ask. Re-declaring re-locks, and the same approval cannot be spent twice.
• Fixed: the My Main / Alt window had no way in unless soft reserve was switched on. Reported as “we had the main/alt in the framework, with a lock and an officer needed to undo it ... you just stopped surfacing it”. Nothing had been removed — the window, the lock on first save and the officer-only unlock were all still there. It had lost its door: the only button that opened it lived on the Soft Reserve tab, and once every loot system became opt-in that tab is hidden for a guild that does not run soft reserve. On a fresh install there was no way to reach your own main/alt setup at all, which matters far more now that ordinary rolls read it too. There is now a My Main / Alt button on the Loot & Rolls settings tab as well, where the option above sits — a second door, not a move.
• Fixed: an officer’s Main / Alt unlock only worked on the officer’s own screen. Locking and unlocking became recorded decisions rather than flipped switches, and then those records never left the client that made them. An officer pressed Unlock, their screen showed it released, and the person who actually had to re-declare was still locked out — which is exactly what the old switch did. The records now sync to the group, so an approval reaches the player it is for, an officer can tell a frozen main/alt table from a never-declared one, and a client that catches up on a whole raid night’s worth at once gets the same answer as everybody else regardless of what order they arrive in. A spent approval still cannot be reused: declare, unlock, re-declare reads as locked on every client. /dibs sync now reports this log too — how many records you hold, how many came from other people, and how many were refused.

v0.4.2 — caster gear drops and you have no idea who it is for

• New: hover any drop and Dibs names the classes it is best-in-slot for. Straight from live use: “as masterlooter, could I have tooltips on loot as to which class/spec for its BiS? I can see my own, but if caster gear drops I have no idea.” The masterlooter window and the loot table window now add a Best in slot for line to the item tooltip, naming the classes and specs — class-coloured, and scoped to the raid you are actually in, because an item can be Molten Core best-in-slot and not worth an enchant once Naxxramas opens. It reads Priest (Shadow) when one spec wants it and just Warrior when every spec of the class does.
  • It is the same answer as the planner’s BiS badge, asked backwards. The badge takes your gear list and finds the best item; this takes one item and finds the classes it is best for. Same rules on both sides — per slot, per raid, and only for classes that can actually equip it — so your planner and the loot row can never contradict each other in front of the raid.
  • It uses the community-standard stat weights, not yours. This line is shown to you about other people, so if it followed your own Weights-tab edits, two officers would announce different answers for the same drop and the raider it is about would have no way to see why.
  • It is information, not a rule. It never decides who may roll — “best in slot for a fire mage” is what a stat weighting thinks, while who is allowed to roll is what your officers decided. Dibs keeps those apart on purpose.

Older releases are in CHANGELOG.md, which ships with the addon, and on the GitHub releases page.

Known issues

Planner and Wishlist — reported from live play, not yet fixed:

• Your characters are listed twice in the character dropdown.
• Switching character on the Build tab can leave the previous character's equipped gear on the paperdoll, and the gear lists may then show “no matches” for every slot. Pressing Reset clears it when you swap toons — but not when you change the dropdown, which is the case still to fix.
• The “no matches for this slot” message runs off the edge of the window instead of wrapping onto a second line.
• The Wishlist doesn't say which boss drops an item. You can see that an alt wants something from Stratholme, but not whether that is Live or Dead side, or which boss.

Loot and DKP:

• DKP is auditable, not secure, and that is a decision rather than a gap. Any WoW addon can be modified, and Dibs cannot prove a points entry really came from the officer it names — so a determined cheat running an altered copy could credit themselves. What you do get is a full append-only history: every entry shows the amount, the reason, who recorded it and when, so an award nobody made is visible to anyone who looks. Treat the ledger like a paper record and check the history if a balance looks wrong. Cryptographic signing was considered and dropped: only officers can create a points entry in the first place, and a dishonest officer is a bigger problem than an addon can fix. The ceiling is deliberately detectable and attributable, not preventable.

Older versions and full developer notes are in the addon's CHANGELOG.md (ships with the addon).

Credits

Pimptasty — author.

EP stat weights — HawsJon / Pawn / Vger (CC BY-NC-ND). Item metadata, drop sources, and BiS/EP data via LibItemDB (AtlasLoot drop data, WoWSims BiS).

Community

Bug reports, feature requests, questions, or chatting about master-loot and gear planning: Join the Discord.