Community & Points

Two engines, one Community area

Guild points is a per-guild currency: members build a balance by earning it or getting a grant from a mod, then spend it in the shop. Community Programs is a separate rules-and-ledger engine for member-driven activity like recruiting, hosting, and pledges, and it runs whether or not you turn points on.

The two connect where it makes sense. A community program can pay its reward straight into a member's points balance, and a recruiting program's tenure tiers hand a new recruit their own welcome points once they've stuck around. You can run either on its own.

Guild points

Points are scoped to one guild: every balance, transaction, and setting lives on that server alone. There's no cross-server economy, so a member's balance here has nothing to do with their balance anywhere else.

Members earn points through earn rules or a direct mod grant, then check their balance and recent history with /points. Mods grant or claw back points with /points-give and /points-take, both capped by a max-per-grant setting so a mistyped amount can't wreck the economy. Every change lands in an append-only transaction log.

Points settings covers the basics: the currency's name and emoji, how many members show on /points-leaderboard and whether it posts publicly or stays ephemeral, an optional channel where GearCheck keeps a live leaderboard digest, a starting balance for new members, an optional balance ceiling, a daily earn cap, a weekly loyalty credit, and whether the shop takes redemptions at all.

Points shop

The shop, /points-shop to browse it and /points-redeem to spend, is where members redeem their balance for rewards you set up. Redeeming debits the balance immediately and creates a requested redemption; denying it later refunds the points automatically, and a failed automatic grant refunds too, so a member is never charged for a reward that didn't happen.

Turn the whole shop off with one setting, or require a minimum balance before anyone can redeem at all.

• Manual: the default type. A mod fulfills it by hand, in-game gold, an item, loot priority, whatever you set the fulfillment note to, then marks it fulfilled.
• Discord role: GearCheck grants a role automatically once redeemed.
• Temporary role: grants a role for a set number of days, then auto-revokes it. Redeeming again stacks more time onto the same expiry.
• Gift: sends points to another member, never yourself or a bot. The sender pays the item's cost; the recipient gets a separately configured amount, so you can price a gap and make gifting its own points sink.
• Raffle ticket: buys one ticket in a raffle you've set up on the Raffles page.
• Choice: one shop entry that lets a member pick between several sub-options, each with its own type, cost, and stock.

Good to know

Role rewards are off by default. With it off, role and temporary-role items keep their other settings but grant nothing, points are meant to buy gold, items, and loot priority, not gear-earned roles, unless you decide otherwise. Turn on Allow role rewards in Points settings to let those items actually grant.

A role, temp-role, or raffle-ticket item can grant instantly on redeem or wait for a mod to approve it first from the Redemptions page. You can also cap total stock, how many times one member can redeem an item, and a cooldown in days between redemptions; 0 means unlimited on any of them.

For raffles, create one with a name, prize, and close time from the Raffles page, then point a raffle_ticket shop item at it. The ticket cost locks in at whatever that shop item charges the first time someone buys one, so editing the item's cost later doesn't change tickets already sold. A raffle draws automatically once it closes, or you can draw it early; the winner is picked weighted by ticket count and gets an announcement and a DM. Cancel a raffle instead and every ticket holder gets refunded.

Earn rules

Earn rules are automatic point faucets tied to guild events, like passing a gearcheck or checking into an event. Every preset ships disabled: a mod turns one on and sets the amount before it pays anyone.

The anti-farm logic is built into the engine, not something you configure: each rule dedupes on a fixed scope, once per build ever, once per member per day, or once per event ever, so re-running a check or re-marking attendance never pays twice.

• Passed a gearcheck: pays once per build, ever, the first time a member's check verifies clean. Set an optional minimum score.
• First-attempt clean pass: a bigger bounty for verifying clean on the very first try at a build, no redo needed.
• Daily gearcheck participation: a small credit for any verified check, capped at once per member per UTC day.
• Attended an event: pays a member once they're marked present at a scheduling event. The amount comes from that event's own check-in reward, not a fixed amount here.

The Daily earn cap in Points settings (0 = uncapped) sets a server-wide ceiling on what any one member can earn from faucets in a day, across every rule combined. Turn on member feedback in Points settings to DM a member whenever a rule pays them.

Community Programs

Community Programs is a generic rules-and-ledger engine for member-driven activity. Recruiting Rewards is the flagship, but the same engine runs Gear-Up Challenges, Event Attendance Rewards, Public Run / Host Credits, Guild Bank Pledges, and a Community Contribution Board.

Each program moves entries through a ledger: pending, eligible, approved, paid, denied, or disqualified. A program's reward pays out as a Manual in-game payout, a Discord role grant (automatic or mod-assigned), or Guild points. Turn on “require approval” so a mod signs off before a qualifying entry can be paid, or leave it off so an entry becomes payable the moment it qualifies.

• Recruiting Rewards: members self-log with /recruit; the reward becomes eligible once the recruit has stayed a set number of days.
• Gear-Up Challenge: rewards a verified readiness score on a target build by a deadline, captured automatically from gear checks.
• Event Attendance Rewards: rewards attending events or filling needed roles, captured automatically from scheduling attendance.
• Public Run / Host Credits: track who hosts public runs and how many prospects join, logged by a mod.
• Guild Bank Pledges: track who pledged gold or materials, whether it's paid, and which fund it supports.
• Community Contribution Board: credit members for guides, builds, help, hosting, and other support, logged by a mod.

Milestones, tenure tiers, and payouts

Layer a bonus on top of the base per-entry reward: escalating one-time tiers (the 5th recruit earns X, the 10th earns Y) or a repeating bonus every Nth qualifying entry. Pick one style per program; only that style's fields apply.

A recruiting program can also pay the recruit, not just the recruiter: a one-time welcome bonus in points once the recruit has stayed a set number of days (up to five tiers per program). This needs points turned on for the guild, or the welcome bonus never gets credited.

The Payouts page lists everyone currently owed a payout across every program, oldest first, with an overdue flag once a payout has waited past your threshold. Mark a payout paid, or mark a role granted, right from the queue; an optional digest can DM your managers, post to a channel, or land in the dashboard inbox.

Members self-serve with /recruit to log a recruit, /myrewards to check their own progress, and /leaderboard to see program standings. Mods get approve and deny buttons on entries that need a decision.

Quiet Members

The quiet members report tracks the last time each member showed up across gear checks, event attendance, community programs, and points activity. The watchlist ranks the quietest members first once they've crossed a threshold you set in Community settings; nobody under the threshold is listed, it's a watchlist, not a surveillance roster.

A weekly loyalty credit is the positive mirror: set the Weekly loyalty credit amount in Points settings and anyone active that week gets credited once, on a schedule rather than an earn rule, so it doesn't count against the daily earn cap. Export the watchlist as CSV from the Quiet Members tab, and keep whatever channel gets the going-quiet notes restricted to officers, since it names members by activity.