74 replies

How should you, the end user, define commands?

How should you define what application commands are for what command classes, and how should they be registered for you? (SUPER IMPORTANT QUESTION)

: Default by the

command.name

command.name

, otherwise

command.chatInputName

command.chatInputName

(for chat input commands) or

command.contextMenuName

command.contextMenuName

for context menus, and provide a utility function on the command store that lets you register them if missing at ready (can go into more details if this option is chosen)

: Passing in an array of

@discordjs/builders

@discordjs/builders

in the command class's options, which get pushed to the API based on client settings (as above, with some options for handling existing commands and what not)

: Propose a better solution

S-IaF

Sapphire - Imagine a Framework•5y ago•

74 replies

vladdy

How should you, the end user, define commands?

How should you define what application commands are for what command classes, and how should they be registered for you? (SUPER IMPORTANT QUESTION)

: Default by the

command.name

command.name

, otherwise

command.chatInputName

command.chatInputName

(for chat input commands) or

command.contextMenuName

command.contextMenuName

for context menus, and provide a utility function on the command store that lets you register them if missing at ready (can go into more details if this option is chosen)

: Passing in an array of

@discordjs/builders

@discordjs/builders

in the command class's options, which get pushed to the API based on client settings (as above, with some options for handling existing commands and what not)

: Propose a better solution

How should you, the end user, define commands?

Similar Threads

How should you, the end user, define commands?

Similar Threads

Similar Threads

Similar Threads