Where to go next

• Commands. Declaring one, the options it takes, subcommands, autocomplete, and context menus.
• Replying. Which reply method Discord allows from which state, how one throw stops 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, and 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.
• Plugins. Extending seedcord with your own functionality, reachable from every handler and typed. Attaching one, its lifecycle, and writing your own.
• Tooling. The dev loop, codegen, the build, logging, and the lint rules for a seedcord project.

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.

docs.seedcord.org (opens in a new tab) carries every exported symbol with its signature and its documentation, plus every error code and what throws it.

Ask in the Discord server (opens in a new tab).