About Linen

One bot that does it all, done properly.

Linen replaces the stack of single-purpose bots most servers run with one family that looks the same, thinks the same, and works together.

Why Linen

Too many bots, not enough polish.

A typical server runs a moderation bot, a logging bot, an anti-nuke bot, a ticket bot, a music bot, and a voice channel bot. Each one has its own prefix, its own style, and its own idea of who's allowed to do what.

Linen puts all of that in one place. Moderation, security, staff management, roles, logging, and everyday tools live in the main bot. Temporary voice rooms and music live in their own bots, so they never get in each other's way, but they share Linen's permissions and shortcuts.

Every reply is short and clear, every big feature opens the same kind of setup menu, and every bot wears the same red.

Principles

How Linen is built.

A few rules every feature follows.

Clear over clever

Replies are one line where one line will do. Missing an option shows its usage, and missing a permission says which one.

Safe by default

Nobody can moderate someone at or above their own role. Mods using fake permissions have limits, and anti-nuke still watches them.

One kind of menu

Anti-nuke, logs, auto-mod, tickets, welcome, and more all open one card with a "Choose an action" dropdown and a Back button.

Works together

Linen VC reads Linen's fake permissions, god tiers, and aliases. The music bots know who owns each voice room. Anti-nuke never flags its own family.

Plays by Discord's rules

Linen works within Discord's limits instead of fighting them, like grouping fun and social commands under one slash command each.

Always on

The bots run around the clock on their own servers, and restart on their own if anything goes wrong.

Trust

Power flows down, never up.

Linen has a clear ladder of trust. Each level can only act on the levels below it, so nobody can moderate their way above the people who gave them power.

The server owner sits at the top. Bot admins configure everything. God tiers are for the people you trust most with anti-nuke. Admins can use every command, and the staff ladder you build covers the rest.

How permissions work →

1
Server ownerAdds bot admins, uses ,panic
2
Bot adminsConfigure everything, including anti-nuke
3
God tiers 0 to 3From bypassing everything to protection from non-god staff
4
AdminsEvery command except Security settings
5
Staff ranksYour own ladder, with promotions and vouches
Roadmap

Built in phases. Tested at every step.

Each phase was finished and tested in a real server before the next one started.

Phase 1 · Done

Foundation

Chat and slash commands, prefixes, aliases, command restrictions, fake permissions, bot admins, god tiers, and the help menu.

Phase 2 · Done

Moderation and logging

Cases, punishments, hardbans, role mutes, auto-mod, the flagged-content review queue, ban appeals, and 11 log channels.

Phase 3 · Done

Protection and staff

Anti-nuke with auto-restore and the delayed disable, ,panic, the staff ladder, promotions, vouches, strikes, and activity tracking.

Phase 4 · Done

Utilities and extras

Info and personal tools, server stats, tickets, welcome messages, giveaways, birthdays, roles, self-roles, social lookups, and games. Plus Linen VC and Linen Music.

Ready when you are.

Add Linen to your server, or read the docs to see everything it can do.