Command details. Note that for message commands, positional arguments are inserted even if
they may not be subcommands or subcommand groups.
example
// A command that looks like this constinput="!myCommand arg1 arg2 arg3"
// Will output this constoutput={ body:{ _: ["arg1","arg2","arg4"], }, command: ["myCommand","arg1","arg2"], }
Because of this ambiguity, the decision of how to treat this behaviour is up to the
programmer later on. Note that this behaviour is properly handled by discord-express.
Readonly createdAt
createdAt:Date
Readonly createdTimestamp
createdTimestamp:number
Readonly guild
guild:null | Guild
Readonly guildId
guildId:null | string
Readonly id
id:string
OptionalReadonly interaction
interaction?:undefined = undefined
Readonly isInteractionRequest
isInteractionRequest:false = false
Readonly isMessageRequest
isMessageRequest:true = true
Readonly member
member:null | GuildMember
Readonly message
message:Message<boolean>
metadata
metadata:{} = {}
Extra metadata that can be stored for any purpose
Type declaration
[key: string]: unknown
Readonly requestType
requestType:"message" = ...
Readonly startAt
startAt:Date = ...
Readonly trigger
trigger:Message<boolean>
What triggered the command. In this case, it's a message
Arguments and options passed from the command