Calls in Discord
Announcement, roster, reminders for gather and departure, archives for finished and disbanded runs.
Welcome to GuildMaster
Guild content and roster tracking for Albion Online, right inside Discord. The bot posts calls, attendance counts itself, the guild master sees who actually shows up.
albion online
a living world
a living world
by players
for players
for players
scroll down
How it usually goes
A small guild runs on memory. Then the familiar part starts.
before
| mon | tue | wed | thu | fri | |
|---|---|---|---|---|---|
| Thorvald | + | + | + | ? | |
| mirelle (?) | + | ||||
| Kaedan | + | + | + | ||
| changed name | ? | ? | |||
| Brannoc | + | + | |||
| Sylva | ? |
last edited three weeks ago
- Only the raid leader remembers who showed up, and only until morning.
- One person keeps the spreadsheet, and it breaks when they leave.
- Discord names change and old reports stop adding up.
- Roster cleanups turn into arguments instead of numbers.
after
TThorvald12
MMirelle11
KKaedan10
BBrannoc9
SSylva9
OOrik8
Counted by the bot. The week closes itself.
1 minto post a call
0spreadsheets by hand
100%of runs recorded
5 minto connect a guild
How it works
Setup takes a few minutes and changes nothing on your server.
- 01
The bot joins by code
You get a code after payment and run the connect command. One code works on one Discord server only.
- 02
Channels create themselves
The bot sets up channels for announcements, PvP, PvE and two archives. We never create roles, you map the ones you already have.
- 03
The raid leader posts a call
A form with content type, roster, gather and departure time. People sign up with a button or a message in the thread.
- 04
Attendance is counted
The leader marks the content as finished and everyone in the roster lands in the weekly count and in their own card.
#pvp-calls
GM
Albion Calls bottoday at 21:12
This is how a call looks in your Discord channel
What is inside
Everything guilds usually keep in spreadsheets by hand.
Attendance tracking
Weeks start Monday, Moscow time, PvP and PvE counted separately, history browsable week by week.
Guild roster
Members and roles sync from Discord. Name changes are kept in history so old reports stay readable.
Member cards
How much they run, what content, when they were last seen, rank by activity.
Role based access
The guild master maps server roles to access levels. We create no roles and ask for nothing extra.
History and export
The data stays with the guild: weekly sheets in Google Sheets and the full history in the dashboard.
Who it is for
Guild master
See who runs content and who is just on the list. Roster decisions on numbers, not memory.
Officer
Know who to promote and who to talk to before the next cleanup.
Raid leader
A call goes up in half a minute and the roster fills itself.
Member
Your own stats in plain sight: how much you ran and when you last showed up.
What the dashboard looks like
Sign in with Discord, no passwords. Everything else counts itself.
Attendance
‹ Week 22 Sep – 28 Sep ›runs completed14disbanded: 2
pvp96attendances
pve58attendances
members active41of 62 in roster
Weekly pace+4 vs last week
Activity table
TThorvaldTank9312
MMirelleHealer7411
KKaedanDPS8210
BBrannocDPS639
SSylvaSupport549
Demo guild with made up data: real client data never appears on the public page
Data and access
One code, one server
A connect code binds to your Discord server and will not work anywhere else.
We do not read messages
The bot only needs members, roles and its own channels for calls.
No roles of ours
The guild master maps roles that already exist on the server.
Access closes with a switch
If a guild leaves, the bot stops working and the history stays in the dashboard.
Questions
What permissions does the bot need?
Reading members and roles, creating its own channels and posting in them. Administrator rights are not required.
What if a Discord role is renamed or deleted?
The mapping is flagged as missing, settings show a warning, and access levels stay as they were. A guild can never end up without a master.
Can we connect two servers?
One code works on one server. A second server needs its own code.
Who can grant dashboard access?
The guild master and the deputy. Other roles are configured separately.
What if in game and Discord names differ?
The member card keeps both, and name changes go into history, so old reports stay correct.
What happens to our data if we stop paying?
The bot disconnects, the dashboard closes, and the guild data stays with us and is handed over on request.
Getting started
Billed monthly. We issue the connect code right after payment and help you map the roles.
Ask about pricing in Discord: it depends on guild size.
Connect your guild
Message us and we will issue a connect code and help you map the roles.