Features Battleboard
The web half of the killboard: every battle a tracked guild fought, on a public page anyone can open — every side, who brought what, and every kill. Pick several and read them as one report.
01 · The battles list
One list per server, built to surface the evening’s real fights rather than every two-kill scrap.
Pick the server
Europe, Americas or Asia. Each server has its own list of battles, newest first by the time of each battle’s first kill.
Set the window and the size
The last 24 hours, 7 days or 30 days, and a floor of 5+, 10+ or 20+ kills — or any size. It opens on 7 days and 5+, so two-kill scraps never bury the evening’s real fight, and a line says how many smaller fights the floor is hiding, one tap from showing them.
Sort it, or find a guild
Newest, most kills or most fame. Type a guild’s name and the list narrows to the battles it was a side of. A guild you follow is named first on its rows.
Open the fight
Each row names both sides with the score between them, then the players seen, the kills and the fame. Two battles within ten minutes that share a side are drawn as one box — looks like one fight — with one tap to open both as a single report.
02 · A battle’s page
Every side named, every kill counted, and who brought what — the questions the guild asks the morning after, answered on one page.
Every side named, guild by guild under its alliance.
Players, kills, deaths, average item power and kill fame for each guild, with a bar of kills against deaths drawn on one scale for the whole table. Where Albion has published its own record of the battle, the head and the scoreboard print Albion’s figures for the whole fight.
The fight, minute by minute, on your own clock.
A line for each guild of the two named sides and a dot for every kill — each dot opens its kill — with the kills as bars under the lines and the three biggest numbered. Up to four more alliances that landed kills get thinner lines of their own.
Who brought what, side by side.
One side at a time, guild by guild: the weapons each guild carried, sorted into tank, healer, support, ranged and melee — and battlemount for a guild that rode one. A player with no weapon on record is counted, never guessed into a role.
Everyone who was there, every column a sort.
Ten a page with a search: each player’s weapon, guild, kills, deaths, assists, damage, healing, item power and kill fame. Copy names puts the whole list on your clipboard, ready to paste into Discord.
Every kill, a page at a time.
Eight a page, with a tab for each side holding the kills it landed and a search by player, guild or alliance. Every row opens the kill’s own page on the Killboard.
Who carried the fight.
Tiles for the most kills, the most damage, the most healing and the single kill that cost the most fame — each naming the player, their weapon and their guild. A category nobody scored in is left out, never shown as a 0.
Every time on the page is in your own time zone. The tabs, sorts and searches are part of the address, so a sorted table or a picked side is a link one member can hand another.
03 · Combined reports
Albion often splits one night’s fighting into several battles. Tick them, and the Battleboard reads them back as one report.
Tick the battles on the list and open them as one report — up to twelve — with the same scoreboard, timeline, composition, players and kills, over all of them. A player who fought in two of them counts once, and each battle’s × takes it back out.
On a battle’s own page, Combine with other battles opens the list with that battle already ticked, and Share copies its address.
In Discord, /killboard battles lists the
battles your guild fought — the last 7 days, or anywhere from 1 to 30 — and links them as
one report.
Only you can see this
Battles — last 7d
• 15/10/2026 — 12K / 3D
• 13/10/2026 — 27K / 9D
• 11/10/2026 — 5K / 6D
Open all on the battle board
04 · Raid reports
Once a raid has fought, the raid report in its Discord thread links one page for the whole evening — and that page keeps up while the raid is on.
The bot posts the raid report in the raid’s own thread: how many battles it fought and how many kills it took, its deaths, and the 🛡️ Request regear button. Its last line, 🗺️ This raid's battles as one report, opens the raid’s page on the Battleboard — and the link stays the same for the life of the raid, so battles that land later appear on the page rather than in a new link.
The page reads the evening from your guild’s side. A table lists every battle the raid fought, oldest first — its span, kills and fame, your side’s kills, deaths and assists, and whether you won, lost or broke even on fame — and under it the battles merge into one report. On a night of more than twelve battles the twelve biggest merge, and the page says how many it left out.
While the raid is on, an open page picks up new battles about once a minute — a Live line says so, and Refresh does the same by hand.
It stays your guild’s business: the page is not offered to search engines, its address is random and cannot be guessed, and it names your Albion guild and nothing from Discord — no raid title, no server, no roster. It needs your server bound to its Albion guild, with the killboard on.
05 · In Discord
A battle’s link unfurls in Discord with the fight’s own scoreboard drawn as a card — the channel sees the result before anyone clicks.
The preview names the two guilds the battle was fought between, the larger side first, with the players and the server — VITRYLA 12 – 1 BLACKHANDS · 46 players · Europe — over two lines: when it was, its kills, fame and sides, then who stood out.
The picture is the scoreboard in big type, drawn from the battle’s own numbers in the board’s dark look: the two sides that fought with their guilds under them, every other side on a row of its own. A battle that grows after the link was shared draws a new card the next time the link is pasted.
A kill’s link does the same with the kill card itself — see the Killboard.
06 · Honest limits
Stated up front, so nothing surprises you after install.
07 · Questions
/killboard battles follows when your guild fought on two.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.
Keep reading
The Battleboard reads the fights of guilds tracked with Guild Butler. Bind yours on the killboard — three taps in Discord — and every battle it fights is there to read.