Commands Overview

A high-level overview of the command system architecture, explaining how commands are organized, loaded, and executed.

Introduction

Commands are the primary way users interact with your Discord bot.

Your bot supports multiple command types, each designed for different interaction styles while sharing the same core architecture.

This page focuses on how the command system works conceptually. Implementation details are covered in later sections.

The command system is built with the following goals:

Commands are designed to be:

This approach ensures your bot remains maintainable as it grows.

The command system currently supports:

Prefix-based commands triggered by normal Discord messages.

These commands are flexible and allow custom parsing logic, making them ideal for legacy support and advanced text-based workflows.

Interaction-based commands powered by Discord’s native slash command system.

They provide better user experience through auto-complete, validation, and discoverability.

Both command types coexist and follow the same architectural principles.

Commands are organized using a folder-based category system.

This allows:

Categories such as general, info, and moderation help keep commands intuitive and easy to manage.

Commands are not manually registered one by one.

Instead, the system:

This enables:

Adding a new command requires no changes to existing handlers.

All commands share a common metadata model, including:

This metadata allows handlers to enforce rules consistently and safely.

At a high level, command execution follows this flow:

This flow ensures predictable behavior across all command types.

This command system provides:

It scales well from small bots to large, feature-rich applications.