Loot Council vs DKP: A Practical Guild Guide

Loot council vs DKP: the quick answer

Loot council gives a group of reviewers discretion over who receives an item. DKP gives members an earned points balance and uses published spending rules to distribute loot. Choose council when upgrade value and group needs should outweigh saved points. Choose DKP when members should control when they spend their accumulated contribution.

Neither system makes loot fair by itself. A council needs consistent criteria and reasons people can question. DKP needs clear earning rules, eligibility, and a way for new members to compete. Both need a readable history.

We make Guild Manager, which supports council and points-based loot workflows. Our recommendation is to choose the policy your guild can explain and keep applying, even on a bad raid night.

Before choosing either, check that your game lets the group allocate or trade the items in question. Bound personal rewards leave much less for a guild loot system to decide. Our Aion 2 DKP guide explores that distinction in a specific game.

One drop, two different decisions

Imagine a shared weapon drop with two eligible members:

• Mira has 120 DKP and a modest upgrade. She has attended consistently and saved for this weapon.
• Tovan has 70 DKP and a much larger upgrade. He recently joined the regular roster and fills a role the group needs.

A council might choose Tovan if its published priority is group progression, then upgrade size. It could choose Mira if its policy puts sustained participation first. The council must explain how the criteria led to the recipient.

In an open DKP auction, suppose Mira bids 80 and Tovan stops at 70. Under a highest-valid-bid policy with equal eligibility and priority, Mira wins and spends 80. That result respects the rules and Mira's decision to save. It does not claim she received the larger upgrade.

These are different definitions of a fair outcome. Settle which one your guild wants before the weapon drops.

Loot council and DKP compared

Roster size affects the work, but it does not decide the system. A large council can work with good preparation. A small guild can prefer DKP because its members value control over their own spending.

When loot council is the better fit

Loot council works well when an item can meaningfully change what the group achieves, and reviewers have enough information to assess that change. Useful evidence might include a member's current gear, declared build, availability, or recent awards.

Make the criteria specific. "Best for the guild" is too broad to explain why one eligible member won over another. "Progression roster first, then the size of the upgrade, then recent loot" gives reviewers an order to follow and members something to assess.

Make the decision reviewable

Before your first session, agree on these rules:

1. Eligibility. Define main characters, alts, trials, and which builds can request the item.
2. Decision order. Rank the criteria. Decide what happens when two candidates remain equal.
3. Conflicts of interest. A reviewer requesting the item should sit out the decision, including when playing another character.
4. Minimum participation. Decide how many eligible reviewers are needed. An odd-sized council can still tie when someone abstains or sits out.
5. Explanation. Record the item, recipient, and the reason the policy favored them.

A useful explanation names the deciding facts: "Progression tank priority; this replaces a lower-tier weapon; the other candidate received a comparable upgrade last session." "Officers agreed" records the process without explaining the choice.

Keep the outcome visible while handling sensitive evidence carefully. Members should be able to understand an award without publishing every private note or screenshot submitted for review.

Council software can organize the discussion, but it cannot decide your guild's values. For an example of an in-game implementation, RCLootCouncil's module documentation separates candidate responses, council voting, and loot history. Check what each tool records and who can read it.

When DKP is the better fit

DKP stands for Dragon Kill Points. Members earn points for activities the guild has chosen to reward, then spend those points on eligible loot. DKP is a guild accounting unit, not the game's gold or cash.

A simple balance is points earned, minus points spent, plus or minus recorded adjustments. OpenDKP documents this model, along with support for points decay. Guilds can choose different earning rates and spending policies.

DKP suits members who want to save for specific items and see a consistent relationship between contribution and buying power. It also makes routine decisions easier to repeat: once eligibility and priority are settled, the spending rule determines the outcome.

Decide how members earn points

Publish what counts before you start paying points. Specify attendance rewards, partial attendance, standby credit, approved absences, and any other contributions you recognize.

Record corrections with a reason. If two members attended the same event under the same rules, different rewards need an explanation. An automated ledger still depends on accurate attendance and sensible policy.

If you use Discord voice attendance, be clear about what was measured. A snapshot proves someone was present at that moment. It does not establish how many minutes they participated between checks. Our voice attendance guide explains the available capture options.

Choose the spending rule separately

DKP is the points system. An auction is one way to spend those points. The bid format changes the experience:

For example, with bids of 80 and 70, a first-price sealed auction charges the winner 80. A second-price rule of "next bid plus a 1-point step, capped at the winning bid" charges 71. A different second-price configuration can produce a different charge. Name the rule rather than assuming everyone knows what "sealed" means.

Priority can also come before price. If main-spec requests beat off-spec requests, say so explicitly. The winning bid should be the highest valid bid within the relevant priority rules, not simply the largest number on the screen.

Give newcomers a defined path

Starting at zero against months of saved points can make a new recruit's first meaningful item feel unreachable. Decide how to address that before recruiting them.

Possible policies include a published starting balance, a separate trial priority, or decay that reduces older balances over time. Each has a cost. Starting points give buying power without equivalent prior attendance. Trial restrictions delay rewards. Decay can reduce the savings of members who have been waiting for a rare drop.

Consider a 10% decay on a balance of 100 points. That balance becomes 90 before any rounding or other constraints. If you use decay, publish the rate, schedule, rounding, minimum balance, and how pending bids affect it. Review the policy at a planned boundary rather than changing it because of one disappointing auction.

Mixing council, DKP, and rolls without surprises

A hybrid can be useful when different items serve different purposes. For example, your guild could publish a short list of progression items handled by council, use DKP auctions for other contested loot, and use eligible rolls for leftovers.

The important rule is to assign the method before requests or bids arrive. Switching to council after seeing a high bid undermines the points rules. Switching to a roll because an officer dislikes a council result undermines the council rules.

For a short-lived group, eligible need rolls may be enough. For a planned run, soft reserves let members declare interest beforehand. Neither requires a long-running points economy, though both still need rules for eligibility and competing requests.

Write these rules before your next raid

Use this checklist with your officers and share the answers with members:

• Which items can the guild actually distribute, and which are personal rewards?
• Who is eligible, and when do main spec, off spec, alts, or trials take priority?
• Which method applies to each item category?
• How are equal bids, equal priorities, and council ties resolved?
• What happens when nobody requests or bids on an item?
• What information will members see about an award?
• How can someone question a decision, and who reviews it?
• How is a mistaken award corrected before the item is delivered?
• When will you review the policy, and how much notice will changes receive?

Separate choosing the recipient from confirming delivery. An award records the decision. A handover records that the item reached the player. If a game imposes a trade timer or binds the item, your officers need to work within that limit. A website cannot move the item or override the game's restrictions.

Try the policy on a few hypothetical drops before using it. Include a trial member, an officer requesting an item, a main-spec versus off-spec request, and a member with points committed to another auction. If officers give different answers, clarify the rule now.

Running your loot policy in Guild Manager

Guild Manager brings council sessions, member submissions, voting, wishlists, points-based auctions, attendance, and loot history into the guild workspace. Council can collect interest and supporting evidence; auctions can use open, sealed, or second-price bidding.

You still choose the policy. The goal is to keep the requests, decisions, and history close enough that officers can explain an outcome without searching through a week of Discord messages. Guild Manager records the workflow; members and officers still deliver items in the game.

Start by agreeing on eligibility and priority. Then configure the matching loot workflow and explain it to the roster. You can explore Guild Manager, read our Discord command guide, or compare guild management tools if you are still choosing a platform.

Common questions about loot council and DKP

Is loot council fairer than DKP?

It depends on the policy you mean by fair. Council can prioritize group needs and upgrade value. DKP can prioritize earned buying power and member choice. Compare the actual criteria, exceptions, and records, not just the system's name.

Does DKP eliminate favoritism?

No. Officers still choose earning rates, eligibility, adjustments, and exceptions. Published rules and visible records make unequal treatment easier to identify, but a points balance does not remove every discretionary decision.

Can a loot council use points as evidence?

Yes. A council can consider contribution points alongside other criteria. If those points do not directly determine the recipient or price, describe them as evidence in the council policy rather than promising a highest-bid-wins DKP system.

Is sealed bidding the same as second-price bidding?

No. "Sealed" describes whether competing bids are hidden during bidding. "Second price" describes how the winner's charge is calculated. A sealed auction can still charge the winner their own bid.

What if nobody bids or requests an item?

Follow the fallback you announced. That might be an eligible roll, a documented manual award, or holding the item if the game allows it. Set any point charge and record the reason. Avoid inventing a different exception for each recipient.