If this interaction has been acknowledged.
The permissions the bot has in the channel this interaction was sent from, if this interaction is sent from a guild.
Optional applicationThe application this interaction is for.
The ID of the application this interaction is for.
The ID of the channel this interaction was sent from.
The data associated with the interaction.
The entitlements for the user that created this interaction, and the guild it was created in.
The id of the guild this interaction was sent from, if applicable.
The preferred locale of the guild this interaction was sent from, if applicable.
Optional guildThe partial guild this interaction was sent from, if applicable.
The locale of the invoking user.
The member associated with the invoking user, if this interaction is sent from a guild.
The permissions of the member associated with the invoking user, if this interaction is sent from a guild.
The message the interaction is from.
The token of this interaction.
The type of this interaction.
The user that invoked this interaction.
Read-only property, always 1
The channel this interaction was sent from.
The guild this interaction was sent from, if applicable. This will throw an error if the guild is not cached.
Create a followup message. Note that the returned class is not a message. The message is located in the property message.
The options for creating the followup message.
Create a message through this interaction. This is an initial response, and more than one initial response cannot be used. Use createFollowup. Note that the returned class is not a message. This initial response does not return a message. You will need to call MessageInteractionResponse#getMessage on the returned class, or getOriginal.
The options for the message.
You cannot attach files in an initial response. Defer the interaction, then use createFollowup.
Edit the message this interaction is from. If this interaction has already been acknowledged, use editOriginal.
The options for editing the message.
Whether this interaction belongs to a cached guild channel. The only difference on using this method over a simple if statement is to easily update all the interaction properties typing definitions based on the channel it belongs to.
Whether this interaction belongs to a private channel (PrivateChannel or uncached). The only difference on using this method over a simple if statement is to easily update all the interaction properties typing definitions based on the channel it belongs to.
A type guard, checking if this interaction is an Autocomplete Interaction.
Whether this interaction is a button interaction. The only difference on using this method over a simple if statement is to easily update all the interaction properties typing definitions based on the component type.
A type guard, checking if this interaction is a Command Interaction.
A type guard, checking if this interaction is a Component Interaction.
A type guard, checking if this interaction is a Modal Submit Interaction.
A type guard, checking if this interaction is a Ping Interaction.
Whether this interaction is a select menu interaction. The only difference on using this method over a simple if statement is to easily update all the interaction properties typing definitions based on the component type.
Reply to this interaction. If the interaction hasn't been acknowledged, createMessage is used. Else, createFollowup is used. Note the returned class is not a message. Depending on which method was used, the returned class may or may not have the sent message. hasMessage can be used for type narrowing to check if message is present. If it is not, the getMessage can be used.
The options for the message.
Due to atachments not being able to be sent in initial responses, attachments will cause a deferred response, if the interaction has not been acknowledged.
Static fromStatic generateIDStatic getStatic get
Represents a component interaction.