1 · 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 five languages: English, Українська, Deutsch, Français and Português (BR).

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:

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.

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.

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

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.

Roster density — full or compact

The other layout lever is how much room each role takes:

• Full (the default) — the role is a heading with its players listed underneath, one per line, and a blank line between roles. Easiest to read on a small comp.
• Compact — the role is a bold label with its players inline right after it, single-spaced: ⚔️ DPS (2/3) — Alice, Bob. Fits a big comp on one screen.

Templates remember it, and it combines freely with columns:.

You don't have to type either of them — 🧩 Roles

columns: and density: are also one-click toggles, so the text form is only there if you like authoring the whole comp as text (or want it saved in a template):

• While building or editing a raid — the builder's 🧩 Roles button opens a small panel: ✏️ Edit roles · 📋 Roster: compact/full · 🔢 Columns: N · ✅ Save & back. The toggles show the layout that's actually in effect (including one inherited from the template you picked), so one click always flips what you see.
• On a raid that's already posted — the console's 🧩 Roles panel has the same two toggles, so you can restyle a live card without re-editing the raid. It re-renders in place and nobody's sign-up is touched.

🔢 Columns is greyed out on a multi-party comp — its sub-parties are already the columns, so the setting would do nothing.

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, ping roles and the rest — so a recurring call goes up in a couple of taps instead of a fresh build every time. Think "do it exactly like last Tuesday's CTA."

The presets board

Presets live on their own pinned, self-updating board — no command to memorize. An officer installs it once (/preset board, or /menu → 📚 Presets board and pick a channel); after that it edits itself in place whenever a preset changes.

Discord

🛡️

Guild Butler✓ APPToday at 20:14

📚 Raid Library — Presets

A preset is a whole saved call — comp · time · mode · requirements · ping. Launch one in two taps. A template is the roster layout only.

• Hideout Defend — 🏛️ · 🕒 20:00 · 🛡️ T8 · ⭐ · 👥×2
• CTA — Zone Blob — 🏛️ · 🛡️ T8 · 🍖 🧪 · 👥×3
• Ava Roads — 🎲 · 🛡️ T6 · 👤×7
• Faction Warfare — 🏛️ · 🕒 21:30 · 👤×15
• …and 22 more

📋 Pick a preset…▾

➕ New preset🔎 Browse all 26

Launch in two taps

Pick a preset from the dropdown and a private panel opens (only you see it). Tap ▶️ Use and the raid builder opens pre-filled — the saved calendar date is dropped and re-derived from how far ahead the preset was scheduled (a "tomorrow" preset always lands as tomorrow), so you usually only set the time and post. Anyone can Use a preset; a non-officer is safely clamped to a casual, untaxed call.

Discord

Only you can see this

Managing Hideout Defend

🏛️ · 🕒 20:00 · 🛡️ T8 · ⭐ · 👥×2 · 40

▶️ Use ✏️ Edit ✏️ Rename ⧉ Duplicate 🗑️ Delete

Edit a preset in place

Officers get ✏️ Edit, which reopens the raid builder on the preset itself — change the comp, time, requirements or anything else through the normal builder controls, and the terminal button saves the changes back to the preset instead of posting a raid. ➕ New preset on the board builds one from scratch the same way, so you never have to post a throwaway raid just to save a set-up.

Discord

Only you can see this

✏️ Editing preset: Hideout Defend

Mode

🏛️ Taxed (role)

Roles

👥×2 · Tank×2 · Healer×4 · DPS… — 40

Time

20:00

Requirements

🛡️ T8 · food · potions

🧩 Roles🕒 Time🛡 Requirements🔔 Ping

💾 Save preset changes

Manage, browse & stay tidy

The panel also carries Rename, Duplicate and Delete (officers). Preset names are unique per server — try to save a second "CTA" and the bot offers to edit the existing one instead. When a guild builds up more than 25 presets, a 🔎 Browse all button opens a private, paginated picker so none are ever out of reach.

Discord

Only you can see this

All 26 presets — pick one:▾

◀1 / 3▶

Safe by default

The raid builder keeps one working draft at a time, so if you're mid-build and open a preset, the bot asks before discarding your draft rather than losing it silently. And a preset's comp is snapshotted when you save it — editing or deleting the template it came from can never quietly change what the preset spins up.

Discord

Only you can see this

⚠️ You have an unsaved raid draft. Opening this will discard it.

Discard & openKeep my draft

Prefer commands? They still work: /preset list to browse, /preset manage for the dropdown manager, /preset delete <name> to remove one, and /preset board to (re)install the board.

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.

Every published card also carries a payout line telling members how they get paid for this raid — one of three, in every raid state, so nobody has to know your server's default to read it:

It is always shown, not just on the unusual raids: Season pool in particular is picked automatically whenever a season is open rather than chosen by anyone, so without the line a member would have to know the server's settings to read the silence. It stays on the card after the raid settles too.

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 full role turns grey but stays clickable — that's deliberate, so whoever is in it can always leave (important for one-slot roles). If you tap a full role you're not in, the bot just tells you it's full.
• Clicking your own role again leaves that role and frees the slot.
• Every card also has an explicit 🚪 Leave button, so leaving never depends on remembering which role you clicked.

Big comps — over 20 roles

When a raid has more than 20 roles, buttons for every one would be unwieldy, so there is a single green ✍️ Sign / change role button that opens a menu instead. Green marks it as the way to join a big raid; on small comps the role buttons stay blue.

1. Click ✍️ Sign / change role.
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 · Running a live raid Officers Raid leaders

Once a raid is live you get tools to place people, grow the roster, fix statuses and check who actually showed up — without ever bumping someone who already signed up.

Open the console — 🛠️ Managing

Click 🛠️ Managing on the raid post. The bot opens a thread on the post and drops the console into it, so the raid and its controls sit together, with a live fill summary (Vanguard 3/20 · Flank 5/20 · 🪑 2). The thread doubles as the raid's discussion thread, so members can ask questions in it.

Raid leaders don't need the officer role

Whoever posts a raid is its caller — its leader. A caller can run their own raid without being an officer. The split is roster and lifecycle vs money.

The line is drawn at guild money, not all money. A casual raid is an untaxed even split — no balances, no banks, no attendance — so its own leader closing it is bookkeeping rather than economics. A taxed raid always needs an officer. This is also why a non-officer editing a raid can't change whether it's taxed: otherwise they could flip a guild raid to casual and settle it themselves.

A caller clicking 🛠️ Managing gets this reduced panel instead of the full console; anyone who is neither officer nor caller is turned away. When a caller who isn't an officer uses one of these powers, the bot posts a one-line note into the raid's thread — nobody is pinged, but officers can see what happened without having to watch.

Grow the roster mid-raid — 🧩 Roles

More people turned up than the comp has slots? Open 🧩 Roles in the console:

• ➕ Add role — create a role (name, slots, emoji, category) on the live card, then optionally seat people into it straight away. On a multi-party raid you pick which sub-party it joins.
• ➕ Add slots — add open slots (1 / 2 / 3 / 5 / 10). It is roster-aware: it tops off parties that still have room, then spills into a new party once one is full — an Albion party is 20, so a single-party raid that overflows becomes Party 1 + Party 2 automatically. You see exactly where the slots will land before you confirm.
• 📋 Roster and 🔢 Columns — restyle the card live (see Templates & comps).

Hand over the lead

Manage → pick a member → 👑 Make leader hands the raid to someone else mid-fight. It asks you to confirm, because the caller's cut and bonus follow the crown when the raid settles. Blocked once a raid is settled — that silver is already paid out.

End without splitting loot

The raid ran, there was simply nothing to split. 🛑 End · no split closes it with no money involved at all: sign-ups stop, nothing is taxed, no balances move, and the card turns amber with the footer 🔒 Closed — no loot split. Nobody is notified. It stays settleable in case loot turns up late, and it is reversible with ♻️ Reopen — which pings nobody either. It is not the same as settling for zero, and it is not how you cancel a raid.

Call a raid off

The raid never ran — six people signed for a twenty-man, the enemy has a ball up, the call is off. 📣 Call it off is the button for that, and unlike End · no split it is loud: everyone on the roster is told to stand down, in the raid channel, straight away.

1. Click 📣 Call it off — it sits beside 🛑 End · no split, and both are red because both are terminal.
2. A short form opens with one optional field — "Why? (optional — everyone signed up will see this)", up to 140 characters. There is no second confirm; the form is the confirm.
3. Submit. The raid closes and the stand-down notice goes out.

The card carries the call-off directly under the title, above everything else, because it is the only thing a reader still needs from that post — 📣 Called off — this raid did not run. plus your reason, quoted with your name on it so caller-written text can never be mistaken for the bot's own words. The footer reads 📣 Called off — this raid did not run.

The notice goes to the raid channel, not the officer thread — the people who need it are the ones about to log in:

Sign-ups are mentioned confirmed first, then the bench. Discord caps how much one message can carry, so on a big roster the tail is counted as "…and N more" rather than quietly dropped — those players are not pinged, so the raid channel is the source of truth, not the notification.

Back on after all? ♻️ Reopen — and the retraction is as loud as the call-off was. The original notice is struck through in place (with mentions off, so an edit can never re-ping) and a fresh recall is posted, because nobody re-reads an edited message.

Activity log

📜 Activity log is the raid's timeline — who signed up, who left, who was moved or kicked, and who did it, with any reason they gave. Players get a neutral version of the same log from the post's Log button. An optional live feed posts changes into the thread as they happen.

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):

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, and the published raid card repeats it as a payout line so members can see how they'll be paid before they sign up (see Calling a raid); 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 · Siphoned energy Everyone

Optional. If your guild tracks Siphoned Energy — the shared resource members draw from your hideout — Guild Butler mirrors the game's energy log and keeps everyone accountable for what they took, so it replaces a separate energy-tracking bot.

The idea: any player can copy their guild's up-to-4-week energy log from the game, and an officer pastes it in. The bot reconciles it into a per-player energy balance (deposits minus withdrawals), shows it on a live board, and DMs anyone who goes negative. Silver and energy are tracked separately — energy never touches your silver balances.

Turn it on & install the console Officers

1. Run /siphoned hub — the officer hub, with a short "getting started" checklist.
2. Click 📥 Install console and pick a channel. The bot posts a pinned energy console there (and turns tracking on).

Keep it updated — paste the log

The game only remembers ~4 weeks, so paste the log regularly (daily is ideal). Anyone can ask for an update; only officers (or a role you nominate) actually paste it.

1. On the console, click 🔄 Request update. If you can paste, a thread opens with instructions; if you can't, it pings the log-fillers to do it.
2. Paste the log from the game's Guild Management → Siphoned Energy screen (Discord attaches long pastes as a file automatically — that's fine).
3. The bot shows a preview — how many rows are new vs. already recorded, and a warning if there's a gap since your last import. Click Import.
4. Mark any large withdrawals that were guild expenses (power cores, HQ, etc.) in the picker so they don't count against the player who pulled them, then Done.

Re-pasting the same log is safe — the bot only records rows it hasn't seen, so overlapping pastes never double-count.

Members: see your balance Players

The log speaks in in-game names, so link yours once to get personal features: run /ign set <your in-game name>. From then on:

• Your energy balance shows on the console (as your mention), in /menu next to your silver, and via /siphoned balance or the console's ⚡ My balance button.
• If your balance goes negative, the bot DMs you a nudge to deposit (at most once a week while you're in the red).
• /siphoned transfer <member> <amount> hands some of your energy to another member; /siphoned top lists the biggest debtors.

Moving over from another bot Officers

Coming from a different energy bot? Bring your existing balances across so nobody starts from zero. Order matters, because your old balance and the 4-week log overlap on the last month:

1. Import the log first (Request update → paste → Import, as above). This lands the last 4 weeks.
2. Then /siphoned hub → 📥 Migrate balances and paste your old bot's balance list.
3. In the picker (sorted biggest-first), skip any "debt holder" account — the dummy character some bots park all guild debt on — so its phantom balance isn't given to a real player. Then Apply.

The migration back-computes each opening balance so every member lands exactly on their old-bot figure, with the real 4-week history underneath. It's re-runnable — if you migrate before importing the log by mistake, just run the migration again afterwards and it self-corrects.

15 · 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 — a session an officer opens to collect claims for one raid or day. Everything happens in a private thread, so screenshots and amounts stay tidy.

Member: file a regear

The bot walks you through one loss at a time, and only ever shows the buttons that apply right now — so you can't accidentally leave a line without its proof.

1. On the drive's board, click 📸 Request regear — the bot opens a private thread just for you.
2. Click ➕ Add death for gear lost dying in the fight, or ➕ Add OC for an off-content loss (whatever your guild counts as one — ask an officer).
3. Enter the silver amount. You can type it however you like: 2343434, 2,343,434, 500k, 2.3m or 1kk.
4. Drop the screenshot into the thread. This is the only step now offered — Add and Submit disappear until that line has its proof, so nothing gets stranded.
5. The buttons come back. Add your next loss and repeat, or press ✅ Submit when you're done.

Officer: review a claim

Each submitted claim lands as a review card, with the screenshots attached and named line-1-shot-1, line-2-shot-1 and so on, so you can tell which image belongs to which amount:

• ✅ Approve — accept it. You can edit amounts down first, or set a line to 0 to drop it.
• ❌ Deny — reject the claim, with a reason.
• ✂️ Split — the member lumped several deaths onto one line. Split it into 2–10 parts that sum to exactly the original: the payout is unchanged, but the stats now count real deaths.
• ✍️ Request changes — pick what is wrong (wrong amount / needs a clearer screenshot / wrong type / duplicate / something else) and which line. The member sees a ⚠️ on that line, and their next screenshot is aimed straight at it.
• ↩️ Revoke — undo a regear you already approved.

A claim comes back to you automatically once every change you asked for is done — otherwise the member resubmits by hand. If auto-approve is on, a small claim can clear instantly, but only a member's first approved claim per drive, so no one can split one big loss into many small automatic ones.

Officers or a dedicated regear officer role can review claims and run drives; changing the regear settings stays with officers. When a drive is done, close it from the board or the regear hub.

16 · 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.

17 · 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.

18 · 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.

19 · Recruitment & applications Officers Optional

Turn "how do I join?" into a button. Guild Butler posts an application board — one or more Apply buttons — collects answers in a private thread, and files each application into a staff-only forum for your officers to approve, deny, or ask about.

Recruitment is optional and off until you set it up. Once it's on, applicants press a button instead of pinging an officer, and everything an officer needs to decide — the answers, an interview room, the accept / decline buttons — lives in one place.

The application board

The board is a message with one or more Apply buttons. Each button is an application type, and every type is configured on its own:

• Its own questions — what this kind of applicant is asked (a short modal form).
• Its own in-game name field — a dedicated, labelled box for the applicant's Albion character name (required, optional, or off, per type).
• The roles it grants on approval — a list, so an alliance application can grant a general ally role and that ally's specific role at once. A type that grants no role is an inquiry — it's simply answered and archived.
• Its own colour — blue, green, or grey, to tell the buttons apart.
• Its own review forum (optional) — route this type's applications to a different forum, or leave it on the guild default.

So "Join the guild", "Apply for an alliance role", and "Ask a question" can sit side by side on one board, each asking different things and ending somewhere different. A board holds up to five types (Discord's one-row button limit). A guild that never configures a type still gets a single default Apply button, so recruitment works out of the box.

What an applicant sees

1. They press an Apply button and fill in that type's short form, including their in-game name.
2. Guild Butler opens a private thread for them and your staff — the place to talk it through.
3. Their answers are filed as one post in a staff-only applications forum, so officers review in private — applicants never see anyone else's answers.
4. Staff decide: ✅ Approve, ❌ Deny (with a reason), or ✍️ Ask for more info (which reopens the thread for a reply).

Approving grants that type's roles, links the applicant's in-game name to their Discord account, and sets their nickname. The application post is retitled and retagged as it moves — 🆕 New → 👀 Waiting on applicant → ✅ Accepted / ⛔ Declined — then archived, still searchable, so the forum becomes a tidy record of everyone who ever applied.

Asking for an in-game stats screenshot

A type can also require an in-game stats screenshot. An image can't be a form field — Discord modals are text-only — so the bot asks for it in the applicant's thread and captures the next image they post. Officers can also ask on demand with a Request screenshot button on the review card.

The captured shot is re-hosted and embedded on the review post, so it survives even after Discord's own upload links expire. To steer what gets sent, the board editor carries an optional guide link and an example image, both surfaced in the prompt — the example rendered right where the applicant uploads.

Interview rooms

Need to actually talk? A review card has an 🎙 Invite to voice button that opens a temporary voice channel just for that application — the applicant and any officer or recruiter can hop in. Rooms tidy themselves up: once one has sat empty for ten minutes it's deleted automatically, so a busy recruiting week doesn't leave a pile of dead channels behind. A room someone is still sitting in is never touched, however old.

In-game names, and why approval sometimes waits

The in-game name is its own labelled field, never guessed from a question — so "Why do you want to join?" can't accidentally be stored as someone's character name. When a name is linked, that member's history (like their siphoned-energy balance) follows it.

Setting it up

1. Open /settings → Recruitment. Set your staff role (the officer role and/or a nominated recruiter role) and the applications forum.
2. For the forum, either Create a fresh 📋-applications forum, or adopt an existing forum from the picker. Adopting one makes it staff-only automatically — a public forum can never leak applicants' answers.
3. Press Manage board to open the editor: set the board's title, text, and colour, then Add type for each Apply button — its label, emoji, colour, questions, name field, granted roles, and (optionally) its own forum.
4. Post the board to a public channel. It re-renders itself in place whenever you change it, so you never have to repost.

The rest of the membership toolkit

Recruitment is one of four optional tools that cover a member's whole life in the guild:

• Nickname prefixes — map a role to a nickname prefix (say the officer role → [O] ) and the bot keeps server nicknames in sync as roles change.
• Departure sync — compare the in-game roster against Discord and remove people who left, so they stop accruing. Always confirmed by a human and undoable (/roster sync, /roster undo).
• Absence care — a board of members who've gone quiet, longest first (/roster absence), with an optional, preview-and-confirm check-in DM.
• The recruiter role — nominate a recruiter role that can run this whole lifecycle (approve applicants, confirm departures, send check-ins) without any economy powers — no settling, taxes, or payouts. Open its console with /recruiter. Every setting stays admin-only.

20 · Killboard Officers Players Optional

The killboard is a live feed of your guild's Albion kills and deaths, posted into your Discord as rendered cards — both players' gear with real item art, damage and healing per participant, and the silver value of what the victim carried. Cards arrive about 6–8 minutes after the fight: Albion publishes its own feed roughly 5–6 minutes behind the game, and nothing can beat that.

Setting it up — three taps

Open the console from any of three doors: the ⚔️ Killboard button on the officer board, /menu → Officer tools, or /killboard console. Then:

1. Pick your Albion server — Europe, Americas or Asia.
2. Type your guild's in-game name. If more than one guild matches, the bot lists every candidate with its alliance tag and you pick — it never guesses, because Albion re-issues freed names.
3. Press ⚡ Create channels for me. The bot makes a Killboard category with #kills and #deaths and sets its own permissions. Prefer existing channels? Choose existing channels opens the pickers instead.

There is no separate switch-on step — the feed arms itself the first time a channel is configured. The done screen tells you about the upstream lag, so nobody stares at an empty channel wondering if it worked.

Card grounds Officers Pro

Cards draw on a ground: parchment — Albion’s own look — is the default and free forever; Obsidian is the dark ground and needs the Pro plan. Pick it on the killboard console; every card the guild posts wears it, and if the plan lapses cards quietly fall back to parchment.

Routing — a channel for every kind of event

Kills, deaths and assists each route to their own channel (or share one). A highlight channel takes the big ones: give it a fame floor, a silver floor, or both — the rule is famous or expensive, and a qualifying kill posts to the highlight channel and stays in the main feed, so the record stays complete. Assists arrive as one compact per-battle digest by default (full cards or off are one tap away), and digests never ping.

To change a route later: Channels → ✏️ Edit a channel… lists your routes by channel name, each opening an editor with move, limits and 🗑️ Stop posting here together. The console also checks the four permissions a card needs — View Channel, Send Messages, Embed Links, Attach Files — and names anything missing per route.

Pings

When a card posts, linked members among the killer, victim and participants are mentioned — matched by Albion character id, never by name, and capped at 10 per card. The guild has a master toggle on the console, and any member can switch off their own mentions with /killboard myping.

Lookups

From a death card to a regear claim

If your death falls inside one of your guild's raid windows — posted start minus 15 minutes through six hours after — and you were on that raid's roster (confirmed or bench), your death card carries a 🛡️ Request regear button. It pre-fills a claim with the five ruled slots — weapon, off-hand, head, chest, boots — priced per line, and files it as pending in the staff review queue with the card as evidence. Officers approve, adjust or deny exactly as with any other claim; nothing is ever paid automatically, and a double-press cannot file twice.

21 · Giveaways Officers Players Optional

Prize draws as a styled card with a 🎉 Enter toggle. Open the hub with /giveaway (or /menu → Officer tools → 🎁), fill the five-field modal — prize, duration, winners, silver per winner, description — then the confirm panel sets eligibility (everyone, guild members, or holders of any listed role) and 🎨 Style. The draw fires at the deadline inside one transaction, so it can never pick winners it fails to pay: silver prizes land straight on winners' guild balances, and an item prize says on the card that the host delivers it.

Raid raffles

The 🎁 Raffle button on a raid's officer console binds a draw to that raid. There is no Enter button — the roster is the entry list (confirmed players plus the bench), snapshotted at the moment of the draw so late signups count and leavers drop out. The host cannot win their own roster, and a called-off raid hides the button.

Members can host too

Members start draws from the member board's 🎁 button, funded from their own balance: the full stake — winners × silver — is locked the moment the card posts, so nobody can promise the same silver twice. Unspent stake is refunded at the draw, cancelling refunds in full, and a host may cancel their own draw but never reroll an announced winner.

Weighted odds

The ⚖️ Odds panel turns an even draw into an attendance-weighted one: tickets are 1 + floor(points) over the last 28 days, capped at 10. The odds are printed on the card and each entrant is told their own ticket count on entering — an opaque weighting is what makes a draw feel rigged. A minimum-attendance gate can narrow who may enter, and a draw can require a linked in-game name so the prize is deliverable.

22 · White-label & plans Admins Optional

Every raid, settle, regear, season and stats feature in these docs works on Free, with no member cap and no trial clock. Two paid tiers add tools on top: Pro for guilds that recruit, and Banner for a bot wearing your guild's own name and face.

Plans

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

Honestly: nothing a member needs is paid. Seeing your own balance, signing up for a raid, filing a regear — all Free, all in Discord. The paid tiers are officer tooling and branding. 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.

23 · Web dashboard Everyone Pro

A read-only web view of your guild's economy and your own stats — sign in with Discord, no new password. It comes with Pro: a server on Free still appears in the picker, with its panels locked behind an upgrade rather than hidden.

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.

24 · 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

Recruiting

The application board itself is built from /settings → Recruitment → Manage board, not a slash command.

25 · FAQ & troubleshooting Everyone

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

Common questions

Troubleshooting

26 · Glossary Everyone

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