The Bot library: ready-made bots

Some bots are written and given away by other people, and they are what most servers actually need: tickets, modmail, moderation. The Bot library tab in the panel sets one up for you. It goes into its own folder in bots, next to anything else you run here (Running several bots).

What is on the list

• Discord Tickets by eartharoid (GPL-3.0): support tickets with a web settings panel, transcripts and staff statistics. Needs Node.js 18 or newer.
• Modmail by Dragory (MIT): members DM the bot, your staff answer in a private channel, every thread logged. Needs Node.js 24.
• Red by Cog Creators (GPL-3.0): an all-in-one bot you extend with plugins (cogs). Needs Python 3.10 or 3.11.

Every bot on a server uses the language the server is set to, so the tab only offers what this server can run. Change it in Startup > Docker Image if nothing else here needs the current one.

We list a bot only when its licence lets anyone run it and it does not need another service we do not have. Music bots that play from YouTube are not on the list: YouTube's terms do not allow it, whatever the bot. If there is something else you would like to see here, ask.

Adding one

1. Make the bot in the Developer Portal and copy its token, as in your first bot. Each bot here needs its own.
2. Open Bot library in the panel and press Add under the one you want.
3. Fill in the boxes. Every bot asks for its token; some ask for a server ID or a channel ID (turn on Developer Mode in Discord's settings, then right-click and Copy ID).
4. Leave Restart the server now ticked and press Add. The console shows it downloading and installing, which takes a minute or two the first time.

Whatever you type goes into bots/<folder>/.env on your own server and nowhere else. After it is installed, the page shows the few things only you can do, like adding the settings panel's address to your Discord application.

What it actually installs

The bot's own code, from the project's own repository at a fixed release, downloaded to your server. Nothing is changed by us and nothing is copied out of our images, so what runs is what the authors published. Its licence and a link to the source are on the card.

Changing, updating and removing

• Settings: edit bots/<folder>/.env in Files and restart. Every option the bot has can go in there (each project's own documentation lists them).
• Updating: change GIT_BRANCH to the newer release tag and restart. Red is pinned in its requirements.txt instead.
• Removing: delete the folder in Files and restart. Stopping it for now: put ENABLED=false in its .env.
• One web page per server: a server has one port, so only one bot that has a web page (Discord Tickets, Modmail) can use it.

These bots are other people's work: their documentation and their support servers are the place for questions about what they do. Anything about the server itself, we answer.

Something here wrong or out of date? Tell us and it gets fixed.