Command Design

[VincentRPS]

Commands are one of the biggest parts of a Discord library today. It determines the user base and other such aspects.

It is important then that we establish a good and well-fleshed-out base for commands, and that's what this discussion does.

This is a more fleshed-out version of my old Pycord Book and explains commands in deeper sentiment.

Firstly, there will be a base command class that features the basic aspects of a class:

• async _invoke - The command has been invoked
• const[str] _event_proc - The event this command processes, data will be sent to _invoke.
• const[str] name - The command's name
• class/null group - The Group this command belongs to, should subclass BaseGroup.
• async _callback - The callback the command should call when invoked

These will all tie into a system that is adversely versatile and extensible. You can hook anything into it and it would work.

Now onto groups, groups are as the name suggests a group of commands, so it averagely just groups together BaseCommands and even holds groups in itself.

It would look something like this:

• const[list[BaseCommand]] commands - The commands this group holds
• const[list[BaseGroup]] groups - The groups this group holds.
• function command - create a new command in this group.
• function group - create a new group in this group.
• const[str|null] name - The Group's name.

While developers can add extra parameters to these bases, they have to be optional unless otherwise stated.

And that's mostly all of the systems a command baseline would need. Else than expansion, and maybe stuff like command concurrency this design should be nearly perfect in every aspect and will aspire to the next generation of Discord bots on Python.