Discord Bots

Build and host Discord bots in JavaScript, Python, and more — from your first token to a bot that never sleeps.

Your first Discord bot

Create the application, grab its token, switch on the intents it needs, and invite it to your server — the Developer Portal half that every bot needs before a single line of code runs.

Host a discord.js bot

Deploy the discord.js starter, paste in your token, and go from an empty server to a bot answering /ping — then learn exactly how the code works and add commands of your own.

BeginnerTemplate

Slash commands in depth

Grow one command set past /ping — typed options, subcommands, rich embeds, and buttons that carry data — with the discord.js v14 pieces you'll reuse in every bot.

Host a discord.py bot

The Python path to a live bot — deploy the discord.py starter, drop in your token, and get /ping answering, then walk through app.py and add commands of your own.

BeginnerTemplate

Organize a discord.py bot with cogs

One app.py is fine for /ping — past that it becomes a wall of code. Cogs split related commands into their own files, loaded at startup. Here's the exact three-file layout.

Host a TypeScript Discord bot

The Node.js application can't run a .ts file directly, so this bot compiles itself on every start — here's the recipe, why it works, and what to edit.

IntermediateTemplate

Storing data for your bot

Three honest options for remembering things between restarts — a JSON file, SQLite on the server, or a managed database that outlives reinstalls — and how to choose.

Build a music bot with Lavalink

A music bot is really two servers — a Lavalink audio node and your bot. Here's how they fit together on Falix, how to wire them up, and where to get the client code.

Structure a discord.js bot past one file

One index.js is fine for /ping — add ten commands and it's a wall. Here's the command-handler pattern discord.js bots grow into: a commands/ folder, an events/ folder, and a loader that wires them up automatically.

Crash-proof your Discord bot

One unhandled error shouldn't take your whole bot offline. Three layers of protection — try/catch in handlers, process-level safety nets, and an error channel — for discord.js and discord.py.

Set your bot's status and presence

Give your bot a "Playing", "Watching 5 servers", or "Listening to /help" status — set once when it's ready, or rotate through several on a timer. discord.js and discord.py, with the honest limits.

Check permissions before your bot acts

Before a command kicks, bans, or deletes, it should confirm the user is allowed — and that the bot itself can. Permission checks and role-hierarchy rules for discord.js and discord.py.

One bot, many servers

The same bot in twenty servers needs twenty different welcome channels, prefixes, and settings. Store per-guild config in SQLite so each server gets its own — and it survives restarts.

A web dashboard next to your bot

Run an Express dashboard and your discord.js bot in one Node process — the bot makes outbound connections, the web server takes your one public port. When it's a good idea, when to split into two servers, and the auth you must not skip.

Build a Discord bot with JDA (Java)

A complete Java bot with JDA — a Maven project, a fat jar that bundles every dependency, the token in a file next to the jar, and a working /ping. Build locally, upload, start.

Build a Discord bot with Serenity (Rust)

A minimal Rust Discord bot with Serenity — a Cargo project, a /ping-style message handler, and the honest truth about compile times on the Rust application, where your code builds on every start.