Features Roster upkeep

Who left. Who’s quiet. Nobody removed by surprise.

Paste the guild members list and the activity log; the bot works out who actually left, flags what needs a human, and opens an absence episode for everyone gone quiet. Confirm with one button, undo with one button.

Add to Discord See how it works

Discord

Only you can see this

Departure sync — preview

Members list ✅ · activity log ✅
64 role-holders · 34 still in the guild

🚪 Would lose the guild role — 21

@Zanshin, @Mordekai, @Kolyada, @Nadiya … +17

⚠️ That’s a lot of people

This would remove 33% of your role-holders (over the 30% threshold). Read the list above carefully before confirming.

🔎 Needs a human — 3

• absent, no departure recorded: @Sviatoslav
• listed as present but the log says they left: @Halyna
• previously restored by an undo: @Ostap

🛡️ Protected — 6

3 with no linked in-game name · 2 officers/exempt · 1 I can’t edit

Remove 21 anyway Cancel

The preview an officer confirms against — amber because the proposal crosses 30% of role-holders. The real embed names up to 15 people per list before the +N.

50%

The roster floor

Fewer than half your role-holders in the paste and nothing is offered at all — a truncated copy can never trigger a mass removal.

30%

The amber line

Propose more than 30% of role-holders for removal and the preview turns amber, spells out the ratio, and the button reads Remove N anyway.

7 · 21 · 7

Absence defaults, in days

Absent after 7, long-absent after 21, and 7 days between check-in DMs.

1 button

To undo a sweep

Every role back, plus a sticky suppression so the same two pastes cannot immediately re-propose the restored members.

01 · Why it exists

Ex-members keep the role, and keep drawing shares

Nobody reconciles who actually left the guild in game, so ghosts keep the member role — and in this bot, the member role decides who is taxed and who receives a payout share.

Why this is a money problem, not a tidiness problem

Guild-member status feeds the loot split. A member who left the guild three weeks ago but kept the Discord role is still counted, still taxed, still owed — and the honest members' shares are smaller for it. The roster check is not housekeeping; it is what keeps the economy pointed at the people actually in the guild.

And the opposite case matters just as much: the quiet member who stopped showing up two weeks ago is noticed only once they have already gone. Absence care exists so someone asks before that happens.

02 · The loop

Two pastes, one preview, one decision

No integration, no API keys — the game's own copyable exports, and a bot that refuses to guess.

Copy two exports out of the game officer

The guild members list, and optionally the 4-week activity log. Paste them in either order, as a message or a .txt/.csv attachment for a big roster — the bot works out which is which.
Read the preview officer

Run /roster sync and read: who would lose the guild role, who needs a human and why, who was skipped and why, alongside the role-holders-versus-present count. The decision is never made on a bare removal number.
Confirm — or don’t officer

Confirming posts an audit note naming you, with an Undo button on the applied report. Above 30% of role-holders the preview turns amber and the button changes to Remove N anyway. Below the 50% roster floor there is no button at all.
The same paste opens the absence board officer

Every quiet member gets an absence episode from the members-list paste, so /roster absence immediately shows who has gone quiet, longest first — one import, both jobs.
Check in, only if you opted in officer

Check-in DMs are off by default and the 📨 button does not appear until a guild opts in. Sending needs a preview then a confirm, is stamped once per episode, skips anyone unlinked or protected, and posts a visible audit note naming who sent them.

03 · Which source says what

The members list decides presence. The log decides departures.

An automatic removal needs both signals to agree across every linked alt. Everything else becomes a flag for a human.

Guard	Threshold	What happens
Roster floor	Fewer than 50% of your guild-role holders appear in the pasted members list	Nothing at all is offered — no list, no button. A truncated copy-paste must never be able to trigger a mass removal, and the officer is told to re-copy the full list. A genuine guild disband trips this too, deliberately.
Second confirm	Above 30% of role-holders proposed for removal	The preview turns amber, an extra field spells out the ratio, and the button changes from "Remove N" to "Remove N anyway".
Always exempt	Officers, admins, the server owner, bots, the recruiter role, anyone 🛡️ protected by absence care	Computed from the holder's own roles, never from whoever is running the sweep — deriving it from the acting officer would exempt everybody at once and silently turn the sweep into a no-op.
Undo	One button on the applied report	Puts every role back. Restored members gain a sticky suppression, so the same two pastes cannot immediately re-propose them.

The members list is the presence authority — anyone listed in it can never reach a removal branch, whatever the log says. The activity log is the departure oracle, and only "left the guild" lines are ever attributed, because Albion exports every other verb with the acting officer in the Player column. Treating that column as the subject would mark your Guild Master as departed every time they kick somebody.

04 · Absence care

Quiet doesn’t mean gone

The same members-list paste opens an absence episode per quiet member — one import, both jobs.

Discord

Only you can see this

Quiet members

11 unseen for 7+ days, longest first. 🛡️ = protected from removal.

❗@Ostap 🛡️

unseen 34 days
📝 exams until August

❗@Halyna 📨

unseen 26 days

@Nadiya

unseen 9 days

Manage a member…

Check in on them

/roster absence — ephemeral, because a member's last-seen is guild-internal. The 📨 button appears only in guilds that opted into check-in DMs.

Conservative on purpose

Each member's panel carries an officer Note, a 🛡️ Protect toggle and a Protect 30 days. A protected member is never auto-removed by a sweep, however absent they look — "exams until August" on their card outranks any roster diff.

The maths will under-report rather than over-report. "Online" counts as zero days. A timestamp the bot cannot read counts as zero and never absent. A future timestamp clamps to zero. A malformed export can never invent an absence.

Check-in DMs are off by default: opting in is admin-only, sending needs an officer preview then confirm, each episode is stamped once, unlinked and protected members are skipped, and a visible audit note names who sent them.

05 · What a sweep removes

The guild role. Nothing else.

Nobody is kicked or banned by a departure sweep, and departed members keep their history.

The guild role comes off, the member is hidden from the energy console views, and that is the whole mutation. Balances, ledgers and linked in-game names are untouched — a member who left on good terms and comes back three weeks later picks up exactly where they left off, and their silver was never in danger in between.

Exemption is computed from the holder's own roles, never from whoever is running the sweep. And every confirmation posts a visible audit note naming who ran it, because a recruiter can run this and the action is outward-facing.

06 · Commands

Three subcommands, one job each

/roster sync/roster undo/roster absence

All three are open to the recruiter rank as well as officers and admins — running the roster is an action, and the recruiter tier owns every action. Only the thresholds and the DM opt-in are admin settings.

07 · Honest limits

The limits, up front

Known limits

Most of these are Albion's export format being what it is — better known before you rely on it.

Albion’s activity-log export only names the player for "left the guild". Every other verb — kicked, accepted, invited, assigned — exports its target as a placeholder and puts the acting officer in the Player column, so only departures are ever attributed. Kicks are counted as an unnamed total; joins effectively never appear, which is why rejoins are caught by the members-list presence check.
Absence care is conservative by design and will under-report. "Online" counts as zero days away, and any timestamp the bot cannot read also counts as zero and never absent, so a malformed export can never invent absences. It can, however, miss real ones.
A genuine guild disband trips the 50% roster floor and is refused, exactly like a truncated paste — deliberately routed to handling by hand.
A sweep can read an extra "never touch these roles" list, but nothing in Discord can set it yet — no settings control writes it. Your working exemptions are the built-in ones: officers, admins, the server owner, bots, the recruiter role, and anyone 🛡️ protected on the absence board.
The recruiter role auto-exempts itself from sweeps, so the tool cannot delete its own operator. The stated cost: a recruiter could shield an ally by handing them the recruiter role — tolerable only because minting recruiters is admin-gated.
The web dashboard has no Recruiting tab, so this area is Discord-only today.

08 · Questions

Questions officers actually ask

What exactly does a departure sweep remove?

The guild role, and nothing else. Nobody is kicked or banned, balances are untouched, linked in-game names are untouched, and the member is simply hidden from the energy console views. One Undo puts all of it back, and restored members gain a sticky suppression so the same two pastes cannot immediately re-propose them. Every confirmation posts a visible audit note naming who ran it.

Can it remove someone who is still in the guild?

Not automatically. The members list is the presence authority: anyone listed in it can never reach a removal branch, whatever the activity log says. An automatic removal needs both sources to agree across every linked alt — every partial, mixed or single-source signal becomes a flag for a human instead.

What happens on a guild disband?

The 50% roster floor trips and the sweep refuses, exactly like a truncated paste. That case is deliberately routed to handling the list by hand rather than automating a mass removal.

Why did a kicked member show up as "needs a human" instead of departed?

Albion’s activity-log export only names the player for "left the guild". Kicks export the target as a literal placeholder with the acting officer in the Player column, so the bot counts kicks as an unnamed total and routes the affected members to human review. Attributing that column would mark your Guild Master as departed every time they kick somebody.

Who can run this?

Recruiters, officers and admins can run and confirm sweeps, undo them, and use the absence board. The absence thresholds, DM cooldown and the check-in opt-in are admin-only — the thresholds mint the unsolicited-DM target list.

See it running before you install

The community server runs the bot in the open — a live killboard, real boards to press, and humans who answer questions.

Watch it live

Keep reading

Features that work with this one

Keep the roster honest with one paste a week

Two game exports in, one preview out, one button to confirm and one to undo.

Add to Discord Read the manual