Guild Butler documentation

Guild Butler runs your Albion Online guild's raids, loot payouts, regears, and attendance from right inside Discord — mostly with buttons, so there's almost nothing to memorize.

A raid is a scheduled group activity in Albion Online (a PvP fight, a gathering run, a big alliance battle). Guild Butler is a Discord bot that handles the whole cycle around a raid: it posts the call, collects sign-ups, tracks who showed, splits the silver (Albion's in-game currency) fairly when the raid ends, and manages regears (reimbursing members who lost gear). Officers press a few buttons; members press even fewer.

The raid loop in a nutshell

Almost everything in Guild Butler is one lap around the same loop. Here it is end to end:

1. Call — an officer posts a raid with /raid or a one-click board button.
2. Sign up — members click their role button on the post to join.
3. Run — the raid happens in-game; officers can assign roles and take roll call.
4. Settle — an officer hits 💰 Settle, enters the loot total, and Guild Butler splits it.
5. Get paid — each member's cut lands in their tracked balance; an officer pays it out in-game.
6. Regear (in parallel) — anyone who lost gear files a regear request; an officer reviews and credits it.

Find your track

These docs cover three kinds of reader, and every section heading is tagged so you can skim just your part:

• Players — you join raids, sign up, file regears, and check your balance.
• Officers — you call and settle raids, run regear drives, and pay people out.
• Admins — you set the server up: roles, taxes, language, and the raid board.

Guild Butler never touches your Albion Online account and never handles real money — it only tracks numbers inside Discord, and an officer sends the actual silver in-game. The bot ships in English and Українська.

2 · Add the bot Admins

Click Add to Discord, pick your server, and Guild Butler starts working right away with sensible defaults.

1. Click Add to Discord and choose the server you want the bot in.
2. Confirm the invite on Discord's authorization screen.
3. That's it — the bot creates its own records and runs immediately on safe defaults (no member role, taxes preset, English, UTC).

You don't have to configure anything to try it out. When you're ready to tune it for your guild — member role, taxes, timezone, language — head to §5 Server setup with /settings.

3 · Roles & permissions Everyone

Guild Butler has four permission tiers — Member, Officer, Admin, Owner — and you qualify for each in a different way. Higher tiers can do everything lower ones can.

A tier decides which buttons and commands you're allowed to use. It's based on your Discord permissions and roles, not on anything you buy. Here's who's who:

Tier	How you qualify	What you can do
Member	Anyone in the server.	Open /menu, view your own profile, balance and stats, create untaxed raids, sign up, save personal templates, file regears, and rate raids.
Officer	Holds the configured officer role, or has Discord Administrator.	Everything a member can, plus call and settle raids, /manage, /assign, run regear drives and reviews, guild templates and presets, seasons, payouts, banks, and alliance sharing.
Admin	Has Discord's native Administrator permission (a Discord permission, not a bot role).	Everything an officer can, plus server configuration: /settings, /config, /raidboard settings, and content profiles.
Owner	The person or team hosting the bot for you.	Manages the hosting side (plans and white-label). You'll rarely deal with this tier directly — your team sets it up.

Two things worth remembering. First, anyone with Discord Administrator is automatically an officer too — so admins can run raids without also holding the officer role. Second, being a guild member is a separate idea: it's about money (whether your loot is taxed and tracked), not about which commands you can run. You'll set that up in §5.

4 · The /menu hub Everyone

Type /menu once to open a private button panel that's tailored to you — from there it's almost all clicking, not typing.

Guild Butler is built around buttons, so you rarely need to remember slash commands. Running /menu opens a private panel (only you can see it) that greets you with your current silver balance and lays out actions in four groups. The panel only shows what your tier can use, so members see fewer buttons than officers or admins.

• You — your profile, balance, stats, ratings, and 📊 My status (a personal card with your balance, recent payouts, and your next signed-up raids, each with a live countdown).
• Raids — call a raid, browse and manage templates, sign-up shortcuts.
• Economy — balances, payouts, banks, and seasons (officer-facing).
• Admin — server settings and the raid board (admins only).

Prefer a plain list? Run /commands for a flat cheat-sheet of every command you have access to. But most days, /menu plus a few clicks is all you'll touch.

5 · Server setup with /settings Admins

Run /settings to tell Guild Butler who your members are, what language and timezone to use, and how loot is taxed. This is the payoff step — get it right and every raid, payout, and season just works.

Type /settings and a private hub opens (only you can see it), organized into four sections you tap into:

• Server — member role, officer role, language, timezone.
• Economy — the tax mode and the tax/caller rates.
• Raids — ping roles and the gather-time auto-ping.
• Status — the bot-status board and the feedback channel (see below).

Inside a section, most controls are drop-down pickers — pick a value and it saves on change, no submit needed. The number fields (tax rates, caller cut, caller bonus) live behind the Economy section's "Rates" modal, which has a Submit button — nothing there saves until you press it. A ⬅ Back button on every section returns you to the hub.

Every server setting

Here is the full list of what /settings controls. You don't have to touch all of it — the defaults are sensible, and the two roles at the top are the important ones.

Setting	What it controls	Default	Values
Member role	Marks who counts as a guild member (taxed and balance-tracked) versus a pug (an outside player who just gets an equal cut, no tracking). This is the most important setting on the page.	Unset	Any server role
Officer role	Grants officer powers (call and settle raids, run regear drives, manage members) to people who don't have Discord Administrator.	Unset (only Admins are officers)	Any server role
Tax mode	Who a raid taxes and balance-tracks: by role (only guild members, the default), everyone (every participant), or no one (an untaxed equal split). Set the server default here in Economy — you can also preset it per content type, and each raid can still be called in a different mode. See §12.	By role	By role · Everyone · No one
Language	The bot's language everywhere — both public messages and your private panels.	English	English · Українська
Timezone	The zone used to read raid times you type in. Times are stored in UTC and shown to each viewer in their own local time.	UTC	Any IANA zone (e.g. Europe/Kyiv)
Merchant tax %	The cut taken from each member's repaired share and sent to the Merchant bank (a guild pot for consumables and gear).	10%	0–100
Regear tax %	The cut sent to the Regear bank (the pot that funds replacing lost gear). It also absorbs any rounding remainders when loot is split.	10%	0–100
Caller cut %	A slice of the total loot (gross) taken off the top and handed to the caller (the officer who led the raid) before anything else is split.	0%	0–100
Caller bonus points	Extra attendance points awarded to the caller on each raid, on top of showing up. Points decide season payout shares.	0	Whole number
Ping roles	A curated set of one-click ping chips you can tap when posting a raid, so you don't hunt for the right role each time.	Empty	0–25 roles
Status board	A pinned board (installed from the Status section) that shows whether the bot is online and which version is running, flips to updating during a deploy, posts short "what's new" notes on updates, and carries a 💬 Feedback button.	Not installed	Any text channel
Feedback channel	Where member feedback (from the 💬 Feedback button or /feedback) is posted for your officers to see.	Unset	Any text channel

Recommended setup order

Do it in this order the first time. The two roles come first because everything else depends on them.

1. Set the Member role — pick the role your actual guild members hold. This is what separates members from pugs.
2. Set the Officer role so your officers can call and settle raids without needing Discord Administrator.
3. Pick your Language if you're not running in English.
4. Set your Timezone so typed raid times land at the hour you mean.
5. In Economy, open Rates and set your Merchant tax % and Regear tax %, then press Submit.
6. Still in Economy, pick your Tax mode if the default (by role) isn't right — choose everyone if your whole roster is guild, or no one for untaxed splits.
7. Optionally add a Caller cut %, Caller bonus points, and a few Ping roles — you can always come back to these later.

Status board & feedback

The Status section is optional but handy. Install a pinned bot-status board into a channel (pick one, or let the bot create #bot-status) and it shows at a glance whether Guild Butler is online and which version is running. During a deploy it flips to 🟠 updating, then back to 🟢 online — and on a new version it drops a short "what's new" note into that channel.

The board also carries a 💬 Feedback button, and anyone can run /feedback. Both open a short form; the report — plus a small snapshot scoped to the sender (their balance, recent activity, the bot version) — is posted to the Feedback channel you set here, so officers see bug reports and ideas in one place.

6 · Regear rules Officers

A regear is the guild replacing gear a member lost in a fight. Set these rules once with /regear settings before you run a regear drive, so claims land in the right channel with the proof you expect.

A drive is one regear session for one raid — members file their losses, officers review them. These settings shape how every drive behaves. Run /regear settings to open the panel.

Setting	What it controls	Default
Event category	The Discord category where the bot auto-creates a fresh channel for each regear drive, keeping claims tidy and separate from your main chat.	Unset
Review channel	Where regear claims are posted for officers to approve or deny. If you leave it unset, claims fall back to the drive's own channel.	Falls back to the drive channel
Min screenshots	The minimum number of proof images a member must attach per item before they can submit a claim.	1
Max amount	A ceiling on how much silver a single claim can request. Above it, the claim can't be submitted as-is.	No cap
Auto-approve under	Claims below this silver amount are approved automatically — but only the member's first approved claim in that drive. Everything after it still needs a human. Set to 0 to turn auto-approve off entirely.	0 (off)
Default conditions text	A standard note shown to members when they file a claim — your guild's regear rules, in your own words.	Unset

7 · Raid board & content profiles Admins

The raid board is a persistent message with one-click buttons for starting a raid. Each button is a content profile — a saved "type of raid" (PvP, PvE, and so on). Set it up with /raidboard settings, then drop it in a channel with /raidboard post.

A content profile is a one-click "type of raid" button — press it and the raid builder opens pre-filled for that content, so you're not filling out the same fields every time. Guild Butler auto-seeds three profiles to start: PvP, PvE, and Guild. Edit them or add your own.

Per-profile fields

Field	What it controls
Label	The text shown on the button (e.g. "PvP", "ZvZ").
Emoji	The icon on the button, next to the label.
Builder	Simple opens a quick modal (title, time as text, roles); Full opens the complete raid builder.
Mode	Untaxed (equal split, nothing tracked) or Taxed (tracked loot and payouts). Taxed-mode buttons are officer-only.
Tax mode	For Taxed profiles, presets who's taxed — by role, everyone, or no one — so this content type always starts in the right mode (falls back to the server default). See §12.
Ping role	The role automatically pinged when a raid is posted from this profile.
Template	The saved role composition (the "comp") this profile starts from.
Post channel	Where raids from this profile are posted, if different from the server default.
Gather VC	The voice channel players gather in — setting it enables Roll Call for the raid.
Enabled	Whether the button shows on the board at all.
Order	The button's position on the board relative to the others.

There's also one server-wide raid post channel — the default place raids land when a profile doesn't set its own post channel.

Setting it up

1. Run /raidboard settings to configure your profiles and the server-wide raid post channel.
2. Adjust the auto-seeded PvP / PvE / Guild profiles, or add new ones, and set each one's label, mode, template, and channel.
3. Run /raidboard post in the channel where you want the board to live.

8 · Templates & comps Officers Players

A template (also called a comp) is a saved, named list of roles you drop into a raid instead of typing the whole line-up every time.

Think of a comp as your raid's shopping list of roles — "2 Tanks, 4 Healers, 6 DPS, 1 Caller", and so on. Save it once, reuse it forever. When you call a raid you just pick a comp and the sign-up buttons appear automatically. A template only ever defines the role line-up — nothing about payouts, timing or scoring lives on it.

Public vs Personal

Every comp has a scope — who can see and manage it. There are two:

• Public — created by an officer and shared with the whole server. These are your guild's official line-ups (a ZvZ comp, a small-scale comp, a gank comp). Only officers can create, edit or delete them.
• Personal — anyone can make one, and it stays private to you. Nobody else sees it. Great for saving a favourite five-man before you call an untaxed raid.

When you run /template create you can pass a scope option (Public or Personal (only you)). Leave it off and the bot picks for you: officers get a Public comp, everyone else gets a Personal one. A non-officer who explicitly asks for Public is turned down.

Comps are also tagged PvP (player-versus-player content) or PvE (player-versus-environment, like dungeons). The tag is purely a label for grouping — it sorts comps on the board and in the managers, and nothing more. You choose it when you create the comp, and you can flip it later with a single button (see below).

The template board

/template board (officers) posts a persistent board in the channel — a message that sticks around so anyone can use it later. It lists your public comps grouped by tag (a ⚔️ PvP line and/or a 🐉 PvE line), with four buttons underneath:

• ⚔️ New PvP and 🐉 New PvE — open the create form. Whether the new comp lands as Public or Personal is decided the same way as the command: officer → Public, everyone else → Personal.
• 📋 Manage public — opens the public template manager (officers only).
• 👤 My templates — opens your own personal manager.

The two manager buttons open a private panel only you can see, so several people can use the same board at once without stepping on each other. Each comp on the board also shows a short structure summary — its party and slot counts (for example 3 parties · 50 slots), so you can size up a line-up at a glance.

The role-spec syntax

When you build a comp you describe each role on its own line, or separated by commas. Each entry follows this shape:

Only the Name is required. The parts, in order:

• Category > — an optional group the role belongs to, written as Category > Name with a > between them (for example Tanks > Main Tank or Healers > Holy). The > is deliberate — it keeps the / free to use inside a role name, so a weapon-choice name like Heavy mace / Hammer works fine. Categories become the pick-a-group menu on big comps.
• Name — what the role is called (up to 40 characters).
• :slots — how many people can take that role, from 1 to 50. Leave it off and you get 1 slot.
• :emoji — an optional emoji shown on the sign-up button. Note it lives inside the role line — there's no separate emoji field on the comp.

A few worked lines:

Multiple parties

A comp doesn't have to be one flat list of roles — you can split it into several sub-parties (Party 1, Party 2, and so on). Each sub-party is just a labelled group of role slots — think of one as a self-contained five-man or a wing of a bigger force. This is how you organise ZvZ and other large comps into readable groups (a Frontline party, a Flank party, a Ranged party) instead of one giant wall of roles.

To open a sub-party, put a line that starts with # and give it a name. Every role line below that header belongs to that party, until the next # header starts a new one. The # was picked because it's the fastest thing to type. Here's a two-party comp:

Parties and categories work together — the party (the # header) is the outer group, and categories (the > before a name) group roles within a party. On the raid post, a multi-party comp shows each sub-party as its own side-by-side column, with a shared bench below that spans the whole raid.

Signing up works the same way, only party-aware. On a small multi-party comp every role is still its own button, with the sub-party name tacked on so there's no confusion (for example ⚔️ Spear · DPS). On a big one (more than 20 roles) the menu asks you to pick a sub-party first, then a role inside it. Officers get the same party-first step when they use /assign.

Columns — the multi-party look, without sub-parties

Sub-parties give you side-by-side columns on the card, but they also change sign-up (on a big comp the picker asks for the party first). If you just want the column layout on a plain single-party comp — and keep sign-up as one-click role buttons — add a columns: N line anywhere in the Roles box:

columns: 1 (or leaving the line out) is the classic single-column card. You can ask for 1 to 4 columns — Discord shows up to three across on desktop and wraps a fourth to a second row. A comp that already uses # sub-parties ignores columns: (its sub-parties are already the columns), and a saved template remembers its column count.

How the roster fills the columns. Guild Butler chooses one of two ways automatically:

• By category — when you tag roles with Category > and have at least as many categories as columns, each category is kept whole and dropped into whichever column is currently shortest. The handy result: one category per column, in order, when the number of categories equals your columns. That's your lever for choosing exactly what goes where — in the example above, Column 1 is the whole Melee category and Column 2 is the whole Ranged category. (With more categories than columns, the smaller ones get packed together to balance.)
• By position — with no categories (or fewer than columns), the flat list is split top-to-bottom into even, contiguous chunks. So columns: 2 over five roles puts rows 1–3 in the first column and rows 4–5 in the second; columns: 3 over six roles gives rows 1–2, 3–4, 5–6.

The create form

Creating or editing a comp opens a short form with just two boxes:

• Template name — a short label for the comp.
• Roles — one role per line, using the role-spec syntax above. This is also where you type your # party headers — the whole line-up, parties and all, lives in this one box.

You don't set the tag (PvP/PvE) or the scope (Public/Personal) inside this form — Discord forms can't hold those menus. Both are chosen before the form opens, from the command option or the board/manager button you clicked. The tag can still be changed afterward from the manager. Editing a multi-party comp round-trips cleanly: the form re-fills with your # headers intact, and renaming or reordering a party keeps everyone who already signed up in place.

Managing your comps

There are two manager panels, and they work the same way:

• /template manage (officers) — the public library.
• /template mine (anyone) — your personal library.

Each panel lists your comps (PvP first, then PvE) with one button per comp, plus New PvP / New PvE buttons at the bottom. Click a comp to open its actions:

• ✏️ Edit — reopen the create form (name + roles) to change the line-up. Renaming a comp happens here too — there's no separate rename button.
• Tag toggle — a button showing the current tag (⚔️ PvP / 🐉 PvE); click it to flip the comp between PvP and PvE in place.
• ⧉ Duplicate — make a copy, keeping the same scope and tag.
• 🗑️ Delete — remove the comp.
• ← Back — return to the list.

The permission rules follow the scope: a personal comp can only be touched by its owner, and a public comp can only be touched by officers — for every one of those buttons.

The commands

Presets — save the whole raid

A comp saves just the role list. A preset goes further and saves a whole raid set-up — comp, mode, start time, tier and food/potion requirements, ratings and the rest — so you can spin up a familiar raid in one shot. Presets are always shared and officer-managed. Manage them with:

9 · Calling a raid Officers Players

There are two ways to post a raid: the full builder (/raid) for total control, and the simple builder (a button on the raid board) for a quick one.

A raid is a scheduled event that people sign up to. Publishing one drops a post in your raid channel with a role button for everyone to claim their spot.

The full builder — /raid

Run /raid and work through the draft panel. You can also attach an image up front with /raid [image].

1. Run /raid to open the draft.
2. Set the Name — this is required; nothing publishes without it.
3. Pick a saved template (comp) or type the roles yourself using the role-spec syntax from §8.
4. Choose the mode (Untaxed or Taxed) and set the time — date, gather time, start time and duration.
5. Add any requirements (gear tier, food, potions) and media (a build link with a label, an image).
6. Set the ping (who gets notified), pick a gather voice channel, and toggle ratings.
7. Hit the green Publish button.

A few things worth knowing about the full builder:

• Non-officers can only post Untaxed raids. Taxed raids (the ones that track loot and pay out) are officer-only.
• Publishing is all-or-nothing. If the post fails to send for any reason, the whole thing rolls back cleanly — you will not end up with a half-created raid.
• Picking a gather voice channel is what enables Roll Call later (see §11).
• Ratings default to Off.

The simple builder — from the raid board

If your server has a raid board (a set of one-click buttons for common raid types), clicking a button opens a short form instead of the full panel. Fill in:

• Title — the raid's name.
• Time — entered as free text (whatever wording your members understand).
• Description — a short line about the plan.
• Roles — the comp, using the same role-spec syntax.

Then press Publish. It is the fastest way to get an untaxed raid on the board. Board buttons set to Taxed mode open the full builder instead and are officer-only.

10 · Signing up Players

Claim your spot on a raid by clicking a role button on the post — and drop out just as easily.

Small comps — click your role

• Click the role button for the spot you want.
• A role that is already full shows as disabled — you cannot click it.
• Clicking your own role again leaves that role and frees the slot.

Big comps — over 20 roles

When a raid has more than 20 roles, buttons for every one would be unwieldy, so you use a menu instead:

1. Click 🎯 Join.
2. Pick a category (the role group from the comp).
3. Pick your role within that category.

To drop out of a big-comp raid, click 🚪 Leave.

The bench

Click 🪑 Bench to stand by without taking a specific role. This is meant for flex players — people the caller can slot into whatever role opens up on the night.

Let callers find you — /profile

Your profile records which roles you can actually play — Tank, Healer, Support, Melee, Ranged, Battlemount and Caller. Set these with /profile. When you sit on the bench, callers use your listed roles to slot you into an open spot — so keep it up to date.

11 · Assign, manage & roll call Officers

Once a raid is live, officers get tools to place people, fix their status, and check who actually showed up.

Assign someone — /assign

/assign drops a member straight into a specific role (and party) on the raid. Use it to place bench flex players or to sort out a line-up by hand rather than waiting for people to click buttons. On a multi-party raid, /assign asks you to pick the sub-party first, then the role — and its autocomplete labels each slot with its party so duplicate roles are easy to tell apart.

Manage a member — /manage

/manage (also reachable via the 🛠️ Manage button on the post) opens per-member controls. For any one person you can:

• Toggle guild member vs pug — overrides how they are taxed and tracked for this raid.
• Mark them merchant-tax exempt or regear-tax exempt — so their share skips that cut.
• Move them to the bench or back to active.
• Kick them off the raid entirely.

Roll call

If you set a gather voice channel when you built the raid, roll call compares who signed up against who is actually sitting in that voice channel — a fast way to spot no-shows before you head out.

12 · Settling the loot Officers

When a raid ends, settling turns the pile of loot into silver that lands in each member's balance and the guild banks. One officer runs it once per raid.

First, two words. Gross is the total silver value of everything the raid earned — you type this in as one number. Repair is the silver the guild fronts to fix broken gear after the fight. Settling shares the gross out, then skims a couple of small taxes into the guild banks.

Run a settlement

1. Click the 💰 Settle button on the raid post (or run /settle).
2. Enter the gross silver and pick an outcome (win / loss / draw) for the raid.
3. Enter the repair amount — this is charged to the member pool only, never to pugs.
4. Review the preview: it shows every member's net, the pug total, and both bank cuts.
5. Click Confirm to lock it in — or Recompute first if the roster changed and you want the numbers refreshed.

Members vs. pugs, in plain terms

A guild member is a participant the raid taxes and tracks; a pug (short for "pick-up group" — an outsider who filled a spot) is paid a flat cut with nothing tracked. Repair costs and the two guild taxes come out of the member pool only; pugs are paid off the top and walk away clean. Who counts as a member depends on the raid's tax mode (below): in by role it's holders of your member role; in everyone it's every participant (no pugs); in untaxed nobody is taxed and everyone gets an equal split.

The five buckets

Every settlement splits the gross into exactly five buckets. Here they are with a worked example — 700,000 gross, 7 people in the party (4 guild members + 3 pugs), 50,000 repair, and a 20% total tax (10% merchant + 10% regear):

Bucket	Who / what	This example
Member nets	Each guild member's take-home, after repair and tax	70,000 each (4 members = 280,000)
Pugs	Flat cut paid to the 3 outsiders	300,000
Repair	Set aside to fix gear (member pool only)	50,000
Merchant bank	Merchant tax on the members' repaired share	35,000
Regear bank	Regear tax (also soaks up rounding remainders)	35,000

Those five always add back up to the gross — nothing appears or disappears. That's the reconciliation identity:

In numbers: 700,000 == 300,000 + 50,000 + 280,000 + 35,000 + 35,000. If the preview ever fails to balance, the settlement won't confirm.

Tax modes

How a raid is taxed depends on the tax mode it was called in. The raid builder labels the choice Taxed (everyone/role) or Untaxed; you set the server default in /settings → Economy (or preset it per content type), and each raid can override it:

• Untaxed — a simple equal split of the gross across everyone. Nothing is taxed and nothing is tracked (no balances, no stats, no banks). This is the old "casual" split.
• Taxed · by role — the default. Only guild members (holders of your member role) are taxed and tracked; pugs get a flat cut. This is the full five-bucket split above.
• Taxed · everyone — every participant is treated as a member: all taxed and balance-tracked, no pugs. Handy when your whole roster is guild.

Separately, a raid can settle into a Pool: its net silver flows into an active season instead of paying out straight away, to be split later by attendance points (see §16). Pool is about when silver pays out; tax mode is about who is taxed — they're independent.

Made a mistake on a normal guild settlement? Run /unsettle to reverse it and start over. Note it can only undo a regular settlement — it cannot claw back a season or pool payout once that has been distributed.

13 · Balances & getting paid Everyone

Every settled raid updates a running silver total per member — their balance. Members check theirs; officers pay it out from a board.

Members: check your balance

Run /balance to see your running silver total plus your recent ledger history — the line-by-line record of what was added (raid nets, adjustments) and paid out. Your balance goes up when raids settle and regears are approved, and down when an officer pays you.

Officers: the payout board

Run /balances to open the payout board — every member with a positive balance. To pay someone:

1. Open /balances and pick a member from the board.
2. Choose Pay full, or Other amount to pay a partial sum (must be ≤ their current balance).
3. The bot writes a payout entry to their ledger and drops their balance by that amount.

Manual adjustments & the banks

Use /adjust to add or deduct silver from a member's balance by hand — handy for corrections or one-off bonuses. It has a count as regear flag if the adjustment should be tracked as a regear reimbursement rather than a plain tweak.

Run /bank to view the two guild banks the taxes feed: the Merchant bank and the Regear bank. These are pooled guild funds, separate from any individual's balance.

14 · Regear: request & review Everyone

A regear reimburses a member for gear they lost on a raid. The member files a claim with proof; an officer reviews it, and approving credits the member's balance.

A regear is filed against a drive — an event an officer opens to collect claims for a specific raid or day. Everything happens in a private thread so screenshots and amounts stay tidy.

Member: file a regear

1. An officer opens a drive with /regear board.
2. On the board, click 📸 Request regear — the bot opens a private thread just for you.
3. Click ➕ Add death for a lost-gear death, or ➕ Add OC to add an "off-content" line (gear lost outside the main fight).
4. Enter the silver amount for that item — what the gear was worth.
5. Drop your screenshot(s) into the thread as proof.
6. Click ✅ Submit once every item has an amount and at least the minimum number of screenshots.

Officer: review a claim

Each submitted claim lands as a review embed with four actions plus a revoke:

• ✅ Approve — accept the claim. You can edit amounts down before approving, or set a line to 0 to drop it entirely.
• ❌ Deny — reject the claim outright.
• ✍️ Request info — reopen the thread and ask the member for more detail or better screenshots.
• ↩️ Revoke — undo a regear you already approved.

If you turned on auto-approve in your regear settings, small first-time claims can clear instantly without a manual review, so members don't wait on tiny amounts.

When all the claims for a drive are handled, close it with /regear close.

15 · Attendance, ratings & stats Everyone

Taxed raids quietly build your track record: attendance points log themselves, ratings are opt-in, and /stats shows what you've earned and how you've shown up.

Attendance points

Attendance points are a simple count of how many raids you've turned up for. You never award them by hand — they log automatically every time a taxed raid is settled. A "taxed raid" is one run in a Taxed mode (the 🏛️ modes), as opposed to an untaxed raid, which is a quick, untracked run.

Every settled taxed raid is worth one attendance point; untaxed raids are worth none. Points come from the raid's mode — tracked (taxed) content versus untaxed — not from any per-template setting. (A caller can earn a few bonus points per raid if an admin set that up.) Untaxed raids track nothing at all — no points, no earnings history — so don't expect them to show up here.

Ratings (opt-in)

After a raid, the crew and the caller (the officer who ran the raid) can rate each other — a lightweight way to flag good teammates and good leadership. Ratings are only collected when the officer turned the ratings toggle on for that raid (it's Off by default), so most runs won't ask.

Whether your ratings appear on the public board is entirely your call. Your ratings are private by default. Use these two commands to control that:

Your stats

Three commands read the numbers, depending on who you are and whose record you want to see:

/stats caller is worth a closer look if you run raids. It summarises how a caller's raids have gone: total and average gross (the silver a raid brought in), what share went to repair (the cost of fixing gear), and the mix of outcomes (win/loss results logged at settle time). It's a fair, at-a-glance measure of a caller's efficiency over time.

16 · Seasons Officers Optional

A season is an alternative payout model: instead of splitting each raid on the spot, loot pools all season long and pays out by attendance at the very end.

How a season works

Normally, each taxed raid is settled and paid out individually. A season changes that: while a season is running, pool-mode raids don't pay out one by one — their net silver flows into a single shared pot. At the end of the season you split that pot across everyone by their attendance points, so the people who showed up the most take home the most.

1. An officer runs /season start to open the season.
2. Pool-mode raids get settled as usual, but their net silver feeds the one seasonal pot instead of paying out immediately. Each attendee also earns attendance points.
3. Anyone can run /season status to see the current pot size and their own projected share.
4. An officer runs /season end to split the pot by attendance points and close the season.

The net that feeds the pot is what's left of a raid's silver after the usual deductions (taxes, repair, any caller cut). You still settle pool-mode raids the normal way — the difference is only where the money goes afterward.

17 · Alliance attendance sharing Officers Optional

Two allied guilds can share raid attendance across the line — never silver, never rosters — so members who fight alongside an ally still get credit at home.

What gets shared (and what never does)

Alliance attendance sharing lets one guild pass along attendance points for players who joined a raid on behalf of an allied guild. Both sides have to consent, and the link is deliberately narrow: only attendance crosses the line. No silver ever moves between guilds, and neither side sees the other's roster or economy.

There are two roles in the handshake: the source guild (the one sharing attendance from its raids) and the subscriber guild (the one following, whose members receive the credit).

Setting up the link

1. On the source guild, an officer runs /alliance and picks the role that marks the ally's players.
2. The bot returns a one-time code that expires in 24 hours.
3. Send that code to an officer on the subscriber guild.
4. The subscriber officer runs /alliance, chooses Follow, and pastes the code.

Once the link is active, whenever the source guild settles a raid, any attendees who hold the bound role (the role picked in step 1) are credited to the subscriber guild — attendance only. Either side can revoke the link later; revoking stops future crediting and doesn't claw back what was already shared.

18 · White-label & plans Admins Optional

Guild Butler is free to use in full. The one paid upgrade today is white-label — letting the bot wear your guild's own name and face.

Plans

There are two tiers, and we'll be straight with you about the difference:

Plan	What you get
Free	The whole bot — every raid, settle, regear, season and stats feature in these docs.
Pro	Everything in Free, plus white-label branding.

Honestly: white-label is the only paid difference today. Every raid and economy feature works on Free. Check your tier any time with /plan show.

What white-label does

White-label lets the bot take on your guild's identity instead of the default Guild Butler branding. There are two flavours:

• A nickname on the shared bot — the same Guild Butler bot everyone uses, but wearing a per-server nickname of your choosing.
• A fully dedicated bot — its own bot with your own name and avatar, run just for your guild.

Turning it on

Once your server is on the right plan, officers manage branding with one command:

The nickname route works right away from Discord. A fully dedicated bot — with its own name and avatar — is set up together with the Guild Butler team, since it needs a separate bot provisioned for you. Reach out to the team to get that rolling.

19 · Web dashboard Everyone

A read-only web view of your guild's economy and your own stats — sign in with Discord, no new password.

The web dashboard is a companion site to the bot. Everything it shows lives in Discord already — the dashboard just gives you a bigger, sortable window into it. It never changes anything: it is read-only and private to your guild.

1. Go to app.guild-butler.com in your browser.
2. Click Log in with Discord — you authorize with your existing Discord account, so there's no new password to create.
3. Pick your server from the list. Only servers you share with the bot show up.
4. Read your view: officers see the economy overview, trends over time, and the members board; members see the overview plus their own stats.

What each role sees maps to what they can already see in Discord — an officer's balance and payout picture, a member's own balance (silver owed to them) and attendance. Nobody sees another guild's data, and members don't see other members' private numbers.

20 · Command reference Everyone

Every slash command, grouped by who uses it. Most members never need this — buttons behind /menu cover the day-to-day.

Type / in any channel to see commands your permissions allow. Below, each card lists the command, what it does, and who can run it. Member = anyone in the server, Officer = holds the officer role or has Discord Administrator, Admin = has Discord Administrator.

You

Raids

Economy

Admin

21 · FAQ & troubleshooting Everyone

Quick answers to common questions, then fixes for the settings that trip people up.

Common questions

Troubleshooting

22 · Glossary Everyone

Plain-language definitions for every Guild Butler and Albion Online term used in these docs, alphabetized.

Term	Meaning
Alliance sharing	A one-way link between two guilds. The source guild shares its settled raids so tagged attendees also earn attendance in the subscriber guild. Only attendance is shared — never silver.
Attendance points	Points a member earns for showing up to tracked raids. They drive stats and, in a season, how the pool is split.
Balance	The silver the guild currently owes a member (or that a member owes the guild). Grows when raids settle in their favor, shrinks when they're paid out.
Base share	An equal slice of the settled loot each qualifying participant starts from, before taxes and cuts are applied.
Bench	A signed-up player kept in reserve rather than active for a raid. Benched players stand by and can be swapped in.
Caller 👑	The person leading a raid. May receive a caller cut and/or bonus attendance points.
Caller cut	A percentage of the gross loot taken off the top for the caller before the rest is split. Default 0%.
Casual / untaxed raid 🎲	A relaxed raid mode any member can create — labelled Untaxed in the bot. It splits loot equally and tracks nothing — no taxes, no attendance, no season pool.
Category (role)	A grouping of roles inside a comp (for example, tanks or healers). In big comps you pick a category first, then a specific role.
Content profile / raid board	A one-click content button on the raid board (auto-seeded PvP, PvE, Guild). Each profile carries its own label, emoji, mode, template, ping role, and channel.
Drive / event	A regear session. Officers open a drive; members file regear requests against it, often in its own channel or category.
Ephemeral	A Discord message only you can see. Many bot replies (like private confirmations) are ephemeral so they don't clutter the channel.
Gross	The total loot value of a raid before any taxes, repair costs, or cuts are taken out.
Guild member 🛡️	A player in the configured Member role. Guild members are taxed and tracked; their shares feed the member pool.
Ledger	The running record of every credit and debit to a member's balance — settlements, payouts, and manual adjustments.
Member pool	The portion of a settlement's silver that is split among the qualifying guild members after repair and off-the-top cuts.
Merchant bank	A guild fund built from the merchant tax — a cut of each member's repaired share. Used for guild expenses.
Net	What a member actually receives from a settlement — their base share after repair and taxes are applied.
Outcome	A win/loss (or similar) result recorded when you settle a raid. It can't be backfilled later, so set it at settlement.
Pug / outsider ⚔️	A player who isn't in the guild's Member role. Pugs are neither taxed nor tracked, and everyone counts as a pug until a Member role is set.
Ping roles	Curated Discord roles offered as one-click ping chips when posting a raid, so the right people get notified. 0–25 configurable.
Plan	The feature tier a server is on (for example, Free or Enterprise). Today it only gates white-label features.
Preset	A saved raid configuration you can reuse to call similar raids quickly without re-entering every field.
Ratings	Optional per-raid feedback that rolls up into a rating for members. Each member chooses whether theirs is public.
Regear	A reimbursement for gear lost in content. A member files a request with the amount and screenshots; an officer reviews it. Items can be a death (a full loadout lost) or an OC (an off-cooldown / partial loss), and each needs a minimum number of shots (screenshots).
Regear bank	A guild fund built from the regear tax; it also absorbs rounding remainders. Note: approving a regear credits the member's balance — it does not draw the regear bank down.
Repair	The cost of repairing gear for a raid, entered at settlement and taken out of the member pool before shares are split.
Roll call	An attendance check-in tied to a raid's gather voice channel, used to confirm who actually showed up.
Role-spec syntax	The shorthand for defining a comp role: [Category > ]Name[:slots[:emoji]] — an optional category, a name, an optional slot count, and an optional emoji. A line starting with # opens a new sub-party.
Season / pool	A period during which pool-mode raids collect their net silver into a shared pool and tag attendance points. At season end the pool is split by points — this is irreversible.
Settlement mode	When a raid pays out: immediate (split now) or pool (net feeds the season pool, split later). Independent of tax mode — see Tax mode.
Silver	Albion Online's in-game currency. Guild Butler tracks silver balances in Discord only; it never moves silver in the game.
Sub-party	A labelled group of role slots inside a comp — Party 1, Party 2, and so on — used to organise large comps into readable groups. You open one with a # header line in the roles box. Splitting a comp into sub-parties does not affect loot settlement.
Tax mode	Who a raid taxes and tracks: by role (only guild members, the default), everyone (every participant), or no one (untaxed equal split). Set per server and per content type, snapshotted onto each raid. The builder shows it as Taxed / Untaxed.
Taxes	Percentages taken from members' repaired shares into guild banks: the merchant tax feeds the Merchant bank, the regear tax feeds the Regear bank. Each defaults to 10%.
Template / comp	A saved lineup of roles (a composition) for a raid. Templates can be Public (guild-wide) or Personal (yours), and are typically tagged PvP or PvE.
White-label	Presenting the bot under your guild's own name and avatar. A lite nickname works on the shared bot; a dedicated setup runs a bot with its own global identity (the team sets this up for you).
ZvZ / CTA	Large-scale Albion content. ZvZ (zerg-vs-zerg) is a big open-world battle; CTA (call to arms) is a mandatory turnout event.