Loot / item distribution Premium

Optional per-guild module. Owners/admins enable and configure it under Guild settings → Loot distribution (custom name, form fields, optional Discord forum). The sidebar shows the feature under your chosen name (default “Loot Distribution”).

Members

• Submit multiple applications per member.
• Edit your own entries while status is not locked (Declined / Accepted are locked).
• Applications are not deleted — staff set Declined instead.

Form fields (staff: Loot permission)

Configure ordered questions in settings: text, link, number (comma decimal), long text, dropdown (options list), slider, image (paste/upload), and class (guild class picker). Required flags per field. The same field types are used for class stats, currency requests, and guild applications.

Review roster

• Table columns: staff see a mail icon for unread comments, then member, status, Item (first form field), last updated. New requests and any request staff have not marked Comments read show as unread.
• Status workflow: New → Active → Declined or Accepted (colour-coded rows).
• Filters by status and member; detail panel for full answers, status change, and staff comments (timestamped, like event comments). The member name in the detail title and member column is a link that opens the full member detail popup (guide).
• With filters on “all”, Declined and Accepted rows are grouped under headers collapsed by default (click ▶ to expand).
• On narrow screens the list and detail panel stack vertically; each area scrolls independently.

Loot vault (optional)

• Enable under Guild settings → Loot distribution → Loot vault. Staff with Vault permission add items (screenshot + name); members browse the vault and apply for a stored item.
• Each vault item has a quantity (default 1, up to 99) — multiple winners can be accepted for the same item (manually or via loot roll).
• Staff with Vault permission can Merge into… a duplicate listing: all applications move to the target item, quantity is chosen at merge (sum, keep target/source, or custom), and the source listing is archived. If the same member has open applications on both items, both are kept (separate roll entries) and staff are warned so they can decline extras before rolling.
• When the vault is on, the Item column and forum thread title use the vault item name; additional form fields come after the item picker.
• When the vault is off, the first configured form field is the item name.
• Optional default availability window, past-item retention, and Discord logging for new vault items.
• When adding a vault item, paste a screenshot with Ctrl+V anywhere on the vault page (no need to open the file picker first).
• If the guild’s game has an item database configured in the admin game template, vault add can show a rarity picker (colored names), an optional Open item database link, and search against the game’s local item catalog (GW2 API import or custom HTML crawl) to fill name, rarity, and icon.

Wishlist (optional)

Separate need-list catalog under the loot module (not vault-backed). Full guide: Wishlist.

• Enable under Guild settings → Loot distribution → Wishlist. Members mark items they need; staff with Loot can Award item (creates an accepted application tagged Wishlist).

Loot rolls (optional)

For vault items only, after the application period has closed. Enable under Guild settings → Loot distribution (Enable loot rolls; optional pity system nested below).

• When it appears — Staff with Loot permission see Roll for winner(s) when an item has two or more open applications (status New or Active) and at least one slot remains. Rolls are hidden while the application period is still open or when only one applicant is left.
• Who is in the pool — Only open applications (New / Active). Applications already Declined or Accepted before the roll are excluded. Staff can decline unwanted entries manually, then roll among the rest.
• Outcome — Randomly accepts up to the item’s remaining quantity; other pool members are set to Declined (with DKP refunds where applicable). A loading overlay shows progress while the roll runs.
• Roll result — Detail panel lists the roll pool (entries per applicant), winners, and not selected. Results are stored on the vault item and shown after reload.
• Loot roll label — Applications resolved by a roll show a Loot roll badge (and a short note in the detail panel) so they are distinguishable from manual accept/decline. Member Details → Item requests shows the same badge.
• Pity system (optional) — Each roll loss adds +1 extra roll entry for that member on future rolls (base entry = 1). Pity resets only when the member wins a loot roll, not on manual accept/decline. Member roster Details shows current pity when enabled.
• Disable rolls — Turn off Enable loot rolls in guild settings to hide roll UI entirely (manual review only).

Buy offers (optional)

• Enable buy requests in loot settings. Members can mark an application as a buy offer and enter the amount they would pay.
• Buy offers appear in the review roster and optional forum threads with a buy banner.

DKP (optional)

Dragon-kill-point style loot currency. Enable under Guild settings → Loot distribution → DKP system. Requires the loot distribution module.

• Guild default — Guild settings → Events sets default DKP per attended event (default 1).
• Per event — On the calendar Create Event form or the event page Edit event modal, DKP awarded when attended overrides the guild default. Leave empty to inherit; set 0 to award none for that occurrence. The event page shows the effective DKP under the description.
• Earning — When voice attendance marks someone attended, attended (no RSVP), or attended (declined) (/track-attendance or auto attendance), they receive the resolved DKP amount once per occurrence. The attendance DM includes +X DKP and the new balance when DKP is enabled.
• Vault prices — Staff set a DKP price when adding or editing vault items (0 = not purchasable with DKP).
• Spending — Members with enough balance can submit a buy with DKP application for a priced vault item. DKP is debited when the request is submitted; staff accept or decline like any other application. Declined (or auto-decline) refunds the spent DKP.
• Balances — Members shows a DKP column and sort when enabled. Staff see applicant DKP balance on item requests.
• Manual grants — Staff with the DKP permission (or owner/admin) can award DKP from the member Details popup on the roster.

Request visibility

• Item requests visible to staff only (loot settings, default off) — when on, members see only their own applications on the loot page; staff with Loot permission see all.

Discord forum (optional)

• Each application can get a forum thread when forum sync is enabled.
• Status changes on the web post history embeds; map statuses to forum tags in settings.
• Declined and Accepted archive the thread after update.
• Buy offers and DKP purchases show banners in forum embeds when applicable.
• Staff can use /set_itemappstate inside the thread — see Discord: loot applications.

Loot permission: review all applications, change status, comment, and manage form fields. Vault permission: manage vault items. Enabling the module and forum channel remains owner/admin. See Guild member permissions. Attendance and DKP awards: Discord: event attendance.