My bot is at ~60 commands and a single interactionCreate handler has become unmanageable. I'm considering a file-based router similar to Next.js.
How are you all organizing command registration, permissions and cooldowns?
We use a folder per command with a definition.ts and handler.ts, then a build step that generates the registration payload. Permissions and cooldowns live in the definition so they're checked before the handler ever runs.
The big win is that command registration becomes a diff: only changed commands get pushed to Discord.
+1 to file-based. I'd add a middleware chain (auth → cooldown → validate options) so handlers stay tiny.
Same approach here. Keep cooldowns in Redis if you run multiple shards, otherwise they reset per process.
Sign in to reply.