Where to go next
Find what to read once your bot runs, plus the example bots, the API reference, and where to ask for help when you get stuck.
Your bot is running and answering /ping. Everything after this page is what you add on top of it.
The tabs
- Commands. Declaring one, the options it takes, subcommands, autocomplete, context menus, and cleaning up what Discord already has registered.
- Replying. Which reply method Discord allows from which state, how one
throwstops a command and tells the user why, and the helpers for building the text you send. - Components. The class that wraps a discord.js builder, then buttons, select menus, modals, and pagination. Discord hands a click back as a plain string. seedcord gives you back the fields you put in it, typed.
- Checks. Gates that run before your handler and refuse by throwing, like permissions, cooldowns, and rules you write. Middleware that runs around every handler, and the order seedcord runs them all in.
- Events. Messages, members, reactions, and the rest of what discord.js emits, on gateway. Publishing and subscribing to your own works on either transport.
- Built-ins. The kv store for keeping records between interactions, the drivers that keep them through a restart, and logging.
- Plugins. Adding a database or anything else your bot needs, reachable from every handler and typed. Attaching one, its lifecycle, and the Mongoose and Kysely plugins.
- Writing plugins. Building your own plugin, limiting where it runs, reloading it in dev, testing it in a bot on your machine, and publishing it.
- Tooling. The dev loop, codegen,
seedcord commands, the tunnel an http bot runs behind, the lint rules for a seedcord project, andseedcord ask, which searches this guide from your terminal in natural language. - Build & deploy. How seedcord runs your bot through Vite, every config key, Vite plugins,
.envmodes, and building for a server, Cloudflare Workers, an npm package, or a route in your own server.
The example bots
mocks/gateway (opens in a new tab) is a runnable bot that does much more than the scaffold. It has pagination done two ways, an autocomplete route, a gated command, both kinds of context menu, event handlers, and commands that throw on purpose so you can see what the user gets.
mocks/http (opens in a new tab) runs the same ping bot on the other transport, and mocks/edge (opens in a new tab) runs it on Cloudflare Workers.
seed (opens in a new tab) is a full bot on Cloudflare Workers, with commands that search this guide and the reference, and you can add it to a server to try them. It also has some utility commands and helpers, and we'll continue to expand it with more features over time.
The reference
seedcord.org/docs (opens in a new tab) carries every exported symbol with its signature and its documentation, plus every error code and what throws it.
If you get stuck
Paste the error or your question into seedcord ask. If that doesn't answer it, ask in the Discord server (opens in a new tab).