Loot rules

Raid standards and time commitment

Preparation, skill, and constructive behavior earn a raid place. Once you are eligible for an item, the same published rule applies to you as to everyone else. We address performance problems directly, not through hidden loot penalties. Officers get no better loot treatment for being officers.

The scheduled commitment is four hours per week. Farming, donations, summons, optional runs, and staying late do not earn credit. We appreciate those contributions, but they do not create a second, hidden commitment.

What credit means

Each contested item gives the selected claimants equal shares of one credit. The winner spends one credit. Your balance is the credit you have gained minus what you have spent. A negative balance means you have won more than your accumulated share. You can still win with negative credit; it is not a penalty or a performance score.

If nobody else in the selected group wants an item, there is no competing claim. The item costs no credit and uses no turn. There is no one-item-per-night limit.

Every contested item costs one credit in its ledger. We do not charge more for a stronger item or choose winners by estimated raid damage.

The three ledgers

Each ledger has exact balances and its own turns. We do not create extra queues for an item, class, pair of players, or claimant combination.

The prized list is a small, published list of specific item variants. Each revision has a version number. These items have separate main-spec priority; weapons and trinkets are not automatically prized. All offspec awards use the same offspec ledger, including prized items.

Membership and outside items

This policy covers recorded guild allocations during scheduled raids. An item you get elsewhere can satisfy a need, but it cannot earn or spend guild credit. Optional runs do not change your priority.

Your records belong to your permanent member identity. Changing characters, changing an approved role, leaving, or returning does not erase them. Qualification applies to you as a member, not to a character. Credit and turns belong to one member, one loot season, and one ledger.

What makes a valid claim

You may claim an actual drop only if you are entitled to receive it, need it under an approved role and gear plan, and will accept it at the normal credit cost. Being on the roster or able to equip it is not enough.

Your role, gear plan, and allowed preferences lock before each raid week. When you get an item, remove the need it satisfies, including alternatives you no longer need. The item catalogue must account for set bonuses and other gear requirements. A higher item level alone does not make an item an upgrade.

You may pass before claims close. A pass earns no credit and prevents you from claiming that same copy through a lower-priority group, including offspec. You cannot change a main-spec claim to offspec after seeing the result. We correct factual errors; preference changes wait until plans can next be updated.

Pick the group first

Check the groups in the listed order. Use the first group with a valid claim, then stop. N counts only the people in that group. Other groups gain and spend nothing. If the selected group has one claimant, the award is uncontested even if someone in a lower group also wants it.

Main-spec awards use the ordinary or prized ledger for the item. Offspec awards use that season’s offspec ledger. If no group has a valid claim, use the published bank, disenchant, or other unallocated-item rule where the game allows it.

Six credited raids to qualify

Qualified prized priority starts at the next raid after six completed, credited scheduled raids. With two raids each week and full participation, that normally means the seventh scheduled raid after three raid weeks. Missed or noncredited sessions extend the period. There is no separate 14-day or 21-day test.

The minimum is 60 minutes in the raid or available on its assigned bench during the scheduled two-hour window. Count overlapping raid and bench time once. A completed raid can count toward qualification only once. Optional runs and time after the scheduled end do not count.

Qualification stays fixed throughout a raid. Completing your sixth credited raid gives you priority at the next raid, not during the sixth. Items won as a recruit, credit, and turns remain in your record when you qualify.

Everyone starts in the recruit groups at guild launch. Founding members have no exemption. Recruits can still receive prized items when no qualified main-spec member claims them.

The credit calculation

When at least two eligible people are in the selected group, let N be the number of people in that group:

Every claimant: balance += 1/N
Winner only:    balance -= 1

The highest exact credit wins. The earliest turn breaks an exact tie. Everyone gets the same +1/N, so that addition cannot change the order; the system may compare the balances before adding it.

Each loser gains 1/N credit. The winner gains the same share, then spends 1 credit: a net change of -(N-1)/N. The changes total zero. If three people start at zero, the winner ends at -2/3 and the other two at +1/3 each.

With one claimant (N = 1), award the item without changing credit or turn. This is not a contested win. With no claimants (N = 0), follow the rule for unclaimed items without changing anyone’s priority.

How turns are made and used

For the first season, we close the initial roster and have Quartermaster publish one random turn order for each ledger. We save each order and its seed, the value used to generate it. Officers cannot reroll to get another order. There is no new roll for each item.

A later enrollee joins the back of every ledger’s order. Every confirmed contested winner moves to the back of the ledger used, whether credit or a tie decided the award. Everyone else keeps the same relative order. Passing, absence, uncontested loot, and qualification do not use a turn.

New members do not move ahead just because they have never won. At equal credit, the earlier turn wins. In the same selected group, a new member at zero can beat an existing member with negative credit.

Software stores turns as unique ascending sequence numbers. Lower numbers win ties. Each enrollment and contested win gets the next number. A returning member uses the existing record. A later season inherits its starting order under section 6 instead of drawing again.

One ladder, different groups

For each drop, select its priority group and ledger, then compare only the people who can claim it. One ledger needs one record per member, not a separate queue for each combination of claimants.

You may lead the overall ladder and still be unable to claim an item. Losing to Alex does not reserve the next item against Alex; either of you may enter other contests that change the next comparison.

A preview must name the item, selected group, season, and record checkpoint. It cannot promise who will get the next prized drop in every situation.

Set a batch order before awarding

Several drops from one boss can affect the same balances and needs. Quartermaster records the complete observed batch, locks claims, and sets a repeatable order before finalizing an award.

Shuffle items within each category using the saved session seed and a fixed batch ID. Process prized items before ordinary items. Give each physical copy a unique, fixed ID. The result must not depend on button clicks or message arrival order.

Save the seed, batch, item order, and policy version. Do not allow repeated shuffles until someone likes the order. A saved seed is not enough to prevent manipulation: changes to the roster, IDs, and permitted corrections must also be recorded.

Process items in that order, updating temporary balances and needs after each award. An earlier award can make a later claim invalid. A real need for multiple copies must already be in the gear plan. Do not change preferences after seeing the first result.

This removes officer choice over order, but it does not find the best whole-batch result for every person. The fixed order can still change who gets which item.

A selection is not a delivery

The addon may preview a batch. A ledger changes officially only after delivery is confirmed. If an earlier award fails, later awards cannot use a state that never happened. Fix the failure and replay the undelivered remainder from the last confirmed state, in the saved order.

The game integration must confirm awards in the saved order and detect conflicting deliveries. Trade-button order cannot change who wins. Reports from multiple addons, retried actions, or repeated uploads must not count the same item twice.

For each award, save included and excluded claims and reasons, selected group, season, ledger, exact balances, turns, recipient, delivery status, and the state before and after it.

Correct facts, not preferences

A wrong ownership record or need classification is an input error. Pause the award, correct the evidence, save a new numbered claimant record, and replay. Do not charge anyone for an item they did not receive. Replay dependent undelivered awards too.

A delivered item cannot be erased by editing a score. Record what happened and reverse or recover it where allowed. Do not invent compensation currency or silently reset turns. Leave conflicts that cannot be recovered as visible incidents.

Disliking a result is not a factual error. Policy changes take effect at an announced future point, outside the current allocation. Neither an officer nor an AI may choose a different winner because they prefer that result.

Four qualified members start at zero prized credit. Their first turn order is Alex, Blair, Casey, Drew. Each row is a different needed item. Confirm each award before the next row.

Order after each contested award

Start:   Alex, Blair, Casey, Drew
After 1: Blair, Casey, Drew, Alex
After 2: Casey, Drew, Alex, Blair
After 3: Drew, Alex, Blair, Casey
After 4: Drew, Blair, Casey, Alex

Every contested winner moves to the back, including Casey, whose win used credit rather than a tie. There is no queue for a particular claimant combination.

Final balances

Drew leads the ladder but could not claim drop 4. A lead matters only if you are in that item’s selected group.

Alex beat Blair twice because both records changed between contests: Blair won another prize and Alex took part in another loss. The result uses their current category-wide records, not a promise about their next direct contest. The four balances sum to zero, and exact fractions must not be rounded into false ties.

A new raid is not an automatic reset

A loot season is the published set of records for one gearing cycle. A new raid can extend it. A major new gearing cycle can start another season. We publish the boundary and item assignments before awards, not after seeing who would gain from a reset.

The catalogue assigns every item variant a season and category. Running an old raid later does not move its loot into the current season. Publish a mapping before allocating new variants or unclear cross-content drops.

New credit, inherited order

At the announced boundary, we save a checked snapshot of the previous season. For each ledger:

1. Sort old records by credit DESC, then turn ASC.
2. Copy that full order as the new starting turns.
3. Set every new-season credit balance to zero.
4. Leave the old ledger unchanged.

Copy the full closing ladder, not only the old turn order. A positive-credit member must not go behind a negative-credit member only because the latter had an earlier old turn.

Old credit determines your starting place, but it does not become new-season credit or debt. After the snapshot, normal new-season rules apply. We do not draw a new random order.

Keep old and new records separate

An old-season item uses its old ledger even if it drops during a later raid. A new-season item uses the new ledger. The item mapping, not the calendar date, chooses the account.

An unmet old-item need keeps its old priority. Receiving that item does not reduce new-season credit. Later old-season awards do not change the new starting turns saved in the snapshot. Items acquired outside guild raids can change needs but cannot earn guild credit.

Qualification and identity continue

Qualified members stay qualified. A recruit with four credited sessions still needs two more; a tier change is not a new trial. Keep character links, membership, and award history.

Members with records at the transition keep their inherited places even if absent or inactive. They must still be eligible to claim each item. New members enrolled after the snapshot start at zero and join the back. Returning members use their existing records, not a fresh order or a cleared balance.

There are no weekly resets or decay within a season. Reopening a season, retiring an old pool, or adding an unusual ledger needs a published rule, not an officer’s improvised result.

The old prized ledger closes with these balances. Its raw turn order happens to be Casey, Alex, Blair, but credit is sorted first.

Alex carries a place in the new order, not one spendable credit. Casey keeps -1 in the old ledger but starts at zero in the new one. The raw old turn order cannot override the closing credit.

All three qualify and claim the first new-season prize. Alex wins the equal-credit tie. New balances are Alex -2/3, Blair +1/3, Casey +1/3, and the new order is Blair, Casey, Alex.

Blair then beats Casey in an equal-credit contest. Alex could still win another item if Blair and Casey cannot claim it. Inherited order is a starting comparison, not a promise that each member gets one prize before anyone wins again.

An old item after the change

Alex and Blair later claim an old-season prize. Their old balances are still +1 and 0, so Alex wins; their old balances become +1/2 each. Their new balances and turns do not change.

That separation is intentional. Alex can use old priority and a new starting place, but the new season does not transfer a continuing balance from the old one.

The end-of-season tradeoff

Taking a contested item near the end of a season can lower your place in the next season’s starting order. Passing on an optional item can preserve that place. A fixed snapshot date does not remove this incentive.

We carry only the starting order, not unlimited credit, and we do not erase all history. Publish this before end-of-season decisions. Do not claim that strategic passing is impossible.

Save the checked season record

Check that all confirmed old-season awards are included before taking the snapshot. Save the source season, exact closing records, inherited orders, effective boundary, and version. Do not use outdated Discord records or awards awaiting delivery.

If a factual error is found before any new-season award, save a corrected snapshot with a new version. After new-season awards have occurred, record a cross-season incident and all affected decisions. Do not silently change the starting order or pretend a delivered item changed owners.

1. “They got four items and I got nothing.”

Morgan gets three ordinary upgrades that nobody else in the selected group wants. Morgan and Alex then tie at zero for a contested ordinary upgrade, and Morgan has the earlier turn.

Result: Morgan wins a fourth item. The first three were uncontested, so they changed no balance or turn. Only the fourth changes contested priority; ordinary wins do not change prized credit. There is no one-item-per-night limit, and those free upgrades did not take an item Alex wanted.

2. “Alex beat me last time. I was owed the next one.”

Blair loses to Alex, wins another prize against other people, and later faces Alex again. In section 5’s fourth contest, both have -1/3 and Alex has the earlier turn.

Result: Alex wins again. Intervening contests changed both records. Blair’s loss earned credit, not a separate right against Alex; records follow the category and season, not one opponent.

3. “I’m first on the ladder. Why didn’t I get it?”

Drew has the highest prized credit, but the item does not meet Drew’s approved needs. Alex and Blair are the only valid claimants in the selected group.

Result: Drew is excluded, gets no credit, and keeps the same turn. Quartermaster compares Alex and Blair. A negative balance can win when no selected claimant outranks it. A preview must show the item, group, season, and checkpoint; it cannot promise the next prized drop in general.

4. “The first prize is still just luck.”

Several people claim the first prize of the first season. They have zero credit, and several equal-credit contests may happen that night.

Result: The published starting turn order breaks each tie. Each confirmed contested award changes credit and turns. Later seasons inherit their starting turns instead of drawing again.

The first order is random. Rare drops can leave people waiting; the system cannot guarantee another drop or show that the first winner deserved it more.

5. “They finished their trial and jumped the queue.”

An established member and a newly qualified member both have zero prized credit. The established member was waiting before the recruit enrolled and has not moved back by winning.

Result: The established member wins the tie because their turn is earlier. Qualification does not move the recruit or reset their account.

Credit still comes first. If the recruit has 0 and the established member has -0.5, the recruit wins when both are in the same group. Neither time in the guild nor having never won gives extra priority.

6. “A recruit got a prized item on their first night.”

No qualified main-spec member claims the prize, and one recruit genuinely needs it for main spec.

Result: The recruit gets it uncontested with no balance or turn change. Several recruit claims compete in the prized ledger. Early fallback awards, credit, and turn changes remain after promotion. Qualified priority is protected, but a recruit is not barred from an otherwise unclaimed prize.

A recruit may receive that item and later leave. Preventing every such loss would mean leaving some usable loot unawarded.

7. “My offspec should beat a recruit’s main spec.”

A qualified member claims a prize for offspec. No qualified main-spec member needs it, but a recruit has a valid main-spec claim.

Result: Recruit main-spec is selected. The qualified offspec claim is excluded and earns no credit. Use the recruit’s prized main-spec ledger, because main-spec gearing comes before offspec collection.

8. “My balance is higher. Why wasn’t it compared?”

A recruit has +0.5 prized credit from an earlier recruit contest. A qualified main-spec claimant has -0.5. Both want the prize.

Result: Qualified main-spec is selected first. If that claimant is alone in the group, the award is uncontested despite the recruit’s claim, and the recruit gets no credit. Choose the group before comparing credit; the recruit keeps +0.5 for later. At launch, everyone may compete in recruit groups, with no founder exemption.

9. “They passed on upgrades to save for the jackpot.”

Alex passes on a lesser prized item. Blair and Casey compete at zero; Blair wins. Alex stays at 0, Blair falls to -0.5, and Casey rises to +0.5. Later, only Alex and Blair need another prize.

Result: Alex wins on credit. Passing earned nothing but preserved Alex’s balance. Blair spent credit because Casey also wanted the first item; a sole claim would have cost nothing.

Members may pass on unwanted optional gear without a penalty. Keeping the prized list small limits the reason to save credit, but does not remove it. Raid readiness is handled separately.

10. “I’ll claim for losing credit and refuse when I win.”

A player claims unwanted items to collect +1/N losses, then withdraws when selected. Another passes main-spec and asks for the same physical drop as offspec.

Result: Neither is allowed. Claim only items you need and will accept at the normal cost. Passing also prevents an offspec claim for that same copy.

Correct invalid claims before delivery and before recording final credit changes. Correct honest errors; treat repeated deliberate false claims as a conduct issue. The software cannot tell whether a player is sincere.

11. “That isn’t an upgrade, but the addon says I need it.”

An item breaks a set bonus, duplicates a satisfied alternative, conflicts with an approved build, or has incomplete ownership data.

Result: Pause the award, check the facts, and correct the gear need. Recalculate any later undelivered awards that depend on it. Do not charge credit for an undelivered item.

Gear plans must account for alternatives and build requirements. Missing or conflicting data stops the decision. A player cannot change an otherwise valid claim after winning just to avoid its cost.

12. “Why is my loss worth less in a bigger group?”

A loser in a two-person contest gains +1/2. A loser in a ten-person contest gains +1/10.

Result: Both are correct. One credit is divided among the selected claimants, so each gets 1/N. The winners’ net changes are -1/2 and -9/10. Each contest totals zero.

Every claim must meet the same need and acceptance rules. Do not add someone who could use the item but does not want it.

13. “Processing the ring first changed who got the trinket.”

Alex and Blair need two prizes from one boss. Their credit is equal, and Alex has the earlier turn. Alex gets the first item; Blair’s higher resulting credit wins the second.

Result: Reversing the order would swap the items. The saved batch shuffle fixes the order, not an officer’s preference or trade-click order. An earlier acquisition can remove a later need, and duplicate copies follow the same rules. The order is repeatable, not an attempt to optimize everyone’s ideal batch.

14. “I was benched. Why didn’t I earn loot credit?”

A member serves the required time on the formal bench but cannot receive the boss’s drops. Another misses a week and returns with positive credit.

Result: Assigned bench time can count toward qualification. Neither player earns loot credit for a contest they could not enter.

Absence leaves credit and turns unchanged, including negative balances. Other players’ awards can still change who ranks ahead. Repeated benching is a roster issue; do not compensate by secretly changing credit.

15. “This is my sixth raid. Am I qualified for this boss?”

A recruit enters a sixth possibly credited session. Another adds optional hours, and a third attends less than the published minimum.

Result: Qualification begins at the next raid, after the sixth credited raid ends. It does not begin on day 21 or partway through a boss.

Count active and assigned-bench time once within the scheduled window. Optional hours do not substitute. A raid shorter than 60 minutes does not count, even if the guild shortened or cancelled it.

16. “Can I change characters and start at zero?”

A member with negative credit switches to an approved alt, changes role, or leaves and returns in the same season.

Result: The permanent member record keeps credit, turn, and qualification history. Approved role rules may change needs, but one person cannot claim twice through different characters. A character change does not erase awards, and a new season resets accounting for everyone only at the published transition. You cannot switch claims after seeing a drop.

17. “The officer wants it to go to a better player.”

Quartermaster selects Alex, but an officer prefers Blair for performance, donations, leadership, or a claimed raid-wide benefit and wants to reclassify the drop.

Result: The officer cannot replace Alex with a preferred winner. Eligibility, the published item catalogue, group, credit, and turn decide.

Correct documented factual errors. Address performance and conduct separately from loot. Any policy change must apply at an announced future point, not to this award.

18. “The trade failed. Did I still lose my credit?”

The addon proposes an award, delivery fails, and later batch previews depend on it.

Result: No delivery means no final credit or turn change. Fix the failure, then recalculate the remaining undelivered awards that depended on it.

Refusing a valid claim is a conduct issue, but it is not proof of delivery. If the item went to the wrong person, record and resolve that mistake. Do not invent a credit charge or hide the error.

19. “Discord disagrees, or that item was uploaded twice.”

Discord has an older checkpoint, the companion retries an upload, or several addons report one copy. Someone attempts a policy edit during the raid.

Result: Only the authorized raid writer can update the active session. Discord shows its last verified checkpoint and sync status. The server processes each confirmed event once, so duplicate reports cannot charge twice.

A cloud edit cannot change the raid’s locked rules. Show conflicts and stop affected imports. Do not manually enter drops into a second, competing ledger.

20. “Both balances say 0.33. Why wasn’t my turn used?”

Alex has exactly 1/3 credit, about 0.33333. Blair has 23/70, about 0.32857, and an earlier turn. Both display as 0.33 to two decimals.

Result: Alex has more exact credit, so the turn is not used. The details view must show exact values and the comparison that decided the award. Rounded values are not necessarily equal; addon and server arithmetic must agree.

21. “I saved three credits. Why can’t I spend them in the new raid?”

Alex built a large positive prized balance in the old season and expects to spend it on several new-season prizes.

Result: The old balance remains available for old-season loot. It sets Alex’s place when we copy the full old ladder, but all new-season credit starts at zero. No old numerical stockpile transfers. Announce this before end-of-season planning.

Use the full credit-then-turn order. Copying only old turns would ignore Alex’s positive credit.

22. “They won on the last night, and now their debt is gone.”

Casey wins a contested prize shortly before the snapshot, ends the old season with negative credit, and starts the new season at zero.

Result: Casey’s negative old balance remains and affects the closing order; it does not become negative new credit. Casey can still win new loot if the people ahead are not selected claimants. A new season carries relative priority, not indefinite debt, and does not require everyone to receive one item before another win.

Awards confirmed before the snapshot affect the inherited order. Later old-season awards do not change the new starting order.

23. “My old best-in-slot item still matters. Did you delete my place?”

Alex still needs an old prized trinket and has positive old credit. It drops in a later scheduled raid, while Alex also has a new-season place.

Result: The trinket uses the old ledger. It changes only old credit and turns; it does not spend new priority or recalculate the already copied order. Old priority remains usable for old items, so Alex can win both kinds of prize without one directly paying for the other.

The published item mapping decides the season. Running an old raid later, or calling it a catch-up run, does not move its loot into a newer ledger.

24. “Does a new tier restart my trial or give me another lottery?”

A recruit has four credited raids when the season changes. A qualified member is absent when the snapshot is taken, and a new member enrolls afterward.

Result: The recruit still needs two more credited raids, then qualifies at the following raid. The qualified member stays qualified and keeps the inherited record despite being absent. The new member starts at zero and joins the back. A returning member uses their existing record.

A season change does not start a new trial or lottery. Members must still meet the attendance and eligibility rules to claim current drops.

Qualification does not clear existing balances, recruit awards, or turns. Records present at the snapshot determine the inherited order. Later enrollment does not reorder those members.

25. “A new raid opened. Why haven’t you reset us?”

New bosses extend the current gearing period. Some members want a reset; others want to keep their balances. Someone asks to take the snapshot before a final award reaches the server.

Result: Only the announced season boundary creates new ledgers. A new raid may use the existing season. Include every confirmed award when checking the closing records; do not choose a partial history. Members cannot choose their own season or snapshot date. Publish the item mappings, source season, exact checkpoint, and resulting orders.

An error found after new-season awards have been delivered needs a recorded cross-season correction. Do not silently reroll or erase the original snapshot and award history.

26. “Why take an upgrade before the snapshot if passing preserves my place?”

Blair can accept an optional contested late-season item or pass to preserve a stronger closing balance and inherited new turn.

Result: A valid pass earns nothing but may preserve the inherited place. Taking the item changes old credit and may change that place. A free uncontested upgrade changes neither. This incentive remains whenever some history carries forward; we allow honest preferences and transfer order, not a full credit balance.

Keep the prized list small and the snapshot date predictable. Members must still prepare for raids and make honest claims. Do not add a late passing penalty, move the snapshot date, or make an officer exception to force a choice.

Records the system must keep

For each permanent member, keep identity, linked characters, eligibility, completed credited sessions, and the numbered role and gear plan. Attendance and qualification do not belong to a loot season.

For each member + season + ledger, keep exact credit and one unique turn sequence. Keep the next sequence number for each ledger. Award history explains a decision; it does not add a hidden never-winner rule.

For each season, keep item-to-season mappings, the source season, effective boundary, a fixed transition snapshot, and inherited orders. For each raid, keep the locked policy and catalogue versions, qualification at the start, authorized writer, checkpoint, and draw seeds.

For each physical item, keep batch and copy IDs, processing position, valid and excluded claims with reasons, selected group, season, ledger, proposed result, delivery proof, and before/after state. Keep reasons and dependencies for corrections.

Allocation steps

The software must use this contract:

claims = validate_locked_claims(drop, session, prior_batch_awards)
group = first_nonempty_priority_group(drop.category, claims)
ledger = account_for(drop.season, group, drop.category)

if size(group) == 0:
    propose unallocated outcome; no priority changes
elif size(group) == 1:
    propose uncontested award; no credit or turn changes
else:
    winner = first(sort(group, credit DESC, turn ASC))
    propose each selected claimant += 1 / size(group)
    propose winner -= 1
    propose winner.turn = next_turn_sequence(ledger)

commit proposed changes once, on confirmed delivery

First choose a result; then record it only after delivery is confirmed. Replay must get the same claims and winner, not trust a client-supplied winner or balance. Addon and server must use the same fixed data format, exact arithmetic, and stable IDs. Unsupported claimant counts or number limits must fail clearly instead of rounding.

Joining and changing seasons

A new member appends a zero-credit record to each relevant ledger under the permanent identity. A returning member reuses the old records. Qualification changes the selected claim tier only at a session boundary; it does not create another prized account.

For a season change, sort each complete old ledger by credit then turn, write that order as unique new turns, and set new balances to zero. Save the change as one checked operation without changing old records. Keep its source checkpoint and item mapping in the audit record.

Every change needs authorization, version checks, processing that ignores an exact repeated event, and a lasting record. An editable balance spreadsheet, silent correction, or AI-selected recipient is not part of this design.

What each part does

Quartermaster addon: The raid tool observes the roster and loot, checks claims, previews batches, calculates locally, confirms delivery, shows exact reasons, and saves a recoverable session transcript. One designated addon writer runs the session. Other clients may verify and keep checkpoints.

Quartermaster service: The server stores the verified records, policy, member identities, gear plans, qualification, and season snapshots.

Quartermaster in Discord: Members inspect the same verified record, link characters, update allowed plans before lock, and retrieve award reasons. A small web page can provide larger editing views. One session summary is better than posting every item in chat.

Raid-leader companion: Transfers prepared session packages and saved raid records between the addon and server. It does not need a continuous addon-to-web connection.

How one raid moves through the system

Before the raid, the service makes a numbered session package with ledger checkpoints, catalogue, locked plans, and qualification. The companion loads it through the verified client workflow. Both sides show the package number and authorized writer.

During the raid, the addon uses that prepared data. Cloud edits cannot independently change the active ledger. A prepared session must work without a live Discord connection. The cloud must clearly show its last verified checkpoint.

After the session is safely saved, the companion uploads its record. The server checks and replays confirmed events, rejects conflicts, ignores exact repeats, and publishes a summary. All confirmed awards must be included before the next session or season snapshot.

Member commands

Linking, publishing policy, and corrections need separate authenticated actions.

Published rules

Publish the prized list, item-to-season mappings, approved roles, gear alternatives, valid needs for multiple copies, starting roster and draw procedure, rules for unclaimed items, and season boundary. Publish a guest policy before any guest joins. There are no reserved-item exceptions, founder exemptions, attendance points, or weekly resets.

Also publish membership checks, plan-lock deadlines, how to identify a complete boss batch, and who may make corrections. Administration checks and corrects facts; it cannot select a preferred winner.

Access and records

Restrict access by guild. Allow one authorized writer per session. Companion credentials must be revocable, and server secrets must stay on the server. Check data structure, versions, signatures where implemented, and exact arithmetic limits. Keep a record of every change.

Show errors clearly with a next action. Label outdated records and pending deliveries. Do not hide a failure by letting an officer or an AI choose the winner.